Chrome DevTools MCP

Chrome DevTools MCP gives a coding agent control of a live Chrome browser with the Chrome DevTools feature set: performance trace recording and insights, network and console inspection, screenshots, and Puppeteer-based input automation. The README scopes support precisely: the server "officially supports Google Chrome and Chrome for Testing only."

It runs locally over stdio via npx -y chrome-devtools-mcp@latest, spawning or attaching to a local Chrome instance; flags exist for attaching to an already-running browser over its remote-debugging endpoint. No hosted remote endpoint exists and the MCP transport itself carries no authentication. The README warns that the server "exposes content of the browser instance to the MCP clients," including any data visible in the browser.

The Google relationship is verifiable on two surfaces: the package.json author field reads "Google LLC", and developer.chrome.com published the launch post announcing "a public preview for the new Chrome DevTools Model Context Protocol (MCP) server", linking this repository. One operational fact worth knowing: Google collects usage statistics from the tool, enabled by default, with an opt-out via the --no-usage-statistics flag; the README states this collection is independent from Chrome browser metrics.

No surface names a supported MCP specification revision. The changelog and release notes through v1.6.0 (2026-07-14) contain no revision statement; SECURITY.md cites the MCP roots capability by linking the 2025-06-18 spec section, which documents a feature reference rather than a revision claim; and the declared @modelcontextprotocol/sdk 1.30.0 devDependency is not evidence of revision support. spec_status is therefore unknown.