[GitHub Trending] ChromeDevTools/chrome-devtools-mcp

8.1 relevance

Chrome DevTools exposed as MCP for coding agents, direct hit to reader's interests.

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 and AI agent builders, this bridges the gap between LLM-driven coding assistants and real browser debugging, enabling reliable end-to-end testing and performance analysis without custom scripting.

Key Takeaways

Integrate chrome-devtools-mcp into your MCP client config to give AI agents full DevTools access for automated debugging and performance profiling.

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

Summary

Google's Chrome DevTools team released an official MCP server that lets AI coding agents (Antigravity, Claude, Cursor, Copilot) control and inspect a live Chrome browser via the Model Context Protocol. It exposes DevTools capabilities like performance tracing, network analysis, and Puppeteer-based automation with source-mapped stack traces, and includes a CLI for non-MCP use. The tool collects usage statistics by default and sends trace URLs to the CrUX API for field data, both opt-out via flags or environment variables.

Author

ChromeDevTools