Skip to content
MCP server

Chrome DevTools MCP

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

Runs locallyActively maintainedStatus and history

The repository was last updated 56 days ago and is published under Apache-2.0.

Install
Pricing
Open source
Platforms
CLI, API, macOS
Runs
Locally
GitHub stars
0
Last commit
2 months ago
Language
TypeScript

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 an MCP server that connects coding assistants such as Claude, Cursor or Copilot to a running Chrome instance. Once connected, the agent can click, type, navigate, take screenshots and read console output, using Puppeteer for the browser actions.

Beyond automation, the server exposes Chrome DevTools features: recording performance traces with extracted insights, listing network requests, pulling source-mapped console messages, and taking heap snapshots for memory debugging. A slim mode limits the set to three tools for basic navigation and screenshots.

It suits developers who want an assistant to verify front-end behaviour or investigate performance problems in the browser they already use. The README warns that anything in the browser, including sensitive data, becomes visible to the connected client, and it notes that the performance tools may send trace URLs to the Google CrUX API unless disabled.

Install

Run in a terminal

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

Add to claude_desktop_config.json

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

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

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

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

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

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

Tools this server provides (10)

Taken from the project documentation; the running server may differ.

click
Clicks an element on the page.
navigate_page
Navigates the selected page to a URL.
take_screenshot
Captures a screenshot of the page.
take_snapshot
Takes a snapshot of the page content.
evaluate_script
Runs a script in the page.
list_network_requests
Lists network requests made by the page.
list_console_messages
Lists console messages from the page.
performance_start_trace
Starts recording a performance trace.
performance_stop_trace
Stops the performance trace recording.
lighthouse_audit
Runs a Lighthouse audit on the page.

What it does

Performance trace analysis
Records Chrome traces and returns actionable performance insights for a page.
Browser automation
Clicks, fills forms, navigates and waits for results through Puppeteer.
Network and console inspection
Lists network requests and reads console messages with source-mapped stacks.
Screenshots with size controls
Captures screenshots with format, quality and maximum size options to limit context use.
Connect to running Chrome
Attaches to an existing debuggable Chrome instance via browser URL, WebSocket or auto-connect.
Slim tool mode
Exposes a reduced set of three tools for basic browsing tasks.

Good for

  • Checking the performance of a web page from inside a coding assistant
  • Debugging front-end errors by reading console output and network requests
  • Automating a browser session to reproduce a bug or test a flow
  • Investigating memory use with heap snapshot tools

Pricing

Open source

Apache-2.0 licensed npm package; no paid plan mentioned.

Chrome DevTools MCP FAQ

Which browsers are supported?

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

Does it send usage data?

Yes, usage statistics are enabled by default and can be turned off with the --no-usage-statistics flag or the CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS environment variable.

What Node.js requirement is there?

The README asks for the current Node.js LTS version, plus a current stable Chrome and npm.

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

What are the best alternatives to Chrome DevTools MCP?

The closest alternatives to Chrome DevTools MCP are Brave DevTools MCP, Selenium MCP, Selenium Webdriver MCP, MCP Browser Extension and MCP Server 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