Chrome DevTools opens to AI agents: chrome-devtools-mcp lets coding assistants drive and inspect a live browser
Synopsis
Google released chrome-devtools-mcp, which lets coding agents such as Antigravity, Claude, Cursor and Copilot control and inspect a running Chrome browser through a Model-Context-Protocol server or a command-line interface. It hands agents DevTools performance tracing, network request analysis, screenshots and console messages, and uses puppeteer to perform actions and automatically wait for their results. The tool officially supports only Google Chrome and Chrome for Testing; other Chromium-based browsers may work but are not guaranteed.
Interpretation
Coding agents can now control and inspect a live Chrome browser rather than only generating code inside an editor. chrome-devtools-mcp supplies this in two forms, a Model-Context-Protocol server and a command-line tool, both giving an AI coding assistant Chrome DevTools automation, debugging and performance analysis. The official description lists three uses: recording traces and extracting performance insights with DevTools, analyzing network requests and taking screenshots while reading console messages with source-mapped stack traces, and reliable automation built on puppeteer.
Once connected through an MCP client, an agent can inspect, debug and modify data in the browser or DevTools. The connection is a Model-Context-Protocol server, started in the client configuration with npx and chrome-devtools-mcp@latest. The server starts the browser automatically only when the client uses a tool that requires a running browser, and connecting to the server alone does not start it; the official check is to record a performance trace on a given page.
Performance analysis can present field data alongside lab data. Performance tools may send trace URLs to the Google CrUX API to fetch real-user experience data. That data is collected by the Chrome User Experience Report and can be disabled with --no-performance-crux.
Perspective
Official support covers Google Chrome and Chrome for Testing; other Chromium-based browsers may work but are not guaranteed and may show unexpected behavior. The tool targets developers driving a browser through an MCP client or a terminal CLI, and the server starts the browser only when the client uses a tool that requires one.
The official statement commits fixes and support only for the latest version of Extended Stable Chrome. Performance tools may send trace URLs to the Google CrUX API, and usage statistics are collected by default; they are disabled separately with --no-performance-crux and --no-usage-statistics, and the official description states that opting out of this tool's usage statistics and opting out of Chrome browser metrics do not affect each other.