mcp-windbg
mcp-windbg is a Model Context Protocol server that bridges AI models and WinDbg for crash dump analysis and remote debugging. It wraps Microsoft's CDB debugger so you can ask in natural language, for example "show me the call stack and explain this access violation". It supports three modes: analyzing Windows crash dumps, connecting to remote debugging targets, and processing a directory of dumps to find patterns. The README is candid about its limits, with a section titled "What This is Not" saying it is not a magical auto-fix, only a Python wrapper around CDB that uses the LLM's knowledge to assist debugging.
It needs Windows with Debugging Tools for Windows or WinDbg from the Microsoft Store, Python 3.10 or newer and any MCP client such as GitHub Copilot or Claude Desktop. Install with `pip install mcp-windbg`. The default transport is stdio, and `--transport streamable-http --host 127.0.0.1 --port 8000` serves it over HTTP at `/mcp`. Options include a custom `cdb.exe` path, a symbols path and a command timeout (30 seconds by default). The README includes VS Code configuration steps, and the project is MIT licensed.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-10
- Commits, last 90 days
- 50
- Releases, last 90 days
- 10
- Latest release
- v1.5.1 (2026-10-10)
- Open issues
- 7
- Recent issues with at least one comment
- 4/9
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #130 Follow-up safety gaps: native marker framing, bounded output, and reliable cleanup2 comments · 2026-10-04
- #151 Reader thread: debugger exit right after a command's marker replaces its output with an empty list1 comments · 2026-10-15
- #152 Debugger output is only in tool responses: add a persistent, live log0 comments · 2026-10-17
- #146 Agent safety: warn about CDB server NUL/EOF stdin exhausting nonpaged pool0 comments · 2026-10-10
- #140 open_cdb_remote: a connected target may legitimately be running, and .echo is not proof of readiness0 comments · 2026-10-08
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!