Chrome DevTools is now an MCP server for your agent

An agent asked to fix a slow page has historically had to work from your description of the problem. chrome-devtools-mcp closes that loop: it is an Apache-2.0 MCP server, from the Chrome DevTools team itself, that gives a coding agent a live browser to inspect.

What it is

An MCP server exposing the DevTools surface to Antigravity, Claude, Cursor, Copilot or anything else that speaks the protocol. Three capability groups: performance traces with extracted insights, browser debugging (network requests, screenshots, console messages carrying source-mapped stack traces), and Puppeteer-driven automation that waits for actions to actually complete. A CLI is included for use without MCP at all.

Why it showed up now

v1.7.0 on August 10 and pushed the day of this snapshot. It has been around since September 2025, which makes it old for this ecosystem, and it is still maintained.

How it actually works

Performance work runs through the real DevTools trace pipeline and returns insights rather than raw traces: the difference between handing a model a 40 MB JSON blob and handing it "layout shift caused by this image without dimensions".

Source-mapped stack traces let the agent read your source instead of guessing from a minified console error. Puppeteer underneath means action results are awaited rather than slept on, which is where most homegrown browser automation becomes flaky.

Official support covers Google Chrome and Chrome for Testing. Other Chromium browsers may work, with committed support for the latest Extended Stable Chrome.

Try it

Add it to your agent's MCP configuration as the npm package chrome-devtools-mcp, or use the bundled CLI directly. Point it at a page you already know is slow and compare the insight list against your own read of the trace.

Where it is weak

Read the disclaimers, because they are unusually direct. The server exposes the content of the browser instance to MCP clients, allowing them to inspect, debug and modify any data in the browser or DevTools. If that Chrome profile is logged into anything, the agent, and whatever it just read on a hostile page, is inside your session. The README's advice is to avoid sharing sensitive information with MCP clients, which in practice means running it against a clean profile.

Performance tooling may send trace URLs to Google's CrUX API to fetch real-user data alongside your lab measurements. A flag disables it, and it is on by default.

114 open issues, and it covers Chrome only: bugs specific to other browser engines stay out of reach.