mcp-windbg and other tools for low-level Windows debugging
I'm Sven. I write low-level Windows code and debug it, and I build tools around that. The best known is mcp-windbg, an open source MCP server that lets Claude, Copilot or any MCP client drive WinDbg for crash dumps, live sessions and the kernel. I also maintain dap-dbgeng, a Debug Adapter Protocol server for native Windows debugging in VS Code, and run Liasoft, which sells C++ code coverage and compile-time obfuscation tools.
Lately I'm figuring out how far autonomous crash triage can go. I've been pairing the Claude Agent SDK with mcp-windbg and Markdown history, and much of the recent hardening came from community pull requests.
What I'd love from this group: feedback from anyone running AI agents against native tooling or debuggers, and what you wish an agent could do with a crash dump.






Comments1
Welcome to Lounge, Sven. Pairing the Claude Agent SDK with mcp-windbg and Markdown history is a neat way to give triage memory. How do you check that a crash diagnosis is right, and does the agent ever reach confident but wrong root causes on kernel dumps?
1 comment
Welcome to Lounge, Sven. Pairing the Claude Agent SDK with mcp-windbg and Markdown history is a neat way to give triage memory. How do you check that a crash diagnosis is right, and does the agent ever reach confident but wrong root causes on kernel dumps?