Skip to content
Sven Scharmentke edited this page Oct 11, 2025 · 4 revisions

Usage

VS Code Setup

  1. Create .vscode/mcp.json in your workspace
  2. Enable MCP in Copilot settings
  3. Restart VS Code

See Configuration Guide for details.

VS Code Integration

Basic Commands

Crash Dumps

  • "Analyze the crash dump at C:\dumps\app.dmp"
  • "List all crash dumps in C:\dumps"
  • "Show me the call stack and explain the access violation"
  • "Execute !peb and check environment variables"
  • "Run .ecxr followed by k and explain the exception"

Remote Debugging

  • "Connect to tcp:Port=5005,Server=192.168.0.100"
  • "Show current thread state and check for deadlocks"
  • "Check timing issues with !runaway and !threads"
  • "Show all threads with ~*k and identify hangs"

Command Line

Manual start:

python -m mcp_windbg

Options:

  • --cdb-path - Custom CDB path
  • --symbols-path - Custom symbols
  • --timeout 60 - Timeout in seconds
  • --verbose - Debug output

Other Clients

Works with Claude Desktop and any MCP-compatible client via stdio.

Workflows

Crash Dump Triage

  1. "List all crash dumps in C:\Dumps"
  2. "Analyze dump C:\Dumps\app_crash_001.dmp"
  3. "Show stack trace and examine top 3 frames"
  4. "Check heap state around crashing address"

Remote Debugging

  1. "Connect to tcp:Port=5005,Server=192.168.0.100"
  2. "Show current state - registers, stack, threads"
  3. "List all threads, identify suspicious ones"
  4. "Examine heap for corruption patterns"

Best Practices

  • Configure symbols for meaningful analysis
  • Set appropriate timeouts for complex operations
  • Close sessions when done to free resources
  • Use secure connections for remote debugging

Troubleshooting

Issue Solution
Tools not appearing Verify MCP enabled, restart VS Code
CDB not found Check installation, set --cdb-path
Symbol loading fails Verify symbol path
Timeouts Increase --timeout

Next: Tools Reference | Troubleshooting

Clone this wiki locally