Google Ships Official Chrome DevTools MCP Server. 38,582 Stars in Days.

chrome-devtools-mcp isn't another community MCP server with 200 stars and a README that doesn't match the code. It's Google's Chrome DevTools team shipping an official MCP server that gives any coding agent (Claude Code, Gemini CLI, Codex, Cursor) full access to Chrome DevTools for debugging, performance analysis, and browser automation via Puppeteer.

38,582 stars. Highest-traction MCP server on GitHub by a wide margin.

The feature that caught my attention: agents can connect to active browser sessions behind logins without requiring additional sign-in. If you've tried to build agent-driven browser testing workflows, you know the auth problem. Your agent can't test the dashboard because it can't log in. Or it can log in but the session expires mid-test. Chrome DevTools MCP solves this by connecting to your existing authenticated session.

This fills a real gap in the agent toolchain. Coding agents are great at writing code, running tests, and modifying files. They're terrible at verifying that the thing they built actually works in a browser. I can tell my agent to build a React component, write tests for it, and it'll do a decent job. But asking it to verify the component renders correctly, handles edge cases in the UI, and doesn't break existing pages? That required me to open the browser and check manually.

With DevTools MCP, the agent can inspect the DOM, check performance traces, and verify rendering without leaving the coding environment. It's not perfect. The agent still doesn't have great visual judgment about whether something looks right. But it can catch broken layouts, missing elements, and JavaScript errors that would otherwise require human inspection.

Connect your coding agent to Chrome DevTools this week. The setup is minimal and the debugging capabilities are immediately useful. Start with having the agent check its own output in the browser after generating frontend code.