MCP server Official

Chrome DevTools MCP

Lets your coding agent control and inspect a live Chrome browser: performance traces, network, console, screenshots, automation.

Author: Chrome DevTools (Google)
Works with: Any MCP client, Claude Code, Cursor
License: Apache-2.0
Documented: Oct 2, 2026

Repository ↗ Official docs ↗ Registry ↗

What Chrome DevTools MCP is

chrome-devtools-mcp is an MCP server that gives coding agents access to Chrome DevTools for automation, debugging and performance analysis. It uses puppeteer for reliable automation. A CLI is also provided for use without MCP.

What it does

Where Chrome DevTools MCP runs and what it adds, from its documentation

Record performance traces and extract insights
Analyze network requests and read console messages with source-mapped stack traces
Take screenshots
Automate Chrome actions via puppeteer with automatic waiting
Slim mode for basic browser tasks (--slim)

When to use it

Good fit

Debugging a web page's performance with an agent
Letting an agent verify UI changes in a real browser
Inspecting console and network errors

Not for

Non-Chrome browsers (only Chrome and Chrome for Testing officially supported)
Sessions holding sensitive data you do not want exposed to the MCP client

How to install Chrome DevTools MCP

You need: Node.js LTS; Chrome current stable or newer; npm

Ensure Node.js LTS, npm and current stable Chrome are installed
Add the config to your MCP client
See the client configurations guide for Claude Code, Cursor, VS Code
Test with: Check the performance of https://developers.chrome.com

Configuration example (from the official docs)

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

Permissions and security

What it can access

Inspect, debug and modify any data in the controlled browser instance or DevTools

Security notes from the maintainers

Avoid sharing sensitive info with MCP clients
Performance tools may send trace URLs to Google CrUX API; disable with --no-performance-crux
Usage statistics on by default; opt out with --no-usage-statistics or CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS/CI env; update checks disabled via CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS

Review the source before granting an agent access to credentials or production systems. We document what the maintainers state; we do not audit code.