Chrome DevTools MCP server

Installing Chrome DevTools

Runs on demand via npx. Nothing to install globally.

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

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

Not sure where the config file lives, or it isn't picking the server up? Config paths for every client.

What it does

Chrome's official DevTools MCP server lets an assistant inspect the DOM, read console and network activity, and run performance traces against a real browser, so it can debug and verify web pages.

Like any MCP server, Chrome DevTools plugs into MCP-compatible assistants (such as Claude and other clients) so the model can use it as a tool , no custom integration code required.

Related Browser & automation MCP servers

• PlaywrightDrive a real browser to navigate and act.
• PuppeteerAutomate a headless Chrome browser.
• BrowserbaseRun cloud browsers for agents at scale.
• Vibium"Selenium for AI", plain-English, self-healing browser tests.
• ApifyRun web scrapers and automation actors.
• StagehandAutomate browsers using natural language instructions.