MCP server, by ChromeDevTools (Google Chrome DevTools team)
Chrome DevTools MCP Server
An MCP server that lets coding agents control and inspect a live Chrome browser using Chrome DevTools for automation, debugging, and performance analysis.
Quick facts
What it does
Chrome DevTools for agents (chrome-devtools-mcp) lets a coding agent such as Antigravity, Claude, Cursor, or Copilot control and inspect a live Chrome browser. It acts as a Model Context Protocol server, giving an AI coding assistant access to Chrome DevTools for reliable automation, in-depth debugging, and performance analysis. A CLI is also provided for use without MCP.
Key features from the README are performance insights from recorded traces, advanced browser debugging (network requests, screenshots, and browser console messages with source-mapped stack traces), and reliable automation using puppeteer that waits for action results. Requirements listed are Node.js LTS, Chrome current stable or newer, and npm. The server starts the browser automatically when a client uses a tool that requires a running browser instance.
Configuration
Add the npx config to your MCP client. Using chrome-devtools-mcp@latest ensures the latest version. A slim mode with --slim and --headless is documented for basic browser tasks.
{"mcpServers":{"chrome-devtools":{"command":"npx","args":["-y","chrome-devtools-mcp@latest"]}}}Source: https://github.com/ChromeDevTools/chrome-devtools-mcp. Placeholders only. Replace them in your own environment, and never commit real keys to a repository.
| Environment variable | Required | Purpose |
|---|---|---|
CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS | Optional | Disables usage statistics collection when set, per README. The CI env var also disables collection. |
CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS | Optional | Disables periodic npm registry update checks when set, per README. |
Verified tools and features
Get performance insights Config checked
Uses Chrome DevTools to record traces and extract actionable performance insights, per README Key features.
Advanced browser debugging Config checked
Analyze network requests, take screenshots, and check browser console messages with source-mapped stack traces, per README Key features.
Reliable automation Config checked
Uses puppeteer to automate actions in Chrome and automatically wait for action results, per README Key features.
Security notes
- README disclaimer: chrome-devtools-mcp exposes content of the browser instance to MCP clients, allowing them to inspect, debug, and modify any data in the browser or DevTools. Avoid sharing sensitive or personal information you do not want to share with MCP clients.
- Only Google Chrome and Chrome for Testing are officially supported. Other Chromium-based browsers may work but are not guaranteed.
- Performance tools may send trace URLs to the Google CrUX API unless run with the --no-performance-crux flag. Usage statistics are enabled by default and can be disabled with --no-usage-statistics or the listed env vars.
An MCP server runs with the permissions of the process you start it from. Scope credentials to the narrowest access the job needs, and review what the client will send before connecting anything sensitive.
Sources and freshness
- Official source: https://github.com/ChromeDevTools/chrome-devtools-mcp
- Repository: https://github.com/ChromeDevTools/chrome-devtools-mcp
Last checked 2026-10-07. Verification label: config checked, which means the configuration and feature list trace to the official source above. It does not mean AgentsUse ran the server. Spotted an error? Send a correction. Back to the MCP server index.