SSyncDev

Windbg MCP Server

WinDbg/DbgEng over MCP: crash dumps, live user & kernel, driver IOCTLs, and TTD.

Local serverstdioGo

What is the Windbg MCP Server?

WinDbg/DbgEng over MCP: crash dumps, live user & kernel, driver IOCTLs, and TTD.

What you get

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.

Configuration and credentials

  • Windows x64 (host bitness must match the target). - dbgeng.dll / dbghelp.dll — present in System32 on modern Windows 11 (verified with 10.0.26100). This is enough for live user-mode/kernel debugging and crash-dump analysis. - For crash-dump !analyze (and any other !-extension command), the engine needs the WinDbg winext\ extensions bundled next to the binary — System32's

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Configuration

  • Windows x64 (host bitness must match the target). - dbgeng.dll / dbghelp.dll — present in System32 on modern Windows 11 (verified with 10.0.26100). This is enough for live user-mode/kernel debugging and crash-dump analysis. - For crash-dump !analyze (and any other !-extension command), the engine needs the WinDbg winext\ extensions bundled next to the binary — System32's

Example prompts to try

  • “Use Windbg to Group.”
  • “Use Windbg to Session.”
  • “Use Windbg to State.”

Frequently asked questions

WinDbg/DbgEng over MCP: crash dumps, live user & kernel, driver IOCTLs, and TTD. Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.