What it does
The server exposes Chrome DevTools Protocol operations as MCP tools. After the user confirms a tab, an agent can pause execution at breakpoints or debugger statements, read local, closure and module scope values, evaluate JavaScript in the current call frame, and step or resume. It is not a general browser automation tool; its focus is runtime debugging.
It suits cases where an agent should reason from actual runtime state rather than static source, such as checking what a variable holds when a button click runs. The workflow covers launching a dedicated Chrome instance with remote debugging, setting breakpoints without editing source files, reloading the page so breakpoints bind, and waiting for a specific pause by file and line. That wait matches either a URL fragment with line tolerance, or the debugger-statement pause reason, which helps when source maps or bundling shift line numbers.
Running it means starting the server over stdio from an MCP client and following the documented sequence: list the open tabs, have the user confirm the exact URL, connect, set a breakpoint or temporary debugger statement, reload, wait for the pause in the same turn, inspect, and resume. Temporary debugger statements should be removed before the agent finishes. Launching Chrome uses a dedicated profile, separate from the user's normal browser session.
Limitations and requirements
Requires Google Chrome installed locally, an MCP client that supports stdio servers and tool calling, access to the application being debugged, and local source access if temporary debugger statements are inserted. The agent must wait for explicit user confirmation before connecting to a tab.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Chrome Debugger MCP
Chrome breakpoint debugging MCP server for inspecting runtime values and stepping through code
v1.0.4As shown on registry.modelcontextprotocol.io when we last read it