mcp-windbg

Why we included this project

Reading a Windows crash dump by hand means memorizing WinDbg command syntax and manually stitching the call stack and module data together. This project is an MCP server that drives the real cdb.exe and kd.exe debuggers, so an LLM can open a .dmp, run automated triage, and answer plain-language follow-ups like 'what caused this access violation?' That helps anyone holding dumps from Windows apps, services, or kernel targets who wants faster root-cause analysis without learning debugger internals. It also attaches to live remote sessions over TCP, named pipes, or KDNET, scans a whole folder of dumps for a common signature, and can strip secrets from tool output before it reaches a cloud model. Treat it as a practical wrapper: you still need symbols and a Windows host with the Debugging Tools installed.