Chrome DevTools MCP

Lets a coding agent control and inspect a live Chrome browser through DevTools.

Official
Local
stdio
v1.10.1

Official: the MCP registry verified that the publisher controls the GitHub account ChromeDevTools, which this server's name is under. Source: MCP registry, checked 2026-09-25.

Repository

How to connect

Your client starts the npm package with npx, which needs Node.js. Some servers also need an API key or arguments; the repository's README says which.

Terminal

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

~/.cursor/mcp.json

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

~/.codex/config.toml

[mcp_servers.chrome-devtools]
command = "npx"
args = ["-y", "chrome-devtools-mcp"]

Syntax from each client's docs, checked 2026-09-25: Claude Code, Cursor, Codex.

Details

Official: Yes
Runs: Local
Transport: stdio
Installs from: npm
Registry version: 1.10.1
License: Apache-2.0
Registry name: io.github.ChromeDevTools/chrome-devtools-mcp
Repository: ChromeDevTools/chrome-devtools-mcp
npm package: chrome-devtools-mcp

Remote, local, transport and packages are read off the registry's platforms. Sources: GitHub, checked 2026-09-25; MCP registry, checked 2026-09-25.

Maintenance

Counts as checked on the day shown. Not a rating.

129 contributors on GitHub as of 2026-09-25.
1,026,016 downloads on npm in the 7 days to 2026-09-25.

Also by Google15

All 16 by Google

Friday

The brief, by email

Five to seven links an issue, each with what to do about it.

Unsubscribe from any issue.

This page as Markdown