Breakpoints set via MCP API don't pause execution (using custom stdio proxy)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- node.js, typescript, vscode
Research direction
Start with the custom stdio-to-HTTP+SSE proxy's handling of add_breakpoint and start_debugging, and reproduce the numbered call sequence against http://localhost:3001/mcp. Trace whether the session and breakpoint state survive both requests; done when MCP-registered breakpoints pause execution and the paused-state tools expose a stack frame.
Written by the indexing model from the issue text.
Description
Breakpoints registered via add_breakpoint are accepted but execution never pauses when code runs through them. Debug sessions run to completion without stopping.
Important: We wrote a custom stdio-to-HTTP+SSE proxy because DebugMCP's HTTP transport is incompatible with Claude Code's stdio-only MCP client. This proxy may be causing the issue.
Environment
- DebugMCP: 2.3.0
- VS Code: 1.132.0
- Node.js: v24.16.0
- OS: Windows 11 Enterprise
- Runtime: TypeScript via tsx v4.22.4 + vitest 4.1.9
- Project: SAP CAP with @sap/cds 10.0.3
- Custom proxy: stdio → HTTP+SSE bridge
Reproduction
- Start DebugMCP (http://localhost:3001/mcp)
- Start custom proxy bridging stdio → HTTP+SSE
- Call add_breakpoin + line number →returns success ✅
- Call start_debugging with launch config → launches successfully ✅
- Code runs through breakpoint without stopping ❌
- Session completes "ran to completion without stopping"
What Works
- Proxy forwards all 15 MCP tools successfully
- Debug sessions launch
- Manual breakpoints in VS Code UI work fine
What Doesn't Work
- Execution never pauses at MCP-registered breakpoints
- No stack frame for variable inspection
- Tools timeout waiting for paused state
What We Tried
- TypeScript source p
- Multiple launch configurations
- Simple test scripts
- Logpoints (also didn't trigger)
- Setting breakpoints
All fail identically.
Hypothesis
Proxy may not be maintaining breakpoint state correctly between add_breakpoint and start_debugging calls. Our proxy parses SSE responses line-by-line and tracks session IDs, but breakpoint registration state might need to persist within a single HTTP session.
Simplified proxy logic:
// Parse SSE from DebugMCP, forward JSON-RPC to Claude Code
const response = await fetch('http://localhost:3001/mcp', {
method: 'POST',
headers: { 'Accept': 'text/event-stream' },
body: JSON.stringify(request)
});
// Parse SSE events, extract session IDs, forward responses
- Dominant language
- TypeScript
- Stars
- 511
- Forks
- 60
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 18
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/DebugMCP
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in microsoft/DebugMCP
Similar issues
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Crush Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ElementsProject/cln-application#167 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Quantco/pnpm-licenses#17 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100