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. That is what the chrome debugger mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
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.
Installation goes through your MCP client rather than a global install: point it at chrome-debugger-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
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; statementsPlenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Chrome Debugger MCP's toolset — startDebuggingSession, launchChrome, listTargets and 11 more — is a fair guide to whether it matches your workflow. It is maintained by BitePro; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| 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; statementsKill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.