Chrome breakpoint debugging MCP server for inspecting runtime values and stepping through code
Chrome breakpoint debugging MCP server for inspecting runtime values and stepping through code
chrome-debugger-mcp exposes Chrome DevTools Protocol primitives as MCP tools so an AI agent can attach to a real Chrome tab, pause execution, inspect scope values, evaluate expressions inside the current call frame, and step through code with runtime facts instead of guessing from static source.
The server publishes 14 tools. What each one is for:
startDebuggingSession — returns the recommended debugging workflow and critical rules for agent behaviorlaunchChrome — launches a dedicated Chrome instance with remote debugging enabledlistTargets — lists available Chrome tabs and requires the user to pick oneconnect — attaches to the confirmed tabsetBreakpoint — creates a CDP breakpoint without modifying source filesremoveBreakpoint — removes a breakpoint created by setBreakpointreloadPage — reloads the current page through CDPwaitForSpecificPause — waits for the next pause and checks whether it matches a target file and linewaitForPause — waits for any pause without location matchinggetScopeVariables — reads local, closure, and module scope values from the paused frameevaluate — executes JavaScript in the paused call frameresume — resumes execution after inspectiondebugger; statementsstartDebuggingSession — returns the recommended debugging workflow and critical rules for agent behaviorlaunchChrome — launches a dedicated Chrome instance with remote debugging enabledlistTargets — lists available Chrome tabs and requires the user to pick oneconnect — attaches to the confirmed tabsetBreakpoint — creates a CDP breakpoint without modifying source filesremoveBreakpoint — removes a breakpoint created by setBreakpointreloadPage — reloads the current page through CDPwaitForSpecificPause — waits for the next pause and checks whether it matches a target file and linewaitForPause — waits for any pause without location matchinggetScopeVariables — reads local, closure, and module scope values from the paused frameevaluate — executes JavaScript in the paused call frameresume — resumes execution after inspectiongetStatus — non-blocking polling for connected or paused stateforcePause — requests a pause at the next JavaScript statementCompare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| startDebuggingSession | returns the recommended debugging workflow and critical rules for agent behavior |
| launchChrome | launches a dedicated Chrome instance with remote debugging enabled |
| listTargets | lists available Chrome tabs and requires the user to pick one |
| connect | attaches to the confirmed tab |
| setBreakpoint | creates a CDP breakpoint without modifying source files |
| removeBreakpoint | removes a breakpoint created by setBreakpoint |
| reloadPage | reloads the current page through CDP |
| waitForSpecificPause | waits for the next pause and checks whether it matches a target file and line |
| waitForPause | waits for any pause without location matching |
| getScopeVariables | reads local, closure, and module scope values from the paused frame |
| evaluate | executes JavaScript in the paused call frame |
| resume | resumes execution after inspection |
| getStatus | non-blocking polling for connected or paused state |
| forcePause | requests a pause at the next JavaScript statement |
{
"mcpServers": {
"chrome-debugger": {
"command": "npx",
"args": ["-y", "chrome-debugger-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
debugger; statementsRead, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.