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 8 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-18 · ★ 11 · #136 OF 168 MAINTAINED DEVELOPER TOOLS · VERIFIED 2026-09-18

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.18.0/windbg-mcp-v0.18.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. 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, 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, 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.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…

v0.17.0 · 2026-09-14

Fixed · Flags computed from the control code, with the code still where it was. The loss check asked whether a register that carried the code had stopped carrying it, and the test clause beside it asked about operand…

v0.16.0 · 2026-09-07

Added · exception_triage - a user-mode fault as fields, which is crash_triage's counterpart for a · process rather than a machine. The exception record with its code decoded, what kind of fault it · is, the thrown C++…

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 #136 of 168 actively-maintained developer tools servers as of 2026-09-18.
release cadence: 10+ releases in the last 90 days (latest 2026-09-17)
registry: io.github.glslang/windbg-mcp (active, first published 2026-07-23 · 23 versions)
packages: mcpb:https://github.com/glslang/windbg-mcp/releases/download/v0.18.0/windbg-mcp-v0.18.0-windows-x64.mcpb

06 · Windbg MCP FAQ

Is Windbg MCP still maintained?

Yes - as of 2026-09-18, its last commit was 2026-09-18 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.

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 · Trace Weave · Code Review Server · Velaris · Grid Proof · Markupr Plus

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