Skip to content
MCP server

Chrome DevTools MCP

MCP server and CLI that let coding agents drive and inspect a live Chrome browser

Runs locallyActively maintainedStatus and history

The repository was last updated yesterday and is published under Apache-2.0.

Install
Pricing
Open source
Platforms
CLI, macOS, Windows
Runs
Locally
GitHub stars
58.1K
Last commit
1 day ago
Language
TypeScript

Similar MCP servers

About Chrome DevTools MCP

Chrome DevTools MCP is an open-source MCP server for browser automation. It runs locally on your machine and is started by your AI client.

The README describes it as a bridge between a coding assistant and a running Chrome instance, offered both as an MCP server and as a companion command-line tool called chrome-devtools. Agents can navigate pages, take screenshots, read console messages and network requests, and record performance traces using Chrome DevTools internals, with Puppeteer handling the browser actions and waiting for results.

The package ships with a set of skills that teach an agent how to use it for accessibility audits, cookie and session debugging, Largest Contentful Paint work, and memory leak hunts. Plugin installs are available for Claude Code, VS Code Copilot and Gemini CLI, and the server can be started in a slim mode that exposes fewer tools.

It suits developers who want their coding agent to verify its own front-end work in a real browser. The README warns that connected clients can read and modify anything in the browser, so it should not be pointed at sessions holding sensitive data. Usage statistics collection is on by default and can be disabled with a flag.

Install

Run in a terminal

claude mcp add chrome-devtools-mcp -- npx -y chrome-devtools-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "chrome-devtools-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp"
      ]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

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

Add to your client's MCP settings (most use this shape)

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

Using several servers? Build one config file with the MCP config generator.

What it does

Performance trace analysis
Records Chrome traces and extracts performance insights for the agent to act on.
Browser debugging access
Inspects network requests, console messages with source-mapped stacks, and screenshots.
Puppeteer-based automation
Drives Chrome actions and waits for their results before the agent continues.
Bundled agent skills
Ships skills for accessibility, cookies, LCP, memory leaks and connection troubleshooting.
CLI companion
A chrome-devtools command-line tool lets scripts control the browser without MCP.
Slim tool mode
A reduced tool set is available for basic browser tasks.

Good for

  • Checking that a freshly built page renders and behaves correctly in Chrome
  • Running Lighthouse accessibility and SEO audits from a coding assistant
  • Finding memory leaks or slow loads in a live web application
  • Debugging browser extensions or cookie and session problems
  • Scripting browser checks from a terminal with the CLI

Pricing

Open source

Free and open source under Apache-2.0.

Prices change. Check developer.chrome.com before you buy.

Chrome DevTools MCP FAQ

Which browsers does it support?

The README says it officially supports Google Chrome and Chrome for Testing only; other Chromium browsers may work without guarantees.

How do I install it in Claude Code?

Add the marketplace with /plugin marketplace add ChromeDevTools/chrome-devtools-mcp, then run /plugin install chrome-devtools-mcp@chrome-devtools-plugins.

Does it send data to Google?

Usage statistics are collected by default, covering tool success rates, latency and environment information. They can be disabled with --no-usage-statistics. Performance tools may also send trace URLs to the CrUX API unless --no-performance-crux is set.

Is Chrome DevTools MCP free?

Yes. Chrome DevTools MCP is open source, so you can use and self-host it for free.

How do I add Chrome DevTools MCP to Claude Code?

Run this command in your terminal: claude mcp add chrome-devtools-mcp -- npx -y chrome-devtools-mcp

What are the best alternatives to Chrome DevTools MCP?

The closest alternatives to Chrome DevTools MCP are REA, Browser Use, Scrapling MCP Server, Context7 and Codebase Memory.

Where this comes from

  • Description: written from the project's README, the project's website and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers