Chrome DevTools MCP

What the Chrome DevTools MCP MCP server does

The Chrome DevTools MCP MCP server connects an MCP client to a live Chrome browser and exposes browser control, inspection, debugging, and performance functions. Agents can open and manage pages, navigate to URLs, interact with page elements, and inspect results from the browser session.

It is intended for coding agents that need more than static code analysis. Typical tasks include reproducing a user flow, checking console output, examining requests, capturing a page image, evaluating JavaScript, or collecting performance data from a real browser.

How it works

The server runs as a local MCP process, normally started with npx, and communicates with the configured MCP client over standard input and output. Puppeteer handles browser automation and waits for action results. Chrome DevTools supplies tracing, performance insights, console details, and network information.

The Chrome DevTools MCP MCP server officially supports Google Chrome and Chrome for Testing. It can connect to an existing browser through a browser URL, including a browser supplied by another client, rather than always launching its own instance.

Setup and configuration

Node.js LTS, npm, and a current stable Chrome version or newer are required. A standard client configuration starts the server with:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["-y", "chrome-devtools-mcp@latest"]
    }
  }
}

Add --slim for a smaller tool set intended for basic browser tasks. The example --headless option can be used with slim mode. When connecting to an already-running browser, pass --browser-url with its debugging endpoint.

Usage statistics are enabled by default. Set CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or run with --no-usage-statistics to disable collection. Set CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS to turn off periodic npm update checks. Performance features may use Google’s CrUX API; --no-performance-crux disables that lookup.

Tools and capabilities

Available tools cover these areas:

• Browser interaction: click, drag, hover, fill forms, type text, press keys, upload files, handle dialogs, and click at coordinates.
• Page management: create, close, list, select, and navigate pages; wait for conditions; resize or emulate browser settings.
• Debugging: evaluate scripts, list or retrieve console messages, list network requests, and retrieve an individual request.
• Performance: start and stop traces, analyze performance insights, and run Lighthouse audits.
• Observation: take screenshots, take page snapshots, and start a screencast.

Limitations and notes

Browser contents are exposed to the MCP client, which can inspect, debug, and modify data in the browser or DevTools. Avoid using the server with sensitive information that should not be shared with the client.

Other Chromium-based browsers may work, but they are not officially supported and can behave unexpectedly. The project targets the latest Extended Stable Chrome. Usage-statistics collection is separate from Chrome’s own metrics, and setting CI also disables this server’s collection.

The Chrome DevTools MCP MCP server can be installed for clients such as Claude Code, Cline, Codex, Cursor, and VS Code. Claude Code also has a plugin installation path that bundles the server with skills.