[GitHub Trending] ChromeDevTools/chrome-devtools-mcp
Scored daily by a customisable AI persona to surface the most relevant engineering leadership news.
Chrome DevTools MCP for coding agents, perfect match for reader
Google's official chrome-devtools-mcp exposes Chrome DevTools capabilities as an MCP server, enabling AI coding agents (Gemini, Claude, Cursor, Copilot) to automate, debug, and analyze performance in live browsers via Puppeteer and the CrUX API. The tool supports headless/slim modes, opt-out flags for usage statistics and CrUX data sharing, and requires Node.js LTS. Its architecture raises a security concern: browser content is accessible to MCP clients, so sensitive data should be avoided.
Integrate chrome-devtools-mcp into your AI coding toolchain to get real-time performance traces and debugging from within agent loops.
For a platform engineer building AI-assisted development workflows, this gives agents direct DevTools-level observability into browser interactions, enabling automated debugging and performance analysis within agent loops.
Chrome DevTools for agents Chrome DevTools for agents ( chrome-devtools-mcp ) lets your coding agent (such as Gemini, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis. A CLI is also provided for use without MCP. Tool reference | Changelog | Contributing | Troubleshooting | Design Principles Key features