
Chrome DevTools MCP
Chrome DevTools MCP is a MCP server that lets agents control Chrome DevTools for debugging and browser testing.
claude mcp add chrome-devtools-mcp -- npx -y chrome-devtools-mcp| GitHub stars | ★ 43.2k |
|---|---|
| Package | chrome-devtools-mcp |
| Repository | ChromeDevTools/chrome-devtools-mcp ↗ |
What it does
Solo builders waste cycles manually reproducing UI bugs and perf issues that an agent could inspect if DevTools were on the MCP bus.
Who is it for?
Indie web and extension builders who want MCP-native browser debugging during test-and-fix loops.
Skip if: Pure backend or CLI projects with no Chrome surface, or teams forbidding local browser control from agents.
What you get
Your agent can run DevTools-backed checks and debugging steps from the same chat where it edits frontend code.
- Registered DevTools MCP server in your agent
- Agent-callable browser inspection and debugging tool surface
Recommended MCP Servers
How it compares
First-party DevTools MCP bridge, not a generic Playwright skill file.
FAQ
Who is Chrome DevTools MCP for?
Solo builders and frontend-heavy teams who want Claude Code or Cursor to drive Chrome DevTools through MCP for debugging and verification.
When should I use Chrome DevTools MCP?
Use it in Ship during testing when you need automated or agent-guided inspection of network, console, and performance in a real browser.
How do I add Chrome DevTools MCP to my agent?
Add the chrome-devtools-mcp npm MCP server (stdio) to your agent config, install v1.2.0 from the npm registry, and ensure Chrome is available for DevTools sessions.