mcp-windbg
Crash-dump analysis, driven by AI.
Ask "why the access violation?" and your assistant runs the right CDB commands, reads the dump and explains the root cause. Crash dumps, live sessions and the Windows kernel, from Claude, Copilot, Cursor or any MCP client.
- Microsoft
- Intel
- AMD
- NVIDIA
- Citrix
- Tencent
- ByteDance
- Red Hat
- Palo Alto Networks
- Sophos
- BeyondTrust
- Sentry
- Thales
- ZEISS
- Philips
- Mistral AI
- and many more
WinDbg, with a conversation on top.
mcp-windbg wraps the Debugging Tools for Windows in a Model Context Protocol server. The model decides which commands to run. The debugger does the work.
- 01
Crash dump analysis
Open .dmp, .mdmp and .hdmp files or triage a whole directory. The model runs the CDB commands, reads the output and explains the root cause.
- 02
User-mode remote debugging
Attach to a remote debug server, break in, inspect, resume. Sessions carry timeouts, so a hung target never hangs your assistant.
- 03
Kernel debugging
Attach to a kernel target over KD. Drivers, bugchecks and a live kernel, through the same conversation.
- 04
Redaction and transport
Text filter hooks scrub PII and secrets before output reaches the model. Runs over stdio or streamable HTTP.
From "it crashed" to "here is why".
Install the tools, then ask.
Install the prerequisites in PowerShell, then add the plugin from inside Claude Code and point it at a dump. Symbols resolve from the Microsoft symbol server on first use.
- Windows with WinDbg or Debugging Tools for Windows
- Astral uv (includes
uvx) for the plugin - Python 3.10+ for the Manual and VS Code routes
winget install astral-sh.uv
winget install 9PGJGD53TN86 --accept-source-agreements --accept-package-agreements WinDbg supplies cdb.exe and kd.exe, which mcp-windbg finds automatically. Alternatively, install the Windows SDK or WDK with Debugging Tools for Windows selected. If you already have the debugging tools, skip the WinDbg install.
After installing uv, open a new terminal and restart Claude Code so it can find uvx. The plugin handles Python and the server package; a separate Python installation isn't required. See the setup guide for more details.
/plugin marketplace add svnscha/mcp-windbg
/plugin install mcp-windbg-uvx@mcp-windbgpip install mcp-windbg
claude mcp add mcp-windbg -s user \
-e _NT_SYMBOL_PATH="SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols" \
-- python -m mcp_windbg{
"servers": {
"mcp_windbg": {
"type": "stdio",
"command": "python",
"args": ["-m", "mcp_windbg"],
"env": {
"_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"
}
}
}
} > Analyze C:\dumps\app.dmp and tell me why it crashed.
open_cdb_dump C:\dumps\app.dmp
run_cdb_command !analyze -v
run_cdb_command kb
The crash is a null dereference in Renderer::Flush ... For VS Code, run pip install mcp-windbg first, then put the snippet in .vscode/mcp.json. Claude Desktop and Cursor use the same command and arguments.
Ten tools, one debugger.
Every tool maps to something you would do by hand in WinDbg. Sessions carry ids, so several dumps or targets can be open at once.
-
list_dumpsList crash dump files in a directory -
open_cdb_dumpOpen and triage a crash dump -
open_cdb_remoteAttach to a user-mode remote debug server -
open_kd_sessionAttach to a kernel target -
run_cdb_commandRun a command on a user-mode session -
run_kd_commandRun a command on a kernel session -
send_ctrl_breakBreak into a running live session -
wait_for_breakWait for the target to stop after a resume -
close_cdb_sessionClose a user-mode session -
close_kd_sessionClose a kernel session
Articles.
Release notes, the story behind the project, and what AI-assisted crash analysis looks like in practice.
- 🚀 New Release: mcp-windbg 1.5.0
Failed opens no longer leak debugger sessions, a timed-out command on a dump gets cancelled instead of wedging the session, and completion markers are unique per session. Plus what I learned measuring six community pull requests against a real debugger.
- 🚀 New Release: mcp-windbg 1.4.0
A quick follow-up to 1.3.1: open kernel crash dumps with open_kd_dump, and load your debugger extensions automatically with init commands.
- 🚀 New Release: mcp-windbg 1.3.1
Break-in while a command runs, partial output on timeouts, and a debugger that exits is reported right away. Three of the four fixes came from the community.
- 🚀 New Release: mcp-windbg 1.3.0
The MCP server, Claude Code skills, and crash-analysis agent are now separate plugins for use with your preferred installation.
- 🚀 New Release: mcp-windbg 1.2.2
A fix for missing Unicode output on Chinese, Japanese, and Korean Windows systems.
- 🚀 New Release: mcp-windbg 1.2.0
mcp-windbg now ships as a Claude Code plugin with four debugging skills and a crash-analysis agent.
- 🚀 New Release: mcp-windbg 1.1.0
Support for the 2.x MCP SDK, a new wait_for_break tool, and fixes for 'g' freezing the machine it was supposed to release.
- 🚀 New Release: mcp-windbg 1.0.0
Kernel debugging, session IDs, and a redesigned tool surface. The first stable release.
- 🚀 New Release: mcp-windbg 0.15.0
Break into live sessions, redact sensitive output before it reaches the model, and a brand-new documentation site. A year and a month in, with 1.4k stars and a community that keeps showing up.
- 🚀 New Release: mcp-windbg 0.12.2
Adding Prompts API support and streamable-http transport to mcp-windbg.
- 🚀 New Release: mcp-windbg 0.10.0
AI-powered crash analysis gets a major upgrade with PyPI availability, live debugging sessions, and community-driven improvements. One-command installation is finally here.
- AI Meets WinDBG: A Different Way to Analyze Crashes
Because manually squinting at hex dumps is so last century. Let me show you how AI-assisted debugging is leaving WinDBG's command line in the dust.
Built in the open.
mcp-windbg is maintained on GitHub and supported by Liasoft. Stars, issues and pull requests keep it moving.
- GitHub stars
- 1.6k
- Downloads / month
- 2.3k
- License
- MIT