What does chrome-devtools-mcp do?

It lets a coding agent control and inspect a live Chrome browser, including recording performance traces, analyzing network requests, reading console messages, and automating browser actions.

Does it automate the browser?

Yes, browser actions are automated using Puppeteer.

Can it help debug JavaScript errors?

It can check console messages and reports them with source-mapped stack traces.

chrome-devtools-mcp

PackWeb & browsing

chrome-devtools-mcp is a plugin that lets a coding agent control and inspect a live Chrome browser. It supports chrome ai integration by giving the agent access to performance traces, network requests, console messages with source-mapped stack traces, and browser automation through Puppeteer.

Unavailable. A Claude Code plugin. It installs in Claude Code, and ahel does not serve packs through its connector yet.

In Claude Code, run:

/plugin install chrome-devtools-mcp@claude-plugins-official

It installs from Anthropic's official plugin marketplace.

What your AI can do with it

Control and inspect a live Chrome browser from the agent
Record performance traces for analysis
Analyze network requests
Check console messages with source-mapped stack traces
Automate browser actions with Puppeteer

Getting started

Have a coding agent that can load plugins.
Have a Chrome browser available on the machine.
Add chrome-devtools-mcp to the agent's configuration.
Ask the agent to inspect pages, record traces, or automate browser actions.

Signals

GitHub stars: 53k
Forks: 5k
Last commit: Sep 2026

What people say

Users praise chrome-devtools-mcp for letting coding agents like Claude Code debug web apps in a live Chrome browser, with one calling it their favorite MCP server. The main recurring complaint is its high token consumption (~18K tokens per use) compared to alternatives.

Praised for: Lets agents debug in a real browser (console, network, perfo; Easy setup with Claude Code; Free and open-source

Complaints: High token usage (~18K tokens)

X@MaximeRivest X@ChromiumDev X@JeffDean X@ChromiumDev X@dani_avila7 X@ChromiumDev

Summarized from 23 public posts. Opinions are theirs, not ahel's.

Questions

What does chrome-devtools-mcp do?: It lets a coding agent control and inspect a live Chrome browser, including recording performance traces, analyzing network requests, reading console messages, and automating browser actions.
Does it automate the browser?: Yes, browser actions are automated using Puppeteer.
Can it help debug JavaScript errors?: It can check console messages and reports them with source-mapped stack traces.

Advanced

Item type: plugin
Key: chrome-devtools-mcp
Source: github.com/chromedevtools/chrome-devtools-mcp

github.com/chromedevtools/chrome-devtools-mcp