Chrome DevTools MCP gives a coding agent control over a live Chrome browser. It runs as a Model Context Protocol server, so an agent such as Claude Code, Cursor, Copilot, or Antigravity can drive pages, inspect what happened, and read back DevTools data; a command-line interface covers the same ground without MCP. The browser starts automatically the first time a client calls a tool that needs it, not when the client connects.

Performance work uses Chrome DevTools itself to record traces and extract insights, and debugging covers network requests, screenshots, and console messages with source-mapped stack traces. Actions in the page run through Puppeteer, which waits for the result of each action. A --slim mode exposes a reduced tool set for basic browser tasks, and options such as --headless and --isolated, WebSocket connections, concurrent sessions, persistent user data directories, attaching to an already-running Chrome, and Android debugging are configurable.

Support is limited to Google Chrome and Chrome for Testing; other Chromium-based browsers may work but are not guaranteed. Fixes target the latest Extended Stable Chrome, and Node.js LTS with npm is required. The server exposes browser content to the connected client, which can inspect and modify any data in the browser, so the guidance is to avoid data you do not want that client to see.

Two data flows are on by default and can be turned off: performance tools may send trace URLs to the Google CrUX API for field data, disabled with --no-performance-crux, and usage statistics such as tool success rates, latency, and environment information are collected unless you pass --no-usage-statistics or set the matching environment variable; collection is also skipped when CI is set. Periodic npm update checks can be disabled with an environment variable.

Features

Performance insights: records traces with Chrome DevTools and extracts actionable findings, optionally alongside CrUX field data
Browser debugging: network request analysis, screenshots, and console messages with source-mapped stack traces
Puppeteer automation: page actions that wait for their results instead of racing the page
Slim mode: a reduced tool set for basic browsing, configured through the same client entry
Flexible connection: headless and isolated flags, WebSocket connections, concurrent sessions, persistent profiles, attaching to a running Chrome, and Android targets
CLI surface: the same capabilities without an MCP client
Subagent reference: guidance for embedding it as a browser subagent inside other agentic tooling