Open Source
Explore the latest AI open-source projects from GitHub and HuggingFace.
Explore the latest AI open-source projects from GitHub and HuggingFace.
Chrome DevTools MCP is Google's official Model Context Protocol server that exposes the full power of Chrome DevTools to coding agents such as Claude Code, Antigravity, Cursor, Codex, Copilot, Cline, and any other MCP client. With 41,737 stars, 2,653 forks, and an Apache 2.0 license, the project has become one of the most installed MCP servers in 2026 because it solves the single biggest weakness of browser-based agent workflows: agents could navigate but they could not actually debug. The server is shipped as the `chrome-devtools-mcp` npm package and is maintained by the Chrome DevTools team itself. ## A Real Debugger, Not Just Browser Automation Most browser-control MCPs stop at clicking, typing, and screenshot capture. Chrome DevTools MCP goes further by exposing the same primitives that human engineers use in DevTools — network request inspection with source-mapped stack traces, console message capture, and full performance trace recording. Performance traces are processed into actionable insights rather than raw waterfalls, which is what makes them usable by an agent that needs to decide whether a slow page is bound by render, network, or main-thread work. The performance tools can optionally hit the Chrome User Experience Report (CrUX) API to compare lab measurements against real-user field data, giving the agent both kinds of evidence at once. ## Built on Puppeteer for Reliable Automation Under the hood the server uses Puppeteer for browser control, with automatic waiting on action results so an agent does not have to write fragile sleep statements between clicks. This is the same primitive Google uses internally for its own end-to-end testing, which means the reliability profile is meaningfully higher than ad-hoc Playwright wrappers. The server officially supports Google Chrome and Chrome for Testing, with explicit commitment to track the latest Extended Stable Chrome release. ## First-Class MCP Client Coverage The README ships configuration recipes for an unusually wide set of MCP clients: Amp, Google's own Antigravity browser-agent, Claude Code (both the CLI install and the plugin marketplace install with bundled skills), Cline, Codex, Command Code, GitHub Copilot CLI, VS Code Copilot, Cursor, and more. Most of those flows reduce to a single command — for example, `claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest` — and the plugin-marketplace install path additionally bundles skills so the agent receives expert guidance on when to invoke each tool. ## Slim Mode for Lightweight Use Cases For agents that only need basic navigation, screenshot, and console capture, the server ships a `--slim --headless` mode that trims the tool surface. This matters in MCP because every additional tool the model sees consumes context budget and creates more opportunity for the model to choose the wrong tool. Slim mode lets teams trade depth for token efficiency without forking the server. ## Privacy and Operational Posture Google is explicit about what the server collects: usage statistics including invocation success rates, latency, and environment info, with documented opt-out flags (`--no-usage-statistics`, `CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS`, or simply setting `CI=true`). Performance trace URLs sent to the CrUX API can be disabled with `--no-performance-crux`. The disclaimers also warn that the server gives MCP clients access to any data visible in the browser instance, which is the right framing for production deployments: this is a debugger, not a sandbox, and it should be pointed at controlled browser sessions only. ## Why It Matters The arrival of an official, well-maintained MCP from the Chrome DevTools team is significant because browser debugging has been the missing piece of agent toolchains. Coding agents could already read source files, run tests, and call external APIs, but they could not see what their generated frontend code actually did in a real browser. Chrome DevTools MCP closes that loop with Google's own tooling under a permissive open-source license, which is why it is now the default browser-debug primitive for Antigravity, Claude Code, and most other production agent harnesses.