chrome-devtools-mcp is the official Model Context Protocol server from the Chrome DevTools team that lets coding agents drive and inspect a live Chrome browser. Rather than relying on brittle DOM scraping or screenshot vision, the server exposes the same capabilities a human engineer uses in DevTools — network inspection, performance traces, Lighthouse audits, console access, emulation, and structured snapshots of the page — as typed MCP tools that any MCP-capable agent can call.
Under the hood the server reuses Chrome's CDP (Chrome DevTools Protocol) surface, so agents get first-party fidelity on the data that actually drives the browser. That makes it a strong fit for agentic debugging workflows: an agent can open a page, capture a performance trace, grab failing requests from the Network panel, run a Lighthouse audit, and explain the regression in a single loop. It slots into Claude Code, Cursor, Windsurf, Copilot and other MCP-capable clients through MCP configuration rather than application-code changes.
The project is Apache-2.0 licensed and maintained inside the ChromeDevTools org, which raises the floor on stability and API coverage compared to community-built browser MCPs. It is particularly useful for web performance work, E2E debugging, and any workflow where the agent needs structured browser telemetry rather than raw pixels or fragile selectors.
