Radar
← All projectsFriday, July 31, 2026
Chrome DevTools MCP
Official Chrome DevTools as an MCP server — let coding agents drive a live browser, debug it, and pull real performance traces.
Why it matters
chrome-devtools-mcp is an open-source Model Context Protocol server from the Chrome DevTools team. It connects coding agents such as Claude, Cursor, Copilot, and Antigravity to a live Chrome instance so the agent can navigate, click, type, inspect the DOM, read the console, capture screenshots, list network requests, run performance traces, and audit with Lighthouse. A CLI is included for the same capabilities without MCP.
Most agent browser tools stop at screenshots and brittle click scripts. This is the Chrome team’s own DevTools surface for agents: network, console with source maps, Lighthouse, heap snapshots, and Puppeteer-backed automation that waits for real results. If your product or agent ships web UI, this is the debugging layer worth wiring once.
How it works
Install the npm package, point your agent’s MCP config at chrome-devtools-mcp, and start a supported Chrome or Chrome for Testing build. The agent gets tools for input and navigation automation, network and console inspection, performance start/stop/analyze, screenshots and accessibility snapshots, plus deeper memory tooling like heap snapshots. You can also run the CLI when you want the same control outside an MCP host.
Not a generic headless wrapper and not an in-page script injected into your app. It is official Chrome DevTools power exposed to agents through MCP — the same debugging and performance stack humans use, including traces and source-mapped console output.
Capabilities
- Public demo available
- MCP server / client support
Similar tools