1. Home
  2. MCP Server for WinDbg Crash Analysis
  3. MCP Server for WinDbg Crash Analysis for Claude Desktop

Data as of

MCP Server for WinDbg Crash Analysis for Claude Desktop

Claude Desktop: Connect MCP assistants to WinDbg/CDB for Windows crash analysis and live remote debugging.

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

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.
  • Compare several dumps for recurring failure patterns.

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

  • 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 Desktop configuration

  1. Choose Claude Desktop configuration scope

    For MCP Server for WinDbg Crash Analysis, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

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

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

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

    MCP Server for WinDbg Crash Analysis: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

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

MCP Server for WinDbg Crash Analysis tools available to Claude Desktop

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

list_windbg_dumps

When Claude Desktop requests list_windbg_dumps from MCP Server for WinDbg Crash Analysis, review the action before approving it.

Find crash dump files for individual or batch investigation.

open_windbg_dump

When Claude Desktop requests open_windbg_dump from MCP Server for WinDbg Crash Analysis, review the action before approving it.

Open a crash dump for debugger analysis.

close_windbg_dump

When Claude Desktop requests close_windbg_dump from MCP Server for WinDbg Crash Analysis, review the action before approving it.

Release an active dump-analysis session.

open_windbg_remote

When Claude Desktop requests open_windbg_remote from MCP Server for WinDbg Crash Analysis, review the action before approving it.

Connect the debugger to a remote live target.

close_windbg_remote

When Claude Desktop requests close_windbg_remote from MCP Server for WinDbg Crash Analysis, review the action before approving it.

run_windbg_cmd

When Claude Desktop requests run_windbg_cmd from MCP Server for WinDbg Crash Analysis, review the action before approving it.

send_ctrl_break

When Claude Desktop requests send_ctrl_break from MCP Server for WinDbg Crash Analysis, review the action before approving it.

MCP Server for WinDbg Crash Analysis: full stored tool descriptions

Troubleshooting MCP Server for WinDbg Crash Analysis in Claude Desktop

  • Fully quit and reopen Claude Desktop for MCP Server for WinDbg Crash Analysis. If python (Python) is missing, check the desktop process's PATH, which may differ from your terminal.
  • In Claude Desktop's MCP Server for WinDbg Crash Analysis entry, check _NT_SYMBOL_PATH. Keep secrets out of shared screenshots and repositories.
  • MCP Server for WinDbg Crash Analysis uses stdio here: Claude Desktop 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 Desktop troubleshooting lives in the /clients/claude-desktop guide.

MCP Server for WinDbg Crash Analysis — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads MCP Server for WinDbg Crash Analysis from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's mcp-windbg example uses stdio.

MCP Server for WinDbg Crash Analysis's Claude Desktop configuration invokes python (Python).

Claude Desktop's MCP Server for WinDbg Crash Analysis example references _NT_SYMBOL_PATH. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

MCP Server for WinDbg Crash Analysis's stored list contains 7 tools, including list_windbg_dumps, open_windbg_dump, close_windbg_dump. Compare those names with Claude Desktop's connected tool list; the stored list is not a live check.

No. The README describes a CDB wrapper that helps a language model investigate crashes, not an automatic-fix solution.

Yes. Tools open remote sessions, run debugger commands, and interrupt execution with CTRL+BREAK.