Software & DevOpsDone with custom-built or unnamed agent Sep 23, 2026
Debug Windows crash dumps with an AI agent via MCP
ForensicDbg is a post-mortem debugger for native Windows x64/x86 crashes with an MCP server so AI agents can debug from interpreted, interlinked crash data.
- What They Did
- ForensicDbg is a post-mortem debugger for x86 and x64 Windows crash dumps. Its MCP server runs over stdio and works with AI tools that support that. It gives the agent output that is already interpreted and labeled, such as the faulting thread, frame and instruction, validated callstacks, and deduced types. The agent works from that instead of raw dump data.
- How It Went
- The page shows one example: the agent traced a crash to a missing null check in a text window's selection code and proposed a guard. It gives no benchmarks or token figures.
- Worth Knowing
- The tool is in a private beta, so you need to request an invite, and the page says little about setup; there is a separate MCP setup guide.
Try it yourself with custom-built or unnamed agent
I have a Windows crash dump at [path to .dmp file]. Use the debugging tools or MCP server available to analyze it and tell me the likely root cause, the faulting call stack, and the exact function and line if symbols exist. Finish with a short report listing evidence for your conclusion and suggested fixes, and don't change any code until I approve.