MCP servers that ship as code — a repository or a package you install and run locally (usually over stdio). They have no hosted endpoint, so we cannot probe or grade them: instead each one shows its repository, install command, license, stars and when it was last updated.
Collected from GitHub repositories and npm, PyPI, Cargo, Go, Maven, NuGet and RubyGems packages tagged as MCP servers, the official MCP Registry, Docker's MCP catalog, ModelScope, Baidu MCP World, Cline and other public directories; one entry per repository. A server that also offers a hosted endpoint is listed under Remote instead. These entries are not counted in our reachability, verification or readiness statistics.
-
iflow-mcp_chrome-devtools-mcpgithub.com/benjaminr/chrome-devtools-mcpupdated this year
Chrome DevTools Protocol integration for Model Context Protocol
pypi MIT -
MCP server that lets AI agents control your Chromium browser through the Chrome DevTools Protocol.
MIT ★ 2 -
An MCP Server for Chrome DevTools, following the Chrome DevTools Protocol. Integrates with Claude Desktop and Claude Code.
MIT ★ 316 -
Capture browser console logs via the Chrome DevTools Protocol and expose them to an MCP client over SSE.
MIT -
Let AI agents use your real Chrome over MCP: each agent in its own tabs and coloured tab group, beside you, and cleaned up when done. Native messaging + Chrome DevTools Protocol, Windows/Linux/macOS, works with any MCP client.
MIT ★ 2 -
MCP server that controls a running Chrome over the Chrome DevTools Protocol (CDP). It connects to Chrome's remote-debugging endpoint and exposes browser control as MCP tools.
-
Model Context Protocol server for Playwright with Chrome DevTools Protocol support
npm MIT -
electron-mcp-servergithub.com/halilural/electron-mcp-serverupdated this year
MCP server that lets AI assistants automate, debug and screenshot any Electron app over the Chrome DevTools Protocol — no app changes required.
MIT ★ 71 -
cray-browsergithub.com/hencray/cray-browserupdated this year
Browser automation MCP server for Claude Code — control real Chrome via DevTools Protocol and native messaging.
-
Spectra — a Chrome DevTools Protocol profiler that identifies the files, functions and components causing frontend slowness, across React, Vue, Svelte, Angular and Next.js builds.
npm MIT -
Hand a whole browser task off in one call: a decision model drives the page server-side, so a flow costs one call, not a turn per click. Ref-based element tables, code-checked assertions, zero-model macro replay, over the Chrome DevTools Protocol.
MIT ★ 25 -
Tradingview-Premium-Claude-MCP-Setupgithub.com/saket3395/Tradingview-Premium-Claude-MCP-Setupactive
TradingView Premium × Claude MCP setup — drive your own TradingView Desktop session via Chrome DevTools Protocol for chart analysis, signals, and backtesting from Claude Code. Analysis only, no order execution.
MIT ★ 16 -
🚇 A plugin-based MCP server for React Native runtime debugging, inspection, and automation. Connects to Metro bundler via Chrome DevTools Protocol — no app code changes needed for most features.
MIT ★ 89 -
tellfigmagithub.com/mrpeterperez/tellfigmaupdated this year
MCP server that gives AI apps (Claude, Cursor, VS Code Copilot, Windsurf) full CREATE/EDIT/DELETE control over Figma via Chrome DevTools Protocol. The only Figma MCP that can modify designs. Now with comment reading/posting. No plugin — just npx tellfigma
npm MIT -
Stealth browser automation for AI agents over MCP and the Chrome DevTools Protocol: navigation, network hooks, DOM extraction, and pixel-accurate UI cloning.
MIT ★ 3,362 -
MCP Server for Chrome Developer Console Log monitoring via Chrome DevTools Protocol
-
gasoline-mcpgithub.com/brennhill/gasoline-mcp-ai-devtoolsupdated this year
Gasoline MCP is an AI Debugger, Inspector, and Observability toolkit. It acts as Chrome DevTools for AI Agents using the Model Context Protocol (MCP).
npm AGPL-3.0-only -
iflow-mcp_brennhill-gasoline-agentic-browsergithub.com/brennhill/gasoline-agentic-browser-devtools-mcpupdated this year
Gasoline Agentic Browser is an AI Debugger, Inspector, and Observability toolkit. It acts as Chrome DevTools for AI Agents using the Model Context Protocol (MCP).
pypi AGPL-3.0-only -
screenshot-mcpgithub.com/Kembec/screenshot-mcpno update data
Capture full-page screenshots of any URL via Chrome DevTools Protocol — single static binary.
smithery -
一个基于 Puppeteer 和 Chrome DevTools Protocol (CDP) 的 MCP Server 插件，支持通过持久化浏览器连接进行调试和排查。
MIT ★ 1 -
@ai-capabilities-suite/mcp-debugger-servergithub.com/digital-defiance/mcp-debugger-serverupdated this year
Enterprise-grade MCP server providing advanced debugging capabilities for Node.js and JavaScript applications via Chrome DevTools Protocol. Features 25+ debugging tools including breakpoints, variable inspection, execution control, CPU/memory profiling, h
npm MIT -
Stealth browser automation that actually works. Runs Camoufox (custom Firefox) in Docker with zero Chrome DevTools Protocol exposure, real OS-level mouse and keyboard input via PyAutoGUI, and a JSON HTTP API + MCP server to control it all remotely. Watch it live via noVNC.
WTFPL ★ 98 -
cdpilotno update data
cdpilot is a browser automation CLI and local MCP server that talks to Chrome, Chromium, Brave or Vivaldi directly over the Chrome DevTools Protocol, with no Puppeteer, Playwright or Selenium and no browser download. Its 45 MCP tools cover navigation, clicks and form filling (including inside cross-origin iframes), accessibility-tree snapshots, screenshots, test assertions, a page's own WebMCP tools, and Web Bot Auth request signing. `cdpilot connect` attaches to a browser you started yourself, so a person can clear a login or CAPTCHA and the agent continues; cdpilot never closes that browser. Every feature has a runnable example with its real output: https://github.com/mehmetnadir/cdpilot/tree/main/examples
smithery -
A lightweight chrome-devtools-mcp alternative: an MCP server + CLI that drives the tabs you name, one target per call over one direct WebSocket, with a bounded timeout on every call, so a stuck page can't wedge your agent or force a /mcp restart. Chrome o
npm MIT -
devtools-lens-mcpgithub.com/aakcay5656/devtools-lens-mcpupdated this year
Give your AI agent Chrome DevTools. Debug Chromium apps through console, network, DOM, accessibility, screenshots, and change analysis.
MIT -
MCP server giving AI assistants real Chrome DevTools access — console, network, DOM, source maps, breakpoints and step debugging — with multi-session tab isolation.
npm MIT -
MCP server for Chrome debugger protocol (Node.js)
MIT ★ 2 -
@vitalyostanin/mcp-chrome-debugger-protocolgithub.com/vitalyostanin/mcp-chrome-debugger-protocolupdated this year
MCP server for Chrome debugger protocol (Node.js)
npm MIT -
MCP server that gives every AI agent session its own persistent, isolated Chromium browser (Chrome, Edge, Brave, Chromium) with extension control. Built on chrome-devtools-mcp.
MIT -
A lightweight chrome-devtools-mcp alternative: drive the Chrome tabs you name, one target per call over one direct WebSocket with a bounded timeout on every call, so a stuck page can't wedge your agent. 39 tools, network mocking, a cookie group, and tab leases so several agents share one browser. No all-target fan-out.
npm MIT ★ 1 -
Let Claude Code, Codex, Cursor and any MCP agent use your real Chrome browser: navigate, click, type, read pages, console and network, with per-capability switches and a one-command setup.
MIT ★ 5 -
css-noop-checkergithub.com/purupurupu/css-noop-checkerupdated this year
Chrome DevTools extension that detects CSS properties with no effect
MIT ★ 25 -
claude-chrome-parallelgithub.com/shaun0927/claude-chrome-parallelupdated this year
Ultrafast parallel browser MCP. Say 'ccp' and Claude automates your Chrome.
npm MIT -
MCP server that lets AI agents drive your Chromium browser through the DevTools Protocol
npm MIT -
Native C++ MCP server for Chrome automation — zero dependencies, instant startup, 22 tools
Apache-2.0 -
Expose the ChatGPT desktop app's browser bridge (formerly Codex Desktop) as an MCP server — drive Chrome and Edge from Claude Code and other agents.
npm MIT ★ 26 -
Grok Build drives your real Chrome: click, type, read console/network, screenshot, record GIFs. No second browser, no Playwright.
MIT ★ 1 -
Debug and fault-test any WebRTC session — Chrome extension, MCP server for AI coding agents, npm library, and Playwright plugin. Live RTCPeerConnection/WebSocket inspection, reconnect testing, network-loss simulation.
MIT ★ 4 -
chrome-eyegithub.com/trvux/chrome-eyeupdated this year
MCP server giving Claude Code a fast, cheap structured-JSON eye into real Chrome via CDP — no screenshot vision loop
MIT -
why-cssgithub.com/shaohui-jin/why-css-skillsupdated this year
CSS 失效诊断 MCP 服务器：对齐运行时、构建产物与源码，回答样式为什么没生效
npm MIT -
Let AI models control your real browser through MCP. A Chromium extension plus an MCP server, with tools for tabs, pages, input and DevTools.
NOASSERTION -
Turn your everyday Chrome into a universal MCP server - one extension + one endpoint for every MCP client (38 browser tools: snapshot/click/fill, network, console, cookies, PDF, CDP debug)
MIT -
CSS 失效诊断 MCP 服务器：对齐运行时、构建产物与源码，回答样式为什么没生效
npm MIT -
SeleniumBase for Rust (unofficial port): browser automation and testing with the SeleniumBase API, a driverless Chrome DevTools engine, stealth mode, and an MCP server for AI agents.
NOASSERTION ★ 1 -
Lets Claude Code and Cursor drive Chrome. Blind benchmark vs agent-browser: -33% tokens, -33% cost, -24% tool calls, -32% time, 30/30.
npm MIT -
chrome-devtools-mcp plus one tool: Jev walks the browser to the spot, your agent makes one devtools call there.
MIT ★ 1 -
agent-browser-bridgeactive
Live multi-tab, multi-profile Chrome DevTools MCP bridge for AI agents (Antigravity, Claude, Cursor, Windsurf)
npm Apache-2.0 -
Open-source browser automation MCP server. Control your real Chrome from any AI agent.
npm MIT -
Local-only MCP server that drives the real Chrome you already have open (your profile, your logins, your session) through a companion extension. 45 tools across navigation, perception, capture, and CDP-backed trusted input that pages receive with isTrusted=true.
MIT -
MCP server that lets many Claude Code sessions and subagents share numbered, logged-in Chrome instances over CDP
MIT ★ 3 -
A security-first bridge between Claude Code (MCP) and Chrome — HMAC pairing, domain allowlist, per-domain evaluate opt-in.
MIT ★ 10 -
MCP tool server for Claude Code: browser and Chrome DevTools automation, HTTP, SQL and MongoDB, system intelligence, on-demand MCP server catalog
MIT ★ 1 -
Browser Bridge: a Chrome extension + local MCP server that gives any AI agent access to your real, logged-in browser
MIT ★ 4 -
Local-first MCP server + Chrome extension for AI agents to control your existing logged-in Chrome session via CDP, native AI tab groups, and a side panel.
MIT -
Drive the Chrome or Edge you're already signed into — from one script. A zero-dependency browser automation runtime, CLI and MCP server for AI agents.
npm MIT ★ 2 -
MCP server that lets AI use your real Chrome: tabs, cookies, logged-in sessions, network and console capture
MIT ★ 7 -
—
MIT ★ 2 -
Let Claude Code, Cursor and any MCP client drive your real, logged-in Chrome: multiple profiles and parallel tabs, 100% local. Zero-dependency MCP server + MV3 extension.
npm MIT -
Codex/Claude Code向けのローカルChromium MCPサーバー — Brave/Chrome/Edgeを起動・接続、セマンティックスナップショット、PDF抽出、36ツール
MIT -
MCP server that drives a real Chrome browser via CDP + Playwright: structured snapshots, click/type, screenshots, network inspection. Persistent login state in an isolated profile.
NOASSERTION