[GitHub Trending] ChromeDevTools/chrome-devtools-mcp

7.5 relevance

Chrome DevTools MCP for coding agents, highly novel and actionable for AI-assisted development.

AI/ML github.com

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

For platform engineers building AI agent workflows, this bridges the gap between LLM-driven coding assistants and real browser debugging—critical for automated UI testing, performance regression detection, and observability pipelines in CI/CD.

Key Takeaways

Integrate chrome-devtools-mcp into your MCP client config to give agents direct browser DevTools access, but disable usage statistics with --no-usage-statistics for production or sensitive environments.

Chrome DevTools for coding agents. Contribute to ChromeDevTools/chrome-devtools-mcp development by creating an account on GitHub.

Summary

Google's Chrome DevTools MCP server lets AI coding agents (Antigravity, Claude, Cursor, Copilot) control and inspect a live Chrome browser via the Model Context Protocol, enabling performance tracing, network analysis, and screenshot capture through Puppeteer automation. The server collects usage statistics by default and sends trace URLs to the CrUX API for real-user performance data, with opt-out flags available. It requires Node.js LTS, Chrome stable, and npm, and can be configured as an MCP client or used as a standalone CLI.