Chrome DevTools MCP, verified

Claude Code

1. Run this in a terminal, in your project folder:

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

1. Start Claude Code and type /mcp. chrome-devtools should show as connected.

Add --scope user to make it available in every project.

Claude Desktop

1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:

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

1. Save the file and restart Claude Desktop.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Add to Cursor (opens in a new tab)

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

Needs Node.js on your computer.

VS Code

Install in VS Code (opens in a new tab)

Or from a terminal:

code --add-mcp '{"name":"chrome-devtools","type":"stdio","command":"npx","args":["-y","chrome-devtools-mcp@latest"]}'

Or commit it to the repo in .vscode/mcp.json:

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

Needs Node.js on your computer.

Devin Desktop

1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):

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

1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest

Or edit ~/.codex/config.toml directly:

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

Needs Node.js on your computer.

Gemini CLI

gemini mcp add chrome-devtools npx -- -y chrome-devtools-mcp@latest

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

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

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer.

README badge

[![Chrome DevTools MCP on mcp.tc](https://mcp.tc/i/chrome-devtools/badge.svg)](https://mcp.tc/i/chrome-devtools)

<a href="https://mcp.tc/i/chrome-devtools"><img src="https://mcp.tc/i/chrome-devtools/badge.svg" alt="Chrome DevTools MCP on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

<script src="https://mcp.tc/w/chrome-devtools.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

<iframe src="https://mcp.tc/embed/chrome-devtools" title="Chrome DevTools MCP on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/chrome-devtools.json

What each field means