Google's Apache-2.0 MCP server and CLI that lets AI agents drive and debug a live Chrome: clicks, screenshots, console, network and performance traces.
Free tool inMCP servers and agent tools
Chrome DevTools MCP at a glance
Checked 22 Oct 2026Chrome DevTools MCP (v1.11.0, Oct 2026, ~54k stars) gives Claude, Cursor, Copilot and other agents control of a real Chrome through Puppeteer, plus DevTools: network requests, console logs, screenshots and performance traces. It can launch Chrome or attach to a running one over a debugging port. Officially supports Chrome only. Google collects usage statistics by default (--no-usage-statistics turns it off), and performance tools may send URLs to the CrUX API. Needs Node.js LTS and current Chrome. Apache-2.0.
RepoQuarry. “Chrome DevTools MCP.” Checked 22 Oct 2026. https://repoquarry.dev/projects/chrome-devtools-mcpWhat it replaces
Nothing people pay for: it’s a free tool, listed because people search for it. Find similar projects in MCP servers and agent tools.
Facts, with sources
Every answer links to where we found it. We read the documentation; we did not install it.
lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser.github.com · chrome-devtools-mcp#readme ↗ today
Data collection is enabled by default. You can opt-out by passing the --no-usage-statistics flaggithub.com · chrome-devtools-mcp#usage-statistics ↗ today
current stable version or newer.github.com · chrome-devtools-mcp#requirements ↗ today
By default, chrome-devtools-mcp in WSL requires Chrome to be installed within the Linux environment.github.com · troubleshooting.md ↗ today
Chrome current stable version or newer.github.com · chrome-devtools-mcp#requirements ↗ today
No licence changes since we started watching. Licence watch: follow Chrome DevTools MCP and we email you if its licence terms change.
Growth and activity in detail
Is it popular, and is anyone still working on it? From GitHub.
Numbers appear after the first nightly fetch from GitHub.