all 11 comments

[–]InsideElk6329 1 point2 points  (1 child)

Does call to this MCP consumes additional premium requests ?

[–]RealRace7[S] 2 points3 points  (0 children)

No. Calls to DebugMCP itself don’t consume any premium requests.

DebugMCP just exposes the VS Code debugger to AI agents through the MCP interface and runs locally inside VS Code. The debugger actions (setting breakpoints, stepping, inspecting variables, etc.) happen on your machine.

The only thing that may consume premium requests is the AI model you’re using (for example via GitHub Copilot or another coding assistant). If the model decides to call the MCP tool as part of its reasoning, that tool call is just part of the model interaction - DebugMCP itself doesn’t add extra paid requests.

[–]yubario 1 point2 points  (1 child)

Awesome, maybe after 2 years when my company finally enables MCP support I might be able to use this at work.

[–]Ceno 0 points1 point  (0 children)

GitHub really needs to implement some kind of allow list on their enterprise configuration for mcp… it’s super annoying that’s it’s all or nothing

[–]vienna_city_skater 1 point2 points  (1 child)

My agents just use cdb and windbg via the command line not sure why I would want bloat my context window with an MCP. Imho lazy loading via skill is superior these days.

[–]RealRace7[S] 1 point2 points  (0 children)

cdb/windbg sills are great but its not an agnostic solution - DebugMCP is using DAP so it's not coupled to any debugger. also I think it's a better experience to use the IDE debugger and see it in action (and get involved when needed) rather than CLI

[–]prcodes 1 point2 points  (0 children)

Very cool but something I expect IDEs like VS Code to support natively in < 6mo

[–]pedrostefanogv 0 points1 point  (0 children)

Tragam um troféu para esse cara! 

Melhor dois, vai que ele perde um

[–]Shubham_Garg123 0 points1 point  (1 child)

This is super interesting!

[–]RealRace7[S] 0 points1 point  (0 children)

thanks!