Chrome DevTools MCP
An open source MCP server that connects coding assistants to local Chrome for browser automation, debugging and performance analysis. Apache 2.0 licensed.
Chrome DevTools MCP gives AI coding assistants access to a live Chrome browser through a locally running MCP server. It's for developers who want their agent to inspect how a web app behaves, investigate errors and measure performance alongside its coding work. It works with clients such as Claude Code, Cursor, Copilot and Antigravity.
The agent can inspect network requests, capture screenshots and read console messages with stack traces mapped back to source code. Performance tools record Chrome DevTools traces and extract findings that help identify slow page behavior. Puppeteer handles browser actions and waits for their results, so an agent can interact with a page and examine what happened afterward.
The project is open source under Apache 2.0 and runs with Node.js and Chrome. It officially supports Google Chrome and Chrome for Testing. A separate CLI provides access without MCP. It can connect to an existing Chrome session, retain browser profiles across sessions and debug Chrome on Android.
Local execution doesn't make browser data private from the connected assistant: MCP clients can inspect and modify content in the browser and DevTools. Google collects usage statistics by default, and performance tools may send trace URLs to the Google CrUX API to retrieve real-user performance data. Both forms of data collection can be disabled, as can the server's periodic checks of the npm registry for updates.
