chrome-devtools-mcp

What it does

Chrome DevTools for Agents is an MCP server that lets AI assistants control and inspect live Chrome browser instances using Puppeteer. It wraps Chrome's DevTools protocol to provide automation, debugging, and performance analysis. The server exposes capabilities for recording performance traces, analyzing network requests, taking screenshots, and inspecting console output with source-mapped stack traces.

Who it's for

Frontend developers and QA engineers automating browser testing with Claude or other AI assistants. Also useful for performance engineers analyzing page metrics within agent-driven workflows.

Common use cases

• Automate end-to-end browser testing by navigating pages and validating state
• Record and analyze performance traces to extract actionable insights
• Debug network requests and console errors in agent workflows
• Take screenshots and analyze visual state changes
• Correlate lab performance metrics with real-user data (CrUX)

Setup pitfalls

• Requires Chrome or Chrome for Testing; other Chromium variants are unsupported and may fail unexpectedly
• One secret detected in the repository—review before enabling in CI/CD
• Usage statistics and update checks are enabled by default; disable with --no-usage-statistics and CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS for offline or privacy-sensitive environments
• Exposes all browser data to MCP clients and sends performance traces to Google CrUX API; disable CrUX with --no-performance-crux and avoid tabs with sensitive information