Skip to content
MCP server

Chrome DevTools MCP

MCP server that lets AI coding agents drive and inspect a live Chrome browser

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
CLI, API, macOS
Runs
Locally
Version
1.10.1004
Listing updated
today

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 this as a way for coding agents such as Claude, Cursor or Copilot to control and inspect a running Chrome instance. It is offered both as an MCP server and as a companion command-line interface, so the same browser actions can be scripted from a terminal without an AI client.

Once connected, the server starts Chrome when a tool that needs a browser is first called. Its tools cover recording performance traces, reading network requests and console messages with source-mapped stack traces, taking screenshots, and automating page actions through Puppeteer, which waits for results before continuing.

The README warns that connected clients can read and change anything in the browser, so it advises keeping sensitive data out of sessions. It officially supports Google Chrome and Chrome for Testing, and offers flags to disable usage statistics, update checks and CrUX field-data lookups. It is aimed at developers debugging web pages and agents that need a real browser.

Install

Run in a terminal

claude mcp add chrome-devtools-mcp -- npx -y @secforge/chrome-devtools-mcp

Add to claude_desktop_config.json

{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@secforge/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",
        "@secforge/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",
        "@secforge/chrome-devtools-mcp"
      ]
    }
  }
}

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

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

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

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

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

What it does

Performance trace recording
Records Chrome performance traces and extracts performance insights from them.
Network and console inspection
Reads network requests and browser console messages, including source-mapped stack traces.
Screenshots from agents
Captures screenshots of pages so an agent can check visual state.
Puppeteer-based automation
Drives page actions through Puppeteer and waits for each action's result.
Companion CLI
Provides a chrome-devtools command for controlling the browser from a terminal.
Bundled agent skills
Ships skills for debugging accessibility, cookies, LCP and memory leaks.

Good for

  • Letting a coding assistant reproduce and debug a front-end bug in a live page
  • Recording and analysing page performance traces during development
  • Auditing network requests and console errors from an agent-driven session
  • Scripting repeatable browser checks from a shell with the CLI

Pricing

Open source

Free to install from npm; no paid plan mentioned.

Chrome DevTools MCP FAQ

Which browsers are officially supported?

The README says it officially supports Google Chrome and Chrome for Testing only. Other Chromium-based browsers may work but are not guaranteed.

Does the server start Chrome on its own?

It starts the browser automatically once a client calls a tool that needs a running instance. Connecting to the server alone does not start Chrome.

Is usage data collected?

Yes, by default. The README says Google collects usage statistics, which can be turned off with the --no-usage-statistics flag or the CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS environment variable.

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 @secforge/chrome-devtools-mcp

What are the best alternatives to Chrome DevTools MCP?

The closest alternatives to Chrome DevTools MCP are Thinkrun, MCP Browser Extension, Cdpilot, Selenium Webdriver MCP and Agentic Browser.

Where this comes from

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

How AIPoweredBot checks servers