What Chrome DevTools MCP actually does

Chrome DevTools MCP is Google's local browser server for coding agents. It starts or attaches to a real Chrome window and exposes DevTools: performance traces, network and console, screenshots, and Puppeteer-backed clicks and fills. The agent sees a live page the way a developer would in DevTools, not a static HTML dump.

This week it is still climbing. Appsgit's MCP trending list for 30 Oct to 6 Nov 2026 lists Chrome DevTools MCP among the weekly star gainers. On PlugMCP the listing is under browser automation, publisher ChromeDevTools, transport stdio, status local.

What it is good for

Use it when the job is debugging or measuring a real Chrome page: Largest Contentful Paint and other performance insights, network waterfalls, console errors with source-mapped stacks, screenshots, or reliable automation that waits for the page the way Puppeteer does.

The npm package is chrome-devtools-mcp (checked at 1.12.0 when this draft was written). The README also ships a chrome-devtools CLI and a set of agent skills for accessibility, cookies, LCP, memory leaks, and setup troubleshooting. Official docs brand the suite as Chrome DevTools for agents.

Google Chrome or Chrome for Testing is the supported browser. Other Chromium builds may work; the README does not guarantee them.

Install in Cursor

Node.js LTS, npm, and a current stable Chrome. In Cursor, open Settings, then MCP, then add a server. Paste this. The publisher README uses @latest; the PlugMCP listing currently pins 1.12.0:

1{
2  "mcpServers": {
3    "chrome-devtools": {
4      "command": "npx",
5      "args": ["-y", "chrome-devtools-mcp@latest"]
6    }
7  }
8}

Connecting alone does not open Chrome. The browser starts when the agent first calls a tool that needs it. A quick check from the docs: ask the agent to check the performance of https://developers.chrome.com. You should see a trace, not an empty tool list.

For basic browser tasks only, the README documents a smaller surface:

1{
2  "mcpServers": {
3    "chrome-devtools": {
4      "command": "npx",
5      "args": ["-y", "chrome-devtools-mcp@latest", "--slim", "--headless"]
6    }
7  }
8}

Install in Claude

Claude Code plugin path from the publisher:

1/plugin marketplace add ChromeDevTools/chrome-devtools-mcp
2/plugin install chrome-devtools-mcp@chrome-devtools-plugins

Or add MCP only, matching the PlugMCP listing pin:

1claude mcp add chromedevtools-chrome-devtools-mcp -- npx -y chrome-devtools-mcp@1.12.0

Claude Desktop uses the same npx plus chrome-devtools-mcp@latest (or @1.12.0) block in claude_desktop_config.json, then fully quit and restart the app.

Gemini CLI and Codex have one-liners in the Chrome get-started guide if that is your client.

Limits to know

• Local stdio. The agent starts a process. The PlugMCP listing is not a remote proxy.
• The agent can read and change anything in the browser session you attach. Do not point it at a profile with mail, banking, or other accounts you would not hand to the agent.
• Usage statistics to Google are on by default. Pass --no-usage-statistics, or set CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS, to opt out.
• Performance tools may call the CrUX API unless you pass --no-performance-crux.
• Skills in the package describe a specific server version. Update skills when you bump the package.

Alternatives on PlugMCP

• Playwright MCP (microsoft-playwright-mcp) when you want Microsoft's accessibility-tree browser loop more than Chrome DevTools traces.
• Scrapling (d4vinci-scrapling) when the work is scrape-and-extract from a local Python process.
• Firecrawl (firecrawl-firecrawl-mcp-server) when you want a remote scrape and search URL rather than a local Chrome.
• Apify (apify-apify-mcp-server) when the work belongs in Apify Actors and a store of managed scrapers, with an API key.

On the PlugMCP page

The listing is chromedevtools-chrome-devtools-mcp. Transport is stdio. Status is local. The install block is the publisher's npx command, currently pinned to [email protected] on the listing and @latest in the README.

Search more browser servers from the directory MCP at https://plugmcp.ai/mcp-server, or open the browser automation category on the site.