MCP Server for WinDbg Crash Analysis for Claude Code: Setup

What you can do with MCP Server for WinDbg Crash Analysis in Claude Code

Choose it to pair assistant explanations with direct WinDbg/CDB control for Windows investigations.

• Interpret exception context and call stacks from a Windows crash dump.
• Apply trusted text filters before passing debugger content to an assistant.

Before you start: MCP Server for WinDbg Crash Analysis in Claude Code

• Windows
• Python 3.10 or newer
• Debugging Tools for Windows or Microsoft Store WinDbg
• mcp-windbg package installed
• An MCP-compatible client

Install with pip install mcp-windbg before using this documented client launch. Configure symbols for your environment. Streamable HTTP is a separate option; only trusted Python scripts should be supplied as text filters.

MCP Server for WinDbg Crash Analysis Claude Code configuration

1. Choose Claude Code configuration scope

   For MCP Server for WinDbg Crash Analysis, open Project scope: .mcp.json at the repository root. Project JSON: merge into mcpServers; user scope: use the CLI.

2. Add MCP Server for WinDbg Crash Analysis to Claude Code

   Use the mcp-windbg entry below in mcpServers. Keep MCP Server for WinDbg Crash Analysis's documented stdio connection fields and your other Claude Code entries.

3. Check MCP Server for WinDbg Crash Analysis in Claude Code

   MCP Server for WinDbg Crash Analysis: Inspect claude mcp list and /mcp status.

{
  "mcpServers": {
    "mcp-windbg": {
      "type": "stdio",
      "command": "python",
      "args": [
        "-m",
        "mcp_windbg"
      ],
      "env": {
        "_NT_SYMBOL_PATH": "<debugger symbol search path>"
      }
    }
  }
}

claude mcp add-json --scope project 'mcp-windbg' '{"type":"stdio","command":"python","args":["-m","mcp_windbg"],"env":{"_NT_SYMBOL_PATH":"<debugger symbol search path>"}}'

MCP Server for WinDbg Crash Analysis tools available to Claude Code

MCP Server for WinDbg Crash Analysis's stored tool list documents 7 tools; compare it with Claude Code's connected tool list, because the stored list is not a live check.

list_windbg_dumps

For MCP Server for WinDbg Crash Analysis's list_windbg_dumps, review the permission request and arguments in Claude Code before approval.

open_windbg_dump

For MCP Server for WinDbg Crash Analysis's open_windbg_dump, review the permission request and arguments in Claude Code before approval.

close_windbg_dump

For MCP Server for WinDbg Crash Analysis's close_windbg_dump, review the permission request and arguments in Claude Code before approval.

Release an active dump-analysis session.

open_windbg_remote

For MCP Server for WinDbg Crash Analysis's open_windbg_remote, review the permission request and arguments in Claude Code before approval.

Connect the debugger to a remote live target.

close_windbg_remote

For MCP Server for WinDbg Crash Analysis's close_windbg_remote, review the permission request and arguments in Claude Code before approval.

Disconnect and clean up a remote debugging session.

run_windbg_cmd

For MCP Server for WinDbg Crash Analysis's run_windbg_cmd, review the permission request and arguments in Claude Code before approval.

send_ctrl_break

For MCP Server for WinDbg Crash Analysis's send_ctrl_break, review the permission request and arguments in Claude Code before approval.

Interrupt a running debugging target for inspection.

MCP Server for WinDbg Crash Analysis: full stored tool descriptions

Troubleshooting MCP Server for WinDbg Crash Analysis in Claude Code

• If MCP Server for WinDbg Crash Analysis fails to start, check python (Python), the working directory, and Claude Code's selected scope; inspect claude mcp list and /mcp.
• MCP Server for WinDbg Crash Analysis: check _NT_SYMBOL_PATH; keep credentials out of shared .mcp.json.
• MCP Server for WinDbg Crash Analysis uses stdio here: Claude Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Requires Windows and Microsoft's debugging tools.
• Known limitation: Assists investigation rather than automatically fixing crashes.
• Known limitation: Filter scripts execute in-process and must be trusted.
• General Claude Code troubleshooting lives in the /clients/claude-code guide.

Frequently asked questions