Maintained by an individual developer (repository svnscha/mcp-windbg, MIT license); it is not an official Microsoft or MCP protocol project. It wraps cdb.exe / kd.exe behind ten MCP tools covering dump analysis, user-mode remote debugging, kernel debugging, bulk triage, and output filtering, with stdio and streamable-HTTP transports plus a Claude Code plugin and VS Code client config. It suits Windows developers doing crash and driver triage who already use an MCP client; it is not for non-Windows environments or users expecting automatic fixes. Before use, confirm the debugging tools are installed, understand that live and kernel sessions interrupt targets, and use a filter script to control sensitive data exposure.
Strongest · Documentation 17/20 Weakest · Reliability 11/20
Static review · not runListed 2026-09-10
Read the FMRS scoring method →Runtime：Python 3.10+ · Prebuilt binary
CDB_PATH
Optional custom path to cdb.exe for when Debugging Tools for Windows is not installed in the default location; no credentials needed.
{
"servers": {
"mcp_windbg": {
"type": "stdio",
"command": "python",
"args": ["-m", "mcp_windbg"],
"env": {
"_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"
}
}
}
}
Shown for Claude Code. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.
{
"servers": {
"mcp_windbg": {
"type": "stdio",
"command": "python",
"args": [
"-m",
"mcp_windbg"
],
"env": {
"_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"
}
}
}
}
Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).
claude mcp add mcp_windbg -e '_NT_SYMBOL_PATH=SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols' -- python -m mcp_windbg
Run it in a terminal; replace any <…> placeholders with your own values first.
After restarting the client, the tool list should show the ten tools such as open_cdb_dump and run_cdb_command; then ask it to analyze C:\dumps\app.dmp — if it returns the !analyze -v triage output, the connection works.
Once connected, you can ask your AI assistant things like:
No matching tools
Listed from the project's documentation, not tested by this site.
A Model Context Protocol server that bridges AI models with WinDbg for Windows crash dump analysis, user-mode remote debugging, and kernel debugging. Under the hood it drives the Windows debuggers: CDB for user mode (dumps and -remote) and KD for kernel targets (-k). It is not a magical auto-fix, but a Python wrapper around cdb.exe / kd.exe that lets an LLM run real debugger commands and reason about the output. Every open_* call returns a session_id so several sessions (dumps, remote, kernel) can be open at once and addressed independently; per-call timeouts break into slow live commands with CTRL+BREAK and resynchronize the session. It runs locally over stdio or as a streamable-HTTP service you can drive from another machine, and a --filter-script can redact PII/secrets from tool arguments and output before they leave the machine.
Upstash's official server providing up-to-date third-party library docs for AI coding assistants
AI-powered NPM package analysis MCP server
An independent control layer that gives AI coding agents budgets, brakes, and receipts
GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
Source revision 48e4350d57c4 Data synced 2026-10-19 Read the FMRS scoring method