Chrome DevTools MCP
The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
- 54,432 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The agent can see and modify any data in the browser
- Launches Chrome and uses the network, sends usage statistics to Google by default
Install
- Works in
Manual install
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}Add --slim and --headless for basic tasks without a browser window.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent can see and modify any data in the browser
- Launches Chrome and uses the network, sends usage statistics to Google by default
This is third-party code. Review the repository files before installing.
What it does
The server gives the agent a real Chrome browser through Puppeteer and the DevTools protocol. The agent opens pages, clicks, fills forms, takes screenshots and accessibility tree snapshots. It reads network requests and console messages with source-mapped stack traces, records traces and extracts performance insights, and runs Lighthouse. A bundled plugin adds skills for accessibility, LCP, memory leak and cookie debugging, plus a CLI for use without MCP.
Who it is for. For frontend developers and QA engineers who want the agent to check and debug pages in a real browser.
Good fit when
- The agent changed markup and should verify the page works
- You need to analyze slow loading or poor LCP from a trace
- You need to find console errors or failed network requests
- You need an accessibility audit of a page
Not a fit when
- You need cross-browser tests in Firefox or Safari
- The browser profile holds data the model must not see
Example request
Open localhost:3000, check the console for errors and measure the home page performanceMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS- Disables usage statistics collection
CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS- Disables npm update checks
Limitations
Only Google Chrome and Chrome for Testing are officially supported. Requires Node.js LTS and Chrome. Google collects usage statistics by default (disable with --no-usage-statistics), and performance tools may send URLs to the CrUX API (disable with --no-performance-crux). All browser content is exposed to the MCP client.
How to disable. Remove the server with claude mcp remove chrome-devtools or delete the chrome-devtools block from your MCP config. The plugin is removed via /plugin.
FAQ
What does --slim mode do?
It keeps only the basic tools for simple browser tasks and saves context.
Can it attach to a running Chrome?
Yes, the advanced usage guide covers connecting to a running instance and debugging on Android.
Discussion
No questions or reviews yet.
Related
MCP serversA Python Chrome MCP: the agent connects to Chrome over the DevTools Protocol, reads network, console and cookies, runs JavaScript and takes page metrics
A Claude Code plugin that drives your Chrome over the DevTools Protocol: tabs, forms, page extraction and screenshots with no third-party dependencies
A Chrome extension with an MCP server: the agent drives your everyday browser with its sessions, tabs, bookmarks and history
An MCP server and Chrome extension that let the agent drive your already open browser with your logged-in sessions, all locally
A CLI, skill and MCP server for driving Chrome with short Puppeteer scripts, with tabs that keep state between calls
A skill for Amp, Claude Code and Cursor: the agent drives your live Chrome with its open tabs and signed-in accounts through a single debugging toggle
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Chrome DevTools MCP (this entry) | yes | not required | 54,432 | |
| Modern Web Guidance | yes | 2,573 | chrome team skills | |
| AXI | no | 2,259 | ten design principles for CLIs that agents use | |
| Vibium | no | 2,934 | one binary for agent browser automation |
README in short
The README explains that the server drives Chrome via Puppeteer and gives the agent performance traces, network, console and screenshots. Setup is a config block with npx chrome-devtools-mcp@latest, with a separate guide per client. Google usage statistics and CrUX lookups are disclosed along with opt-out flags. There is a --slim mode, a CLI and guidance on embedding it as a browser subagent.