chrome-devtools-mcp README

The project's README from github.com/ChromeDevTools/chrome-devtools-mcp. As one markdown file: README.md.

Chrome DevTools for agents

npm chrome-devtools-mcp package

Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis. A CLI is also provided for use without MCP.

Tool reference | Changelog | Contributing | Troubleshooting | Design Principles

Key features

Disclaimers

chrome-devtools-mcp exposes content of the browser instance to the MCP clients allowing them to inspect, debug, and modify any data in the browser or DevTools. Avoid sharing sensitive or personal information that you don't want to share with MCP clients.

chrome-devtools-mcp officially supports Google Chrome and Chrome for Testing only. Other Chromium-based browsers may work, but this is not guaranteed, and you may encounter unexpected behavior. Use at your own discretion. We are committed to providing fixes and support for the latest version of Extended Stable Chrome.

Performance tools may send trace URLs to the Google CrUX API to fetch real-user experience data. This helps provide a holistic performance picture by presenting field data alongside lab data. This data is collected by the Chrome User Experience Report (CrUX). To disable this, run with the --no-performance-crux flag.

Usage statistics

Google collects usage statistics (such as tool invocation success rates, latency, and environment information) to improve the reliability and performance of Chrome DevTools MCP.

Data collection is enabled by default. You can opt-out by passing the --no-usage-statistics flag when starting the server:

"args": ["-y", "chrome-devtools-mcp@latest", "--no-usage-statistics"]

Google handles this data in accordance with the Google Privacy Policy.

Google's collection of usage statistics for Chrome DevTools MCP is independent from the Chrome browser's usage statistics. Opting out of Chrome metrics does not automatically opt you out of this tool, and vice-versa.

Collection is disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.

Update checks

By default, the server periodically checks the npm registry for updates and logs a notification when a newer version is available. You can disable these update checks by setting the CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS environment variable.

Requirements

Getting started

Add the following config to your MCP client:

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

[!NOTE] Using chrome-devtools-mcp@latest ensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.

If you are interested in doing only basic browser tasks, use the --slim mode:

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

See Slim tool reference.

MCP Client configuration

For setup instructions specific to your editor or agent (e.g. Antigravity, Claude Code, Cursor, VS Code), please see our Client Configurations Guide.

Your first prompt

Enter the following prompt in your MCP Client to check if everything is working:

Check the performance of https://developers.chrome.com

Your MCP client should open the browser and record a performance trace.

[!NOTE] The MCP server will start the browser automatically once the MCP client uses a tool that requires a running browser instance. Connecting to the Chrome DevTools MCP server on its own will not automatically start the browser.

Tools

If you run into any issues, checkout our troubleshooting guide. See the full Tool Reference for a complete list of all supported MCP capabilities.

Configuration

Find the complete list of server parameters (e.g., --headless, --isolated, --slim) and how to configure WebSocket connections in the Configuration Guide.

Advanced Usage

For advanced features such as handling concurrent sessions, persistent user data directories, connecting to a running Chrome instance instead of starting a new one, or debugging on Android, see our Advanced Usage Guide.

Integrating as a browser subagent

If you are developing agentic tooling and want to provide an integrated browser subagent as part of your product, we recommend building on top of Chrome DevTools for agents.

For a reference implementation, see the Gemini CLI browser agent documentation.

chrome-devtools-mcp (ChromeDevTools/chrome-devtools-mcp)

Searching Database…

53.7K ·GitHub
Chrome-devtools-mcp
What is this?chrome-devtools-mcp is an MCP server that lets coding agents like Claude, Cursor, Copilot or Antigravity control and inspect a live Chrome browser using the full power of Chrome DevTools.
Is this a library I import, or a standalone server?It's an MCP server (plus a standalone CLI) that your MCP client connects to; it's not a library you import into app code.
How do I add it to my MCP client?Add chrome-devtools-mcp@latest as a server entry in your MCP client's config (Antigravity, Claude Code, Cursor, VS Code, etc.), following the Client Configurations Guide, then just prompt your agent to use it.
What do I need installed before running this?You need a Node.js LTS version, a current stable (or newer) Chrome browser, and npm.
Does it work with any Chromium browser, or just Chrome?It officially supports only Google Chrome and Chrome for Testing; other Chromium-based browsers might work but aren't guaranteed.
What can it actually do once connected?It records performance traces and extracts actionable insights, analyzes network requests, takes screenshots, reads console messages with source-mapped stack traces, and automates browser actions reliably via Puppeteer with automatic waiting.
Is there a lighter mode if I only need basic automation?Yes, running with the --slim flag enables a reduced tool set for basic browser tasks, documented in the Slim Tool Reference.
Can it connect to a browser I already have running instead of launching a new one?Yes, the Advanced Usage Guide covers connecting to an already-running Chrome instance, persistent user data directories, concurrent sessions, and debugging on Android.
How do I turn off the telemetry and update checks?Pass --no-performance-crux and --no-usage-statistics flags at startup, or set the CHROMEDEVTOOLSMCPNOUPDATECHECKS environment variable to stop version-check notifications; collection is also disabled automatically in CI.
What are similar projects?moli, dev-browser, bb-browser, claude-code, browser, chromedp, playwright-cli, XActions
Which topics is it in?puppeteer, chrome, devtools, debugging, browser-automation, testing, browser, monitoring, mcp-server, performance, agent, mcp
Creator
ChromeDevTools
Size
21.6 MB
Stars
53.7K
Updated
CommitOct 16Releasechrome-devtools-mcp-v1.11.0Oct 15
Age
1y
Commits · 90 Days