Windbg MCP
An MCP server that exposes WinDbg/DbgEng to AI agents (Claude Code, Claude Desktop, Cursor, …) over stdio. It drives a live debugger engine for user-mode, kernel-mode, crash-dump, and Time Travel Debugging (TTD) workflows. Its 8 documented tools cluster into session, inspect, crash, run & execute.
People who need developer tools tools inside Claude, Cursor, VS Code, or another MCP client. The project is written in Rust.
VERIFIED ACTIVE
LAST COMMIT 2026-08-24 · ★ 7 · #118 OF 139 MAINTAINED DEVELOPER TOOLS · VERIFIED 2026-08-25
MIT · Rust servers · how we verify → /methodology
01 · Install Windbg MCP
Claude Desktop
Settings → Extensions → Install, then select the https://github.com/glslang/windbg-mcp/releases/download/v0.11.0/windbg-mcp-v0.11.0-windows-x64.mcpb .mcpb bundle 02 · Evidence
Security posture
What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.
runs as Claude Desktop extension (.mcpb bundle)
license MIT - declared in the repository
registry namespace io.github.glslang is GitHub-verified and matches the repo owner
03 · What Windbg MCP can do
Prose above is summarized from the project's README and registry record - no invented capabilities.
What you can build
An agent gets 8 documented tools across session, inspect, crash, including session, inspect, crash, exec.
Capability map
Tools grouped from the project's README - what Windbg MCP lets an agent do.
Session
1 tool - e.g. open_dump, open_trace, attach_kernel_local, attach_kernel, attach_process, launch, interrupt, end_session, session_status
session
Inspect
1 tool - e.g. registers, read_memory, backtrace (the stack as typed frames, each carrying module+RVA where the engine can place it, as well as its symbol), modules, threads,
inspect
Crash
1 tool - e.g. crash_triage - a bug check as fields: code and parameters, crashing process, the stack as module+RVA, and the faulting driver frame
crash
run & execute
1 tool - e.g. go, step_over, step_into, set_breakpoint, run_to_address
exec
Batch
1 tool - e.g. debug_batch - an ordered sequence with assertions and a rollback the engine process runs on every path
batch
Ttd
1 tool - e.g. step_back (t-), step_over_back (p-), reverse_go (g-), goto_position (!tt)
ttd
Ioctl
1 tool - e.g. decode_ioctl, driver_object, device_object, irp_stack, ioctl_trace, reachable_from_dispatch
ioctl
Allocator
1 tool - e.g. pool_find_tag, pool_chunk, pool_census, pool_diagnostics
allocator
Limitations (from the README)
The full list, with what each one means for a workflow, is in docs/limitations.md. The three that catch people first: - TTD is user-mode only - a Microsoft limitation, so a kernel target cannot be time-travelled. - One command at a time per session. Sessions run concurrently, but each is one engine running operations serially: await each result before sending the next call against that session. - Symbol names need se
Latest releases
v0.11.0 · 2026-08-23
Added · A tool surface per client, not just per server (FOLLOWUPS.md item 36, which closes it). A · --listen server names its clients already, and they do not have one budget between them: the · arrangement this…
v0.10.0 · 2026-08-20
Added · --listen: the same tool surface over HTTP, so the client and the model need not be on the · debugger host (#135). DbgEng is Windows-only · and holds one debuggee per process; nothing about the client has to be.…
v0.9.0 · 2026-08-14
Changed · modules renders its listing from its own values, and no longer runs lm · (#120). It was the one tool whose text was · the debugger's rendering rather than a rendering of its own records: the text came from…
04 · Who maintains Windbg MCP
windbg-mcp is maintained by glslang. It's the only MCP server we track from this author; the repo dates to May 2026.
05 · Facts
- repository
- github.com/glslang/windbg-mcp
- category
- developer tools - ranked #118 of 139 actively-maintained developer tools servers as of 2026-08-25.
- release cadence
- 10+ releases in the last 90 days (latest 2026-08-23)
- registry
- io.github.glslang/windbg-mcp (active, first published 2026-07-23 · 13 versions)
- packages
- mcpb:https://github.com/glslang/windbg-mcp/releases/download/v0.11.0/windbg-mcp-v0.11.0-windows-x64.mcpb
06 · Windbg MCP FAQ
Is Windbg MCP still maintained?
Yes - as of 2026-08-25, its last commit was 2026-08-24 and it shipped 10+ releases in the last 90 days. We re-verify nightly.
What can Windbg MCP do?
An agent gets 8 documented tools across session, inspect, crash, including session, inspect, crash, exec.
07 · Alternatives to Windbg MCP
Alternatives to Windbg MCP
Maintained developer tools servers if Windbg MCP isn't the fit.
- Xcode Build MCP XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities. ★ 6,274 · 2026-08-12
- Strata MCP server for progressive tool usage at any scale (see https://klavis.ai) ★ 5,794 · 2026-06-01
- Kubefwd Kubernetes port forwarding for local development with automatic /etc/hosts entries. ★ 4,162 · 2026-08-21
- Sem Entity-level code intelligence: semantic diff, impact analysis, blame, and context for AI agents ★ 3,309 · 2026-08-24
- Claude Code Explorer MCP Explore the Claude Code CLI source - browse tools, commands, search code, and more. ★ 3,263 · 2026-04-22
- Server for WinDbg Crash Analysis A Model Context Protocol server for Windows crash dump analysis using WinDbg/CDB ★ 1,533 · 2026-08-22
Pairs well with
Servers that cover what Windbg MCP doesn't - only shown when the pairing reason fits the companion.
More developer tools MCP servers · Code Review Server · Grid Proof · Batch Review · Grok MCP · Proof Flow
More Rust MCP servers · Orion · Doom MCP · Product CLI · Dbmcp · Hwatu · see all