Windbg MCP

An MCP server that exposes WinDbg/DbgEng to AI agents (Claude Code, Claude Desktop, Cursor, …) - over stdio, or over HTTP with --listen, which serves the same tools to clients that are not on the machine DbgEng runs on. It drives a live debugger engine for user-mode, kernel-mode, crash-dump, and Time Travel Debugging (TTD) workflows. Its 9 documented tools cluster into session, inspect, crash, run & execute.

People who work with debugging, windbg and windbgx and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in Rust.

VERIFIED ACTIVE

LAST COMMIT 2026-09-30 · ★ 12 · #142 OF 180 MAINTAINED DEVELOPER TOOLS · VERIFIED 2026-09-30

MIT · Rust servers · how we verify → /methodology

01 · Install Windbg MCP

before you install - you'll need

The README does not document required environment variables for a basic install.

Claude Desktop

Settings → Extensions → Install, then select the https://github.com/glslang/windbg-mcp/releases/download/v0.20.0/windbg-mcp-v0.20.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 9 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. current_location (instruction pointer, execution context, and PE coordinate), registers, read_memory, backtrace (the stack as typed frames, each carrying module

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; exception_triage - the user

crash

run & execute

1 tool - e.g. go, step_over, step_into, set_breakpoint, breakpoints (the session's whole inventory, as records - what to check before resuming or detaching a live target), cl

exec

Batch

1 tool - e.g. debug_batch - an ordered sequence with assertions and a rollback the engine process runs on every path where it can still identify the target it would aim at

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, driver_hazards, ioctl_map - the control codes a dispatch routine ac

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 four 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 set

Latest releases

v0.20.0 · 2026-09-24

Added · The heap_ tools walk ARM64 processes. They refused any processor but AMD64 ("heap walking supports x64 targets only (machine 0xaa64)"), which on an ARM64 debugger host is every target there is - native…

v0.19.0 · 2026-09-20

Fixed · Remote-kernel cleanup now reconciles late confirmed releases and does not preserve returned · pre-commit attach failures. Preserved orphan workers no longer hold the MCP client's stderr · open. Live-test…

v0.18.0 · 2026-09-17

Fixed · Every pool and heap query refused current Windows, over one renamed field. _HEAP_VS_AFFINITY_SLOT::VsContext -- the back-pointer a per-affinity VS slot uses to name the _HEAP_VS_CONTEXT it belongs to -- is…

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

category
developer tools - ranked #142 of 180 actively-maintained developer tools servers as of 2026-09-30.
release cadence
10+ releases in the last 90 days (latest 2026-09-24)
registry
io.github.glslang/windbg-mcp (active, first published 2026-07-23 · 25 versions)
packages
mcpb:https://github.com/glslang/windbg-mcp/releases/download/v0.20.0/windbg-mcp-v0.20.0-windows-x64.mcpb

06 · Windbg MCP FAQ

Is Windbg MCP still maintained?

Yes - as of 2026-09-30, its last commit was 2026-09-30 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

What can Windbg MCP do?

An agent gets 9 documented tools across session, inspect, crash, including session, inspect, crash, exec.

07 · Alternatives to Windbg MCP

More developer tools MCP servers · Trace Weave · Code Review Server · Sabline · Roast My Design System (gregkozakiewicz) · Grid Proof

More Rust MCP servers · Orion · Ground Lens · Stallhunt · Doom MCP · Product CLI · see all