mcp-windbg MCP — ユースケース, インストール & ライブデモ

なぜ使うのか

主な機能

Crash dump analysis with AI-assisted interpretation
Live remote debugging connections
Batch processing of multiple dump files
7 MCP tools for complete debugging workflows
Multiple transport protocols: stdio and streamable HTTP

ライブデモ

実際の動作

mcp-windbg.replay ▶ 準備完了

0/0

インストール

クライアントを選択

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "mcp-windbg": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/svnscha/mcp-windbg"
      ]
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config を開く。保存後、アプリを再起動。

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "mcp-windbg": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/svnscha/mcp-windbg"
      ]
    }
  }
}

Cursor は Claude Desktop と同じ mcpServers スキーマを使用。プロジェクト設定はグローバルより優先。

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "mcp-windbg": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/svnscha/mcp-windbg"
      ]
    }
  }
}

Cline サイドバーの MCP Servers アイコンをクリックし、"Edit Configuration" を選択。

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcp-windbg": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/svnscha/mcp-windbg"
      ]
    }
  }
}

Claude Desktop と同じ形式。Windsurf を再起動して反映。

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "mcp-windbg",
      "command": "TODO",
      "args": [
        "See README: https://github.com/svnscha/mcp-windbg"
      ]
    }
  ]
}

Continue はマップではなくサーバーオブジェクトの配列を使用。

~/.config/zed/settings.json

{
  "context_servers": {
    "mcp-windbg": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/svnscha/mcp-windbg"
        ]
      }
    }
  }
}

context_servers に追加。保存時に Zed がホットリロード。

claude mcp add mcp-windbg -- TODO 'See README: https://github.com/svnscha/mcp-windbg'

ワンライナー。claude mcp list で確認、claude mcp remove で削除。

ユースケース

実用的な使い方： mcp-windbg

How to analyze a Windows crash dump with AI assistance

👤 Windows developers investigating application crashes ⏱ ~30 min intermediate

使うタイミング： You have a .dmp file from a crash and need to understand what happened.

前提条件

Windows with Debugging Tools/WinDbg — Install from Microsoft Store or Windows SDK
mcp-windbg installed — pip install mcp-windbg

フロー

Open the dump

Open the crash dump at C:\dumps\app_crash.dmp. Run !analyze -v and explain what caused the crash.✓ コピーしました

→ Detailed crash analysis with exception type, faulting module, and call stack
Investigate the call stack

Show me the full call stack of the faulting thread. What was the application doing when it crashed?✓ コピーしました

→ Annotated call stack with function descriptions
Check for patterns

Run !locks and !heap -s. Is there a deadlock or heap corruption?✓ コピーしました

→ Lock/heap analysis results with interpretation

結果： Root cause of the crash identified with a clear explanation.

注意点

Missing symbol files — Set up a symbol path: .sympath SRV*c:\symbols*https://msdl.microsoft.com/download/symbols

組み合わせ： filesystem

Batch analyze multiple crash dumps to find patterns

👤 Support engineers investigating recurring crashes ⏱ ~45 min intermediate

使うタイミング： You have multiple crash dumps from the same application and need to find common patterns.

前提条件

mcp-windbg and WinDbg installed — pip install mcp-windbg

フロー

List available dumps

List all crash dump files in C:\dumps\. How many are there and when were they created?✓ コピーしました

→ List of dumps with timestamps
Analyze and compare

Open each dump, run !analyze -v, and give me a summary comparing the crash reasons. Are they the same bug or different issues?✓ コピーしました

→ Comparison table showing crash type, module, and stack similarity

結果： Pattern analysis across multiple crashes to prioritize fixes.

注意点

Large dumps take time to analyze — Start with minidumps if available — they're faster to open

組み合わせ： filesystem

組み合わせ

他のMCPと組み合わせて10倍の力を

mcp-windbg + filesystem

Export crash analysis reports to files for bug tracking

Analyze all dumps in C:\dumps\ and write a summary report to C:\reports\crash-analysis.md.✓ コピーしました

ツール

このMCPが提供する機能

ツール	入力	呼び出すタイミング
list_windbg_dumps	directory: str	Discover crash dump files in a directory
open_windbg_dump	dump_path: str	Open and analyze a crash dump
close_windbg_dump	session_id: str	Close a dump analysis session
open_windbg_remote	connection_string: str	Connect to a remote debug target
run_windbg_cmd	session_id: str, command: str	Execute any WinDbg command in a session
send_ctrl_break	session_id: str	Break into a running debug target

コストと制限

運用コスト

APIクォータ: N/A — fully local
呼び出しあたりのトークン: 300–3000 tokens per command output
金額: Free — WinDbg is free from Microsoft
ヒント: Use targeted WinDbg commands (!analyze -v, k) instead of verbose outputs to reduce tokens.

セキュリティ

権限、シークレット、影響範囲

認証情報の保管： N/A for local dumps. Remote debugging may require authentication.

データ送信先： Local analysis only. Symbol downloads go to Microsoft's symbol server.

⚠ This tool is designed for authorized security research, CTF competitions, and defensive analysis only. Do not use it against systems you don't own or have written authorization to test.
Crash dumps may contain sensitive data (memory contents, credentials). Handle them securely.
Live debugging can affect the target process — use with caution on production systems.

トラブルシューティング

よくあるエラーと対処法

WinDbg/CDB not found

Install Debugging Tools for Windows from the Windows SDK or WinDbg from Microsoft Store.

確認： where cdb

Symbols not loading

Configure symbol path: run_windbg_cmd with '.sympath SRV*c:\symbols*https://msdl.microsoft.com/download/symbols' then '.reload'

確認： Run 'lm' to check loaded modules

Dump file corrupted or incomplete

The dump may be a minidump missing key data. Request a full dump from the application or use procdump to capture a new one.

確認： Check dump file size — minidumps are typically <100MB

代替案

mcp-windbg 他との比較

代替案	代わりに使う場面	トレードオフ
cheatengine-mcp-bridge	You need live memory analysis of running processes rather than crash dump analysis	Live process manipulation vs post-mortem analysis

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る