Enable coding agents to diagnose performance and errors in a live Chrome browser
This tool helps coding agents identify why web pages are slow or buggy. It is a server that allows AI coding assistants to call Chrome DevTools features directly. It analyzes network requests, console messages, and performance traces while the browser is running and takes necessary actions.
Passing browser data to the agent
The tool is available in two forms: an MCP (Model-Context-Protocol) server and a CLI. The MCP server enables coding agents like Claude, Cursor, and Copilot to check and manipulate the state of a Chrome browser in real time. It uses Puppeteer to automate actions within the browser and waits automatically until results are available. This allows the agent to go beyond writing code to verifying behavior and debugging in an actual browser environment.
Performance tracing and debugging features
It extracts actionable performance insights using Chrome DevTools' performance tracing capabilities. It analyzes network requests, takes screenshots, and checks browser console messages, including stack traces with source maps applied. During performance analysis, it may also call the Google CrUX API to provide real user experience data. This data can be disabled with the --no-performance-crux flag.
Skill set for the agent
The package includes skills that help agents use Chrome DevTools effectively. These include page debugging and automation, fixing accessibility issues, debugging cookies and authentication, LCP (Largest Contentful Paint) optimization, and memory leak detection. These skills can be installed as plugins or copied directly into the agent's skill directory. Since skills describe specific versions of the tool, they must be updated whenever the server or CLI is updated.
Installation and initial setup
Node.js LTS, the latest Chrome stable version, and npm are required. You can add the npx -y chrome-devtools-mcp@latest command to your MCP client configuration. The server automatically starts the browser when a tool that requires it is called. To use the CLI, install it globally with npm i chrome-devtools-mcp@latest -g and run commands in the terminal. Usage statistics collection is enabled by default and can be disabled with the --no-usage-statistics flag or an environment variable.
Security and compatibility checks before use
Because this tool exposes the contents of a browser instance to the MCP client, sensitive information that you do not want to share should not remain in the browser. The officially supported browsers are Google Chrome and Chrome for Testing; operation is not guaranteed for other Chromium-based browsers. Fixes and support are provided for the latest Extended Stable Chrome version. Browser usage statistics and this tool's usage statistics are managed independently, so disabling Chrome metrics does not stop this tool's statistics collection.
