Chrome DevTools MCP
Official Chrome DevTools as an MCP server for coding agents
AI Agents / Browser Automation · OSS/MIT · 50.8k
What's Good
Official Chrome DevTools team MCP server. Agents get performance traces, network inspection, console with source-mapped stacks, screenshots, and Puppeteer-backed automation that waits for results. Works with Antigravity, Claude, Cursor, Copilot. Slim mode for basic browsing; full mode for debugging. This is the browser surface built for coding agents, not a generic scraper.
The Catch
chrome-devtools-mcp@1.8.0 engines: "^20.19.0 || ^22.12.0 || >=23". 20.16 and 20.17 fail; 20.19 LTS is in engines. “Node ≥ 22.12” and “Node 20 fails” are both too blunt — README “LTS” is marketing; engines is the catch. A CLI is provided for use without MCP; official CLI docs call it experimental. Complementary to Playwright MCP already on the catalog—DevTools-grade traces, Lighthouse, heap snapshots, and --autoConnect, not a generic scraper or a Playwright replacement. Officially supports Google Chrome and Chrome for Testing only. Exposes browser content to the MCP client—do not point it at sensitive sessions. Usage statistics on by default (opt out with --no-usage-statistics). Needs a current Chrome.
Verdict
The MCP browser for agents that need real DevTools, not just clicks.
Embed
[](https://stackgems.com/gems/chrome-devtools-mcp)