Google's Chrome DevTools MCP Just Cracked Open Third-Party Tools
Google's official Chrome DevTools team shipped chrome-devtools-mcp v0.25.0 on May 6, then v0.24.0 a few days before. 39K stars on GitHub, +107 today. The repo lets coding agents drive a real Chrome browser — record traces, inspect networks, automate clicks, snapshot memory, the whole DevTools surface.
v0.25.0 is the structural one. It exposes what Google calls third-party developer tools — DevTools panels and extensions injected by the page itself or by other tools. Behind a `--category-experimental-third-party` flag for now. What this actually means: any DevTools extension your team has built — React DevTools, Redux DevTools, Vue DevTools, your custom internal observability panel — is now reachable by Claude Code, Codex, Cursor, Cline, JetBrains AI, and the 15+ other clients chrome-devtools-mcp supports.
v0.24.0 quietly added agentic browsing capabilities inside Lighthouse. That is the Google performance audit tool now running with an agent driver instead of a deterministic script. Plus MCP roots feature support — clients can scope which directories the server is allowed to touch. Together with conditional tools support in CLI it is a real harness-engineering pass.
Why this matters more than another MCP server release: Chrome DevTools is one of the most successful debugging UIs in software history. Google making it agent-driven, with extension support, is an explicit bet that the browser-as-debugger surface will become the default for agentic web work — beating dedicated tools like Playwright MCP or Browserbase on installed-base alone.
github.com/ChromeDevTools/chrome-devtools-mcp. Two structural releases in one week, in a repo trending daily on GitHub. The Chrome team is moving fast on this for a reason.
← Back to all articles
v0.25.0 is the structural one. It exposes what Google calls third-party developer tools — DevTools panels and extensions injected by the page itself or by other tools. Behind a `--category-experimental-third-party` flag for now. What this actually means: any DevTools extension your team has built — React DevTools, Redux DevTools, Vue DevTools, your custom internal observability panel — is now reachable by Claude Code, Codex, Cursor, Cline, JetBrains AI, and the 15+ other clients chrome-devtools-mcp supports.
v0.24.0 quietly added agentic browsing capabilities inside Lighthouse. That is the Google performance audit tool now running with an agent driver instead of a deterministic script. Plus MCP roots feature support — clients can scope which directories the server is allowed to touch. Together with conditional tools support in CLI it is a real harness-engineering pass.
Why this matters more than another MCP server release: Chrome DevTools is one of the most successful debugging UIs in software history. Google making it agent-driven, with extension support, is an explicit bet that the browser-as-debugger surface will become the default for agentic web work — beating dedicated tools like Playwright MCP or Browserbase on installed-base alone.
github.com/ChromeDevTools/chrome-devtools-mcp. Two structural releases in one week, in a repo trending daily on GitHub. The Chrome team is moving fast on this for a reason.
Comments