Chrome Debugger MCP
Let your agent drive real Chrome breakpoint debugging—inspect variables and step code—while you fix frontend issues.
Overview
Chrome Debugger MCP is a MCP server for the Ship phase that connects your AI client to Chrome breakpoint debugging for stepping code and reading runtime values.
What is this MCP server?
- MCP server wired to Chrome DevTools-style breakpoint debugging
- Inspect runtime values and step through JavaScript in a live browser session
- npm package chrome-debugger-mcp with stdio transport (v1.0.4)
- Complements headless automation by exposing true debugger controls
- Open-source GitHub repo for local install and MCP config
- npm identifier chrome-debugger-mcp version 1.0.4
- stdio transport from official MCP registry metadata
- GitHub source repository listed in server.json
Community signal: 1 GitHub stars.
What problem does it solve?
Frontend bugs hide in live browser state that agents cannot see when they only read source files and console snippets.
Who is it for?
Indie devs debugging React, vanilla JS, or extension frontends locally who want agent-assisted stepping without abandoning Chrome DevTools.
Skip if: Backend-only API work, teams forbidden from debugger attachment, or workflows that only need headless screenshot automation.
What do I get? / Deliverables
After install, your agent can interact with real breakpoints and stack frames so you fix UI logic with verified runtime context.
- Agent-accessible breakpoint set, step, and inspect operations in Chrome
- Faster reproduction notes tied to actual stack and scope values
- Verified frontend fixes before ship
Recommended MCP Servers
Journey fit
How it compares
Live Chrome debugger MCP, not a passive DOM scraper or unit-test runner skill.
Common Questions / FAQ
Who is chrome debugger mcp for?
Solo builders and frontend-focused indies using MCP agents who need breakpoint-level visibility in Chrome while iterating on web apps.
When should I use chrome debugger mcp?
Use it when reproducing a client-side bug requires inspecting variables at specific lines, stepping async code, or validating fixes under real browser execution.
How do I add chrome debugger mcp to my agent?
Install the npm package chrome-debugger-mcp, add an stdio MCP server entry in Claude Code or Cursor, launch Chrome with remote debugging as required by the repo docs, then reconnect tools.