Data as of

MCP Server for WinDbg Crash Analysis for Windsurf: Setup

Windsurf: 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 Windsurf

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

  • Compare several dumps for recurring failure patterns.
  • Apply trusted text filters before passing debugger content to an assistant.

Before you start: MCP Server for WinDbg Crash Analysis in Windsurf

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

  1. Choose Windsurf configuration scope

    For MCP Server for WinDbg Crash Analysis, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

  2. Add MCP Server for WinDbg Crash Analysis to Windsurf

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

  3. Check MCP Server for WinDbg Crash Analysis in Windsurf

    MCP Server for WinDbg Crash Analysis: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_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 Windsurf

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

list_windbg_dumps

After refreshing MCP Server for WinDbg Crash Analysis in Windsurf settings, check Cascade's tool list for list_windbg_dumps.

Find crash dump files for individual or batch investigation.

open_windbg_dump

After refreshing MCP Server for WinDbg Crash Analysis in Windsurf settings, check Cascade's tool list for open_windbg_dump.

Open a crash dump for debugger analysis.

close_windbg_dump

After refreshing MCP Server for WinDbg Crash Analysis in Windsurf settings, check Cascade's tool list for close_windbg_dump.

open_windbg_remote

After refreshing MCP Server for WinDbg Crash Analysis in Windsurf settings, check Cascade's tool list for open_windbg_remote.

Connect the debugger to a remote live target.

close_windbg_remote

After refreshing MCP Server for WinDbg Crash Analysis in Windsurf settings, check Cascade's tool list for close_windbg_remote.

run_windbg_cmd

After refreshing MCP Server for WinDbg Crash Analysis in Windsurf settings, check Cascade's tool list for run_windbg_cmd.

send_ctrl_break

After refreshing MCP Server for WinDbg Crash Analysis in Windsurf settings, check Cascade's tool list for send_ctrl_break.

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 Windsurf

  • Check python (Python) on the machine running Windsurf's MCP integration for MCP Server for WinDbg Crash Analysis; refresh MCP and inspect Cascade's tools.
  • Check _NT_SYMBOL_PATH for MCP Server for WinDbg Crash Analysis; do not bypass a Windsurf permission error with a broad administrator token.
  • MCP Server for WinDbg Crash Analysis uses stdio here: Windsurf 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 Windsurf troubleshooting lives in the /clients/windsurf guide.

MCP Server for WinDbg Crash Analysis — details. Windsurf guide

Frequently asked questions

Windsurf reads MCP Server for WinDbg Crash Analysis under mcpServers in ~/.codeium/windsurf/mcp_config.json on macOS/Linux; Windows uses %USERPROFILE%\.codeium\windsurf\mcp_config.json.

Windsurf's mcp-windbg example uses stdio.

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

Windsurf'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 Windsurf's connected tool list; the stored list is not a live check.

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

An optional trusted Python script can process tool input and output text. It runs inside the server process.