Chrome DevTools MCP Server
The Chrome DevTools MCP Server hands the browser's developer tools to your AI. When you're debugging a frontend issue, you no longer paste console errors and network-panel screenshots by hand — the AI opens a Chrome and reads the page's real DOM, network requests and console output itself.
For web developers this removes the reproduce-screenshot-describe loop. The AI sees what actually happened in the browser, so it has fuller context for finding the problem.
Install / Connect
claude mcp add chrome-devtools-mcp -- npx -y chrome-devtools-mcpFollow the official README; env and args vary per server.
Works with these clients
- Claude Desktopnpx
- Claude Codenpx
- Cursornpx
- VS Codenpx
- Windsurfnpx
Derived from the registry manifest (package type and transport) — we have not installed it ourselves. Check the official README before relying on it.
Why use it
Good for: developers who want the AI to help debug frontend issues, analyze page performance, or reproduce browser-only bugs that only appear in a real environment.
Before connecting: it launches a real browser process, so it is heavier than a pure API server. The maintenance signals, TrustScore and derived client compatibility are all below.
Similar / alternative servers
io.github.achiya-automation/safari-mcp
Native Safari browser automation for AI agents — 97 tools, zero Chrome overhead.
playwriter
Chrome extension & CLI to let agents control your browser. Runs Playwright snipp
ai.foura/mcp
Reliable web access for AI agents: smart HTTP, rotating proxies, and full-browse
io.github.ShaftHQ/shaft-mcp
shaft-mcp
Frequently Asked Questions
Does it need Chrome installed locally?
It needs a Chrome/Chromium it can drive. Check the official README for exact version requirements.
Which AI clients are supported?
It's a local stdio server, so Claude Desktop, Claude Code, Cursor and VS Code all work. See the compatibility section below.