MCP Server for WinDbg Crash Analysis — Claude Code MCP server
Bridges Claude Code with CDB and KD debuggers for crash dump triage, kernel inspection, and remote debugging without opening the WinDbg UI.
claude mcp add --env CDB_PATH=<CDB_PATH> --env _NT_SYMBOL_PATH=<_NT_SYMBOL_PATH> --transport stdio mcp-server-for-windbg-crash-analysis -- uvx mcp-windbgWhat MCP Server for WinDbg Crash Analysis does
The server functions as a Python wrapper around console utilities cdb.exe and kd.exe. It supplies MCP tools to inspect user-mode dumps (.dmp, .mdmp), kernel dumps (MEMORY.DMP), or live targets. An assistant can inspect stack frames, list loaded modules, and run debugger diagnostics through commands like !analyze -v.
Every target receives an isolated session identifier. This architecture permits side-by-side triage across multiple dump files. To prevent hanging live sessions, per-call timeouts trigger a CTRL+BREAK interruption to resynchronize the connection, and an optional filter script strips sensitive data before output leaves the host.
Without Debugging Tools for Windows or WinDbg installed to provide cdb.exe and kd.exe, the server cannot execute. Unlike Microsoft's official GUI-integrated WinDbg MCP, this project operates completely headless over stdio or HTTP.
What it helps with
- Triage crash dump files after application crashes or kernel bugchecks.
- Execute arbitrary WinDbg and KD commands from natural language requests.
- Inspect multiple crash dumps across a directory to compare failures.
- Attach to remote user-mode debug servers or live Windows kernel sessions.
Example prompts for the agent
- Open crash.dmp in the current folder and explain the failure using !analyze -v
- Run kb on the open cdb session and inspect the faulting call stack
- Scan C:\Dumps for crash files and summarize the common fault signatures
How to install MCP Server for WinDbg Crash Analysis
Platform CLI
claude mcp add --env CDB_PATH=<CDB_PATH> --env _NT_SYMBOL_PATH=<_NT_SYMBOL_PATH> --transport stdio mcp-server-for-windbg-crash-analysis -- uvx mcp-windbgReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from mcp-windbg <command>
Platform CLI
codex mcp add mcp-server-for-windbg-crash-analysis --env CDB_PATH=<CDB_PATH> --env _NT_SYMBOL_PATH=<_NT_SYMBOL_PATH> -- uvx mcp-windbgReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from mcp-windbg <command>
Config file
{
"mcpServers": {
"mcp-server-for-windbg-crash-analysis": {
"command": "uvx",
"args": [
"mcp-windbg"
],
"env": {
"CDB_PATH": "<CDB_PATH>",
"_NT_SYMBOL_PATH": "<_NT_SYMBOL_PATH>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from mcp-windbg <command>
Config file
{
"servers": {
"mcp-server-for-windbg-crash-analysis": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-windbg"
],
"env": {
"CDB_PATH": "<CDB_PATH>",
"_NT_SYMBOL_PATH": "<_NT_SYMBOL_PATH>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from mcp-windbg <command>
Platform CLI
gemini mcp add -e CDB_PATH=<CDB_PATH> -e _NT_SYMBOL_PATH=<_NT_SYMBOL_PATH> mcp-server-for-windbg-crash-analysis uvx mcp-windbgReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from mcp-windbg <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about MCP Server for WinDbg Crash Analysis
How to install MCP Server for WinDbg Crash Analysis in Claude Code?
Run claude mcp add mcp-windbg -- uvx mcp-windbg. If you need custom debugger or symbol paths, supply the flags: `claude mcp add --env CDB_PATH=<CDB_PATH> --env _NT_SYMBOL_PATH=<_NT_SYMBOL_PATH> --transport stdio mcp-server-for-windbg-crash-analysis -- uvx mcp-windbg`.
How does this compare to Microsoft's official WinDbg MCP?
Microsoft ships an MCP server built into the WinDbg desktop interface. This community tool runs headless via cdb.exe and kd.exe, supporting automated batch dump triage and remote HTTP setups without the UI.
What host requirements are necessary before setup?
The host machine requires Windows, Python 3.10 or higher, and Debugging Tools for Windows (or WinDbg from the Microsoft Store) to supply cdb.exe and kd.exe.
