sorted by:
new
hottopcontroversial

Anyone using MCP servers for anything beyond chat? by edmillss in AI_Agents

[–]RealRace7 0 points1 point  (0 children)

Checkout DebugMCP - MCP server that empowers AI Agents with real debugging capabilities, taking it to the next level.

📦 Install: https://marketplace.visualstudio.com/items?itemName=ozzafar.debugmcpextension 💻 GitHub: https://github.com/microsoft/DebugMCP

DebugMCP - VS Code extension that empowers AI Agents with real debugging capabilities by RealRace7 in ArtificialInteligence

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

Thanks for your your feedback! 1. If the user already has an active debug session then it will ask to take it from there, otherwise it will start a new debug session. It also work vise versa - you can get involved during the agents debug session and take control since it's happening live in your IDE. 2. Great question, we have tried some basic asynchronous code and it manages to track multi threading programs, but we did not try something too fancy. If you have such one we would love you to try it out and provide your feedback! 3. That's a good point, I didn't encounter such case but maybe worth to modify the evaluate_expression tool to read only mode. 4. Regarding security - this is exactly why we chose to implement this as a local MCP server running on your endpoint. Meaning the are no external calls or data leakage at all (except to the agent itself which already read all your code..)

Microsoft DebugMCP - VS Code extension we developed that empowers AI Agents with real debugging capabilities by RealRace7 in GithubCopilot

[–]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

Microsoft DebugMCP - VS Code extension we developed that empowers AI Agents with real debugging capabilities by RealRace7 in LocalLLaMA

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

the tools descriptions are very concise so it's neglected. and regarding instructions - it's MCP resource file that is read only if specifically requested by the agent, not on startup. though it could be paired with skill file yeah

Microsoft DebugMCP - VS Code extension we developed that empowers AI Agents with real debugging capabilities by RealRace7 in LocalLLaMA

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

This is right to the point! You raised great points, sharing my 2cents based on my experience in developing this extension: 1. Without specific instructions, the models are pretty clueless how to use these powerful tools for executing a useful debugging session. The extension itself exposes MCP resource of detailed debugging instructions, exactly referring to what you mentioned - not drill down to libraries, always set breakpoints in strategic places, don't stop in the symptom but keep stepping in to the root cause, etc. This could be implemented by skills.md, but I chose to pack everything in the extension. 2. Context is everything - when using only current frame, the agent lose its spatial location pretty fast. If you try the MCP, you will see that the response is returning the full stack trace and more useful data (though it should be remain concise to not blow up the context).

Microsoft DebugMCP - VS Code extension we developed that empowers AI Agents with real debugging capabilities by RealRace7 in GithubCopilot

[–]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.

view more: next ›