Chrome DevTools MCP Chrome DevTools MCP
Chrome DevTools MCP is the Chrome team's official Model Context Protocol server that gives coding agents the full power of Chrome DevTools against a live browser. Added to any MCP client with `npx -y chrome-devtools-mcp@latest`, it lets an agent record performance traces and extract actionable DevTools insights, analyse network requests, read console messages with source-mapped stack traces, take screenshots and drive pages reliably through Puppeteer with automatic waiting for action results. A `--slim` mode exposes only basic browser tasks, `--headless` runs without a window, and advanced options cover concurrent sessions, persistent user-data directories, attaching to an already-running Chrome over WebSocket, and debugging on Android. A standalone CLI is provided for use without MCP, and the docs include client configuration guides for Antigravity, Claude Code, Cursor and VS Code plus guidance on running it as a browser subagent. It officially supports Google Chrome and Chrome for Testing, tracking the latest Extended Stable release.
Chrome DevTools MCP released v1.10.0 and v1.10.1 on 23 September 2026, appears on GitHub's monthly trending list with about 52,600 stars, and is now documented at developer.chrome.com/docs/devtools/agents; community plugins and posts (for example a Jev-Reach plugin that reduces model turns per click) show active third-party use.
As of
- Official Chrome team MCP server and CLI for coding agents
- Performance tracing with DevTools-derived insights and optional CrUX field data
- Network request analysis, console messages with source-mapped stack traces and screenshots
- Reliable Puppeteer-based automation that waits for action results
- --slim, --headless and --isolated modes; connect to a running Chrome; Android debugging
- Client configuration guides for Antigravity, Claude Code, Cursor and VS Code
- Design principles for use as a browser subagent inside larger harnesses
Web developers who want their coding agent to verify, debug and performance-profile the actual page in Chrome rather than guessing from source code.
Teams that need cross-browser (Firefox/Safari) automation, or environments where exposing a live browser session and its data to an MCP client is unacceptable.
Chrome DevTools MCP is free and open source under the Apache-2.0 license, published to npm as chrome-devtools-mcp. It requires Node.js LTS and a current stable Chrome. Google collects anonymous usage statistics by default (opt out with --no-usage-statistics or the CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS/CI environment variables), and performance tools may query the Google CrUX API unless --no-performance-crux is set.
Chrome DevTools MCP is the reference way to give an agent real browser observability — first-party, well maintained and far deeper than screenshot-only browser tools — with the caveat that you should review its default telemetry and the data it exposes to MCP clients.
Is Chrome DevTools MCP free?
Yes - Chrome DevTools MCP is Open Source. Chrome DevTools MCP is free and open source under the Apache-2.0 license, published to npm as chrome-devtools-mcp. It requires Node.js LTS and a current stable Chrome. Google collects anonymous usage statistics by default (opt out with --no-usage-statistics or the CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS/CI environment variables), and performance tools may query the Google CrUX API unless --no-performance-crux is set.
Is Chrome DevTools MCP open source?
Yes - Chrome DevTools MCP is open source. Chrome DevTools MCP is free and open source under the Apache-2.0 license, published to npm as chrome-devtools-mcp. It requires Node.js LTS and a current stable Chrome. Google collects anonymous usage statistics by default (opt out with --no-usage-statistics or the CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS/CI environment variables), and performance tools may query the Google CrUX API unless --no-performance-crux is set.
Who is Chrome DevTools MCP best for?
Web developers who want their coding agent to verify, debug and performance-profile the actual page in Chrome rather than guessing from source code.
Who is Chrome DevTools MCP not ideal for?
Teams that need cross-browser (Firefox/Safari) automation, or environments where exposing a live browser session and its data to an MCP client is unacceptable.
What are the best Chrome DevTools MCP alternatives?
The closest Chrome DevTools MCP alternatives on ai.dosa.dev are Pieces for Developers, agenttrace, Vibe Kanban - all listed under Developer Productivity & Workflow.
Who makes Chrome DevTools MCP?
Chrome DevTools MCP is developed by Google (Chrome DevTools). It is listed in the Developer Productivity & Workflow category on ai.dosa.dev.
Favorite this tool to revisit it later, or Zap it to contribute to the public vote count.
Content on this page is AI-generated. Please verify details with the vendor's website for accuracy.