What it is
Chrome DevTools MCP, which Google now calls Chrome DevTools for agents, gives an agent control of a real Chrome browser and the inspection tools of DevTools. Beyond clicking and filling forms, it can record performance traces, read network requests and console messages with source-mapped stack traces, run Lighthouse audits and analyse heap snapshots.
Install with npx -y chrome-devtools-mcp@latest on a Node.js LTS release. The tool reference lists 59 tools; memory tools need --memoryDebugging and coordinate clicks need --experimentalVision, while --slim cuts the set to three. It can launch its own Chrome, attach to a running one with --autoConnect, or connect over a remote debugging port. Only Google Chrome and Chrome for Testing are officially supported.
Version 1.12.0 shipped on 22 October 2026, a week after 1.11.0. The package also includes a chrome-devtools CLI and skills, for agents that prefer commands to MCP.
Install
npx -y chrome-devtools-mcp@latestOur review
Chrome DevTools MCP is a debugger first and a browser driver second, and that is its case against Playwright MCP. performance_start_trace and performance_analyze_insight return trace findings, list_network_requests and get_network_request show the failing call, and console messages arrive with source-mapped stack traces. Heap snapshot tools such as compare_heapsnapshots and get_heapsnapshot_retaining_paths take an agent into memory-leak work that Playwright MCP does not attempt.
The project moves quickly. It passed 54,000 GitHub stars, and the 1.12.0 release added parallel execution of independent tool calls, live config reloading and heap analysis without a browser connection. The trade-off is surface area: 59 tools is a heavy load for a model's context, which is why --slim exists, though three tools is a blunt alternative.
The defaults send data to Google. Usage statistics such as tool success rates, latency and environment details are collected unless you pass --no-usage-statistics or set CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS (setting CI also disables it). Performance tools may send trace URLs to the Chrome UX Report API unless you pass --no-performance-crux. The server also checks npm for updates periodically.
Local exposure needs equal care. The profile at ~/.cache/chrome-devtools-mcp/chrome-profile persists between runs unless you pass --isolated, and the docs warn that opening a remote debugging port lets any application on the machine control the browser. Four medium-severity advisories have been published, the latest two disclosed on 22 October 2026 for bugs already fixed in 1.4.0 and 1.5.0: service-worker fetches that bypassed the URL allow and block lists, and a symlink path that escaped MCP roots. Cross-browser work still belongs to Playwright, since only Chrome is supported.
Where it earns its place
A performance engineer at an e-commerce site with a slow product page
Find what is hurting load time and propose a fix
The agent records a trace with performance_start_trace, reads the insights and checks the network waterfall, then edits the code. Run it with --no-performance-crux if the staging URLs should not reach Google.
A React developer chasing a memory leak in a single-page dashboard
Work out which component keeps detached DOM nodes alive
Starts the server with --memoryDebugging, takes heap snapshots before and after the suspect route change, and has the agent compare them and follow retaining paths. Free, though heap snapshots of a large app are slow to analyse.
An engineering lead at a 25-developer agency
Let developers debug client sites with an agent without leaking client data
Standardises on --isolated and --no-usage-statistics in the shared MCP config, and bans connecting to personal Chrome profiles. That keeps client logins out of the persistent profile and usage data away from Google.
Before you commit
- Setup
- npx -y chrome-devtools-mcp@latest in Claude, Cursor, Copilot, Antigravity, Gemini CLI and other clients; the browser starts on the first tool call that needs it, so a first trace takes a few minutes.
- Integrations
- 59 tools in 11 groups, including navigate_page, click, fill_form, evaluate_script, lighthouse_audit, performance_start_trace, list_network_requests and 14 heap snapshot tools; --slim leaves navigate, evaluate and screenshot.
- Data and privacy
- Exposes everything in the browser profile to the MCP client. Usage statistics go to Google by default, trace URLs may go to CrUX, and four medium-severity advisories were published in 2026, all for versions before 1.5.0.
- Cost at scale
- Free; the costs are model tokens for snapshots and traces and one local Chrome per concurrent session.
- Limits
- Officially supports Google Chrome and Chrome for Testing only; memory and vision tools sit behind flags; the default profile directory can serve only one browser at a time.
What's good
- Performance traces, network, console and heap snapshots in one server
- Built by the Chrome DevTools team, with frequent releases
- Lighthouse audits and source-mapped stack traces
- Attaches to a running Chrome or launches its own
What's not
- Usage statistics sent to Google by default
- Trace URLs may go to the CrUX API unless disabled
- 59 tools in full mode; slim mode keeps only three
- Chrome only; four security advisories in 2026
Best for
Front-end and performance engineers who want an agent to diagnose runtime errors, slow pages and memory leaks in Chrome.
Alternatives
Chrome DevTools MCP: common questions
- Is Chrome DevTools MCP worth it?
- When an agent needs to know why a page is slow or broken, not just click through it, this is the server that can tell it. We rate it 4.6 out of 5.
- How much does Chrome DevTools MCP cost?
- Free and Apache-2.0 licensed. Usage statistics go to Google unless you opt out.
- What are the downsides of Chrome DevTools MCP?
- Usage statistics sent to Google by default; trace URLs may go to the CrUX API unless disabled; 59 tools in full mode; slim mode keeps only three; chrome only; four security advisories in 2026.
- Who is Chrome DevTools MCP best for?
- Front-end and performance engineers who want an agent to diagnose runtime errors, slow pages and memory leaks in Chrome.
- How much does Chrome DevTools MCP cost for a team or in production?
- Free; the costs are model tokens for snapshots and traces and one local Chrome per concurrent session.
- Is Chrome DevTools MCP safe for company data?
- Exposes everything in the browser profile to the MCP client. Usage statistics go to Google by default, trace URLs may go to CrUX, and four medium-severity advisories were published in 2026, all for versions before 1.5.0.
- What are the best Chrome DevTools MCP alternatives?
- The closest alternatives we have reviewed are Playwright MCP and Browserbase MCP.
Answers checked Oct 22, 2026.
Make Chrome DevTools MCP? Show this rating on your site
