# Chrome DevTools MCP

Canonical: https://cqbase.net/en/entry/chrome-devtools-mcp
Chinese: https://cqbase.net/zh/entry/chrome-devtools-mcp
English: https://cqbase.net/en/entry/chrome-devtools-mcp

> Gives a coding agent Chrome DevTools so it can inspect a running page.

ChromeDevTools/chrome-devtools-mcp is an Apache-2.0 MCP server that exposes Chrome DevTools to a coding agent. The agent can look at a real page instead of guessing layout from HTML alone.

Use it when a frontend change depends on the console, network, or performance data. Enable it locally against pages you own. Do not point it at an admin site you are not allowed to operate.

## What problem it solves

Chrome DevTools MCP — the package is `chrome-devtools-mcp`, and official docs also call it Chrome DevTools for agents — lets a coding agent control and inspect a live Chrome browser. It can automate a page, debug it, and record a performance trace with real DevTools data, instead of asking the model to guess what the page looks like.

Official docs ship both an MCP server and a CLI. This page focuses on MCP in Claude Code and Cursor. Connecting to the server does not start Chrome by itself. The browser starts when the agent actually calls a tool that needs one.

## Who it is for

It is for people who already use an MCP-capable coding agent and need to inspect a real page, record performance, or debug front-end issues. You need current stable Chrome, plus the latest Node.js LTS and npm. Official support covers Google Chrome and Chrome for Testing only. Other Chromium-based browsers “may work, but this is not guaranteed.”

The project is open source under Apache-2.0, and the official getting-started config does not ask for a separate API key. It does expose browser content to the agent. Official docs warn you not to attach it to a signed-in session that holds sensitive data. Google collects usage statistics such as tool success rates by default; pass `--no-usage-statistics` to opt out. That collection is separate from Chrome’s own metrics.

## How to install it

Checked on 15 November 2026 (Asia/Shanghai) against the repository README, the [client configuration guide](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/client-configurations.md), and [Chrome’s own getting-started page](https://developer.chrome.com/docs/devtools/agents/get-started). The standard config is:

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

In Cursor, open Cursor Settings → MCP → New MCP Server and paste that config.

In Claude Code, to add the MCP server only, run this in your terminal:

```bash
claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest
```

To install the MCP server plus skills as a plugin:

```text
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp
/plugin install chrome-devtools-mcp@chrome-devtools-plugins
```

Official docs say: if you already had this MCP server in Claude Code, remove it from your config before installing the plugin. Restart afterward, and check with `/skills`. If plugin install fails with `Failed to clone repository`, see the pitfalls below, or use `claude mcp add` instead (that path does not include the bundled skills).

## A worked example

The official prompt for checking the setup is: `Check the performance of https://developers.chrome.com`. This review did not run it, so the page does not invent trace numbers or a screenshot.

1. Confirm current stable Chrome and Node.js LTS are installed, and finish the client setup above.
2. Send that official prompt in your agent.
3. Official docs say the client should open a browser and record a performance trace. The window appears only when the agent calls a tool that needs a browser, not merely because the MCP server is connected.
4. Confirm the page and trace yourself. Do not record results that were not observed, and do not run this against a browser profile where you are signed into personal or work accounts.

## Common pitfalls

- The agent can see whatever the browser can see. Official security notes say the agent can read, inspect, debug, and change data in the browser. Do not point it at an already signed-in personal or work session.
- The plugin cannot clone the repository. Official troubleshooting records `Failed to clone repository` when the environment cannot reach `github.com` on port 443. The documented options are to send GitHub HTTPS URLs over SSH, or to install with `claude mcp add`, which does not need a git clone.
- Chrome is missing in WSL. Official troubleshooting says you need Chrome inside the Linux environment. Launching the Windows browser from WSL currently fails because of a known issue, [WSL #14201](https://github.com/microsoft/WSL/issues/14201). Related discussion is in [chrome-devtools-mcp#131](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/131).
- Windows cannot find `chrome.exe`. [Issue #148](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/148) reported discovery failures on 64-bit Windows. Confirm you are using officially supported Chrome, not an unsupported Chromium shell.
- Claude Code cannot connect. [Issue #182](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/182) covers connection failures. Check `claude mcp list` or `/mcp`, and confirm Node and Chrome meet the requirements.

## FAQ

### Do I need an API key?

The official getting-started config does not ask for a separate API key. You need Chrome, Node.js LTS, and an MCP client. Usage statistics are on by default; pass `--no-usage-statistics` to opt out.

### Can I use Edge or Arc?

Official support is limited to Google Chrome and Chrome for Testing. Other Chromium-based browsers may work, but that is not guaranteed.

### Why is there no window after I connect?

Official docs say connecting to the MCP server does not start the browser. Chrome starts when the agent calls a tool that needs one.

### Do I have to install the skills?

No. `claude mcp add` or the standard JSON installs the MCP server only. The plugin also installs skills. Skills need to stay in sync with the server version, or they may describe tools or parameters that have changed.

### The plugin install fails on a corporate network. What then?

If the error is that `github.com:443` cannot be reached, follow the official troubleshooting workarounds: SSH instead of HTTPS, or `claude mcp add`. This page does not describe network workarounds beyond those docs.

## Sources and license

[ChromeDevTools/chrome-devtools-mcp](https://github.com/ChromeDevTools/chrome-devtools-mcp) is licensed under Apache-2.0. This page follows the README, client configuration guide, [troubleshooting doc](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/troubleshooting.md), and [Chrome for Developers getting-started page](https://developer.chrome.com/docs/devtools/agents/get-started) as of 15 November 2026, rewritten for CQBase — Context & Query Base. If the install commands change, follow the repository and official docs.

## Catalog record

- Author: ChromeDevTools
- License: Apache-2.0
- Source: https://github.com/ChromeDevTools/chrome-devtools-mcp
- Added: 2026-11-15
- GitHub stars: 56538 (captured 2026-11-15)

