MCP serverPartly tested (needs an account)
Check your site in Chrome
Chrome DevTools MCP
The Chrome DevTools team's MCP server. Your agent can open a page in Chrome, read errors, record performance and run Lighthouse checks.
- Works with
- Claude Code, Codex CLI, Gemini CLI
- Good for
- Web developers, Build an app
What it does
What it is
Chrome DevTools is the panel that web developers use to find errors and slow parts of a page. This MCP server gives the same powers to your AI agent: it can open a page, read console errors, look at network traffic, record a performance trace and run a Lighthouse check.
Who it helps
Web developers and site owners who want the agent to find why a page is slow or broken.
How to start
Install the server. Open your own site and ask: "What errors show in the console? What makes the first load slow?"
Be careful
The tool controls a real browser, so use a fresh profile. It sends usage statistics to Google unless you turn them off with a flag.
How to install
claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latestHow to use it
Ask the agent to check a page, for example "open localhost:3000, list console errors and tell me why it loads slowly". It uses the same tools as Chrome DevTools.
What to watch out for
- It controls Chrome and can read page content, cookies in the browser it controls, and network traffic. Use a fresh browser profile.
- By default it sends usage statistics to Google. Add the flag --no-usage-statistics to the command to turn that off. Our test used that flag.
- Some checks send page addresses to Google's field-data service. Read the README option list if you test private pages.
Licence and author
- Licence
- Apache-2.0
- Author
- Chrome DevTools team (Google)
How we tested it
We installed it on an empty test computer on 12 Oct 2026. Partly tested: installed in a clean test system, but its main features need an account or key we did not use.
The server starts without Chrome, but you need Chrome on your computer to use it. The test registered the server with a slightly different form of the command (with -y and the --no-usage-statistics flag), not the README line shown above.
Technical details of the test
- Date
- 12 Oct 2026
- Method
- In a clean container with no account we started npx -y chrome-devtools-mcp@latest --no-usage-statistics, sent the MCP initialize and tools/list requests, and it answered with 30 tools. We also registered it with claude mcp add, and claude mcp list reported it as connected. Chrome was not installed in the container, so no page was opened.
Checked again on 12 Oct 2026
Sources
- github.com/ChromeDevTools/chrome-devtools-mcp