Chrome DevTools MCP

Chrome DevTools MCP connects AI coding assistants to a live Chrome browser through a locally running server. It's for developers who want an agent to investigate web app behavior alongside its coding work.

• Browser automation: Agents can perform browser actions through Puppeteer, which waits for action results before continuing.
• Error investigation: Inspect network requests, capture screenshots and read console messages with stack traces mapped back to source code.
• Performance analysis: Record DevTools traces and extract performance findings; optional Google CrUX lookups add real-user experience data and may send trace URLs to Google.
• Existing browser sessions: Connect to a running Chrome instance, retain browser profiles across sessions or debug Chrome on Android.

The server is open source under Apache 2.0 and requires Node.js, npm and Chrome. It works with assistants such as Claude Code, Cursor, Copilot and Antigravity. A separate CLI provides access without MCP. Official browser support covers Google Chrome and Chrome for Testing; other Chromium browsers aren't guaranteed to work.

Connected assistants can inspect and modify browser content, so running the server locally doesn't keep that content private from the MCP client. Google collects usage statistics by default. CrUX lookups and periodic npm registry update checks can each be disabled.