Chrome DevTools MCP

What you can do with Chrome DevTools MCP

Chrome DevTools MCP lets a coding agent control and inspect a live Chrome browser through Puppeteer and the DevTools Protocol: record performance traces, read network requests and console messages, take screenshots and automate page actions with automatic waits.

• ·Record a performance trace and extract insights
• ·Inspect network requests and console messages with stack traces
• ·Automate clicks, forms and navigation with auto-waits
• ·Run Lighthouse audits and take screenshots or snapshots
• ·Take and compare heap snapshots to find memory leaks
• ·Attach to your running Chrome with its logins

What Chrome DevTools MCP can and cannot do

What you need before using Chrome DevTools MCP

Runtime

Node.js LTS with npx

Also needed

Chrome current stable or newer (Chrome 144+ for --autoConnect); the browser starts only when a tool needs it

Connect Chrome DevTools MCP and confirm it works

1. Add the server with command npx and args ["-y", "chrome-devtools-mcp@latest"]
2. Optionally add --headless, --slim, --isolated or --channel to the args
3. To drive your own Chrome: enable remote debugging at chrome://inspect/#remote-debugging and add --autoConnect, or start Chrome with --remote-debugging-port=9222 and a custom --user-data-dir and pass --browser-url=http://127.0.0.1:9222

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

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

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

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

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

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

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

When to choose another server

• Playwright MCP Server#10

  You want Playwright's accessibility-snapshot tooling, Firefox/WebKit, or test assertions rather than DevTools panels.

• Browser Devtools MCP#442

  You want Playwright-based page debugging plus Node.js process debugging tools (note: package deprecated).

• SeleniumBase MCP#13

  The target site blocks automation and you need a stealth-focused CDP browser.

Compared side by side in Browser automation MCP servers.

What changed, and when this was checked

First listed

Sep 23, 2025

Latest version published

Oct 15, 2026

Version history

55 versions tracked (below)

Requirements evidence

Declared by Glama, last synced Oct 16, 2026. Not independently verified by MCP Toplist.

Profile checked

Oct 9, 2026 against README, Tool reference, Configuration guide

Ranking data as of

Oct 16, 2026

Do you maintain Chrome DevTools MCP? Claim it to correct or enrich this profile.

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

[![MCP Toplist](https://mcptoplist.com/badge/io.github.ChromeDevTools%2Fchrome-devtools-mcp.svg)](https://mcptoplist.com/server/io.github.ChromeDevTools%2Fchrome-devtools-mcp)

<a href="https://mcptoplist.com/server/io.github.ChromeDevTools%2Fchrome-devtools-mcp"><img src="https://mcptoplist.com/badge/io.github.ChromeDevTools%2Fchrome-devtools-mcp.svg" alt="MCP Toplist: #1 of 144,396" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.