get-debug-sessionLABSCO SUMMARY
Logpoints and conditional breakpoints, set from the same place you are asking about the bug.
The useful move here is the logpoint: set a breakpoint that prints an interpolated message instead of halting, so you get the value of a variable at a line without stopping the app or editing the file. Errors and violations also stream, so a long session does not need polling.
What it is
A development companion for React and Next.js work. It drives Chrome through Puppeteer to capture errors and network activity, watches files for complexity and rule violations, and manages breakpoints — all reachable as tool calls.
What you get
- get-errors — caught and uncaught errors, console errors and promise rejections, filtered by severity or timeframe
- get-violations — code-quality rule violations, by severity or by file
- analyze-complexity — cyclomatic complexity, function metrics and nesting depth for one file
- get-performance — render times and performance metrics over a timeframe
- manage-breakpoints — set, remove and list breakpoints, including conditional ones and logpoints that log instead of stopping
- get-debug-session and update-config — the current session, and changing the debugger's settings mid-flight
- Three live resources: stream://errors, stream://violations and stream://performance
Requirements
Node — clone, npm install, npm run build, then point the client at the built dist/index.js. No credentials.
Setup effort
Build from source — git clone https://github.com/Phoenixrr2113/debugger-mcp.git
USE CASES
01
Finding out what actually blew up
Pull the errors for the last few minutes, filtered by severity, instead of scrolling a console.
02
Watching a value at a line without editing code
Set a logpoint with an interpolated message at that line; the app keeps running and the message shows up.
03
Stopping only when the request is failing
Set a conditional breakpoint on the API call so it fires on error responses rather than every call.
04
Deciding which file to refactor first
Get complexity, function metrics and nesting depth for a component, and check what rules it is breaking.
7 tools
Listed in project docs. Your client may show a different list.
get-errorsget-violationsanalyze-complexityget-performancemanage-breakpointsupdate-configBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
# Clone the repository
git clone https://github.com/Phoenixrr2113/debugger-mcp.git
cd debugger-mcp
# Install dependencies
npm install
# Build the project
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"debugger": {
"command": "node",
"args": [
"<YOUR_PATH_TO_DEBUGGER_MCP>/dist/index.js"
],
"env": {}
}
}
}
