Chrome breakpoint debugging MCP server for inspecting runtime values and stepping through code
{
"mcpServers": {
"chrome-debugger": {
"args": [
"-y",
"chrome-debugger-mcp"
],
"command": "npx"
}
}
}Chrome breakpoint debugging MCP server for inspecting runtime values and stepping through code
Is it safe?
No known CVEs for chrome-debugger-mcp.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 22 days ago. 17 weekly downloads.
Will it work with my client?
Transport: stdio, sse. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Context cost
17 tools. ~1,000 tokens (0.5% of 200K).
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'chrome-debugger-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
startDebuggingSessionReturns the recommended debugging workflow and critical rules for agent behavior
launchChromeLaunches a dedicated Chrome instance with remote debugging enabled
listTargetsLists available Chrome tabs and requires the user to pick one
connectAttaches to the confirmed tab
setBreakpointCreates a CDP breakpoint without modifying source files
removeBreakpointRemoves a breakpoint created by setBreakpoint
reloadPageReloads the current page through CDP
waitForSpecificPauseWaits for the next pause and checks whether it matches a target file and line
waitForPauseWaits for any pause without location matching
getScopeVariablesReads local, closure, and module scope values from the paused frame
This server is missing a description.If you've used it, help the community.
Add informationNo known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.