MCP Server for WinDBG Crash Analysis
About
An AI-powered MCP server that bridges language models with WinDbg for Windows crash dump analysis and live remote debugging. It wraps Microsoft’s CDB debugger and lets developers issue natural‑language debugging commands through any MCP‑compatible client.
Details
- Author
- svnscha
- GitHub stars
- 1,404
- Downloads
- 828
- Categories
- Other
Jump to
- Bridges AI models with WinDbg for crash dump analysis.
- Supports crash dump, live debugging, and directory analysis modes.
- Provides tools: list/open/close dumps, remote session, run commands, send break.
- Redacts sensitive data via optional filter script hooks.
- Compatible with any MCP‑enabled client (Copilot, Claude, Cursor, etc.).
- Uses CDB backend; requires Debugging Tools for Windows.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MCP Server for WinDBG Crash AnalysisCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install via pip install mcp-windbg, then configure the server in your MCP client (e.g., VS Code, Claude Desktop). Start with mcp-windbg (stdio) or with --transport streamable-http for HTTP. Use queries like “Analyze the crash dump at C:\dumps\app.dmp” to run debugger commands.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp server for windbg crash analysis": {
"mcp_windbg": {
"command": "python",
"args": [
"-m",
"mcp_windbg"
],
"env": {
"_NT_SYMBOL_PATH": ""
}
}
}
}
}McpServers
{
"mcp_windbg": {
"command": "python",
"args": [
"-m",
"mcp_windbg"
],
"env": {
"_NT_SYMBOL_PATH": ""
}
}
}MCP Server for WinDbg Crash Analysis
A Model Context Protocol server that bridges AI models with WinDbg for crash dump analysis and remote debugging.
<!-- mcp-name: io.github.svnscha/mcp-windbg -->
Overview
This MCP server integrates with CDB to enable AI models to analyze Windows crash dumps and connect to remote debugging sessions using WinDbg/CDB.
What is this?
An AI-powered tool that bridges LLMs with WinDbg for crash dump analysis and live debugging. Execute debugger commands through natural language queries like "Show me the call stack and explain this access violation".
What This is Not
Not a magical auto-fix solution. It's a Python wrapper around CDB that leverages LLM knowledge to assist with debugging.
Usage Modes
- Crash Dump Analysis: Examine Windows crash dumps
- Live Debugging: Connect to remote debugging targets
- Directory Analysis: Process multiple dumps for patterns
Quick Start
Prerequisites
- Windows with Debugging Tools for Windows or WinDbg from Microsoft Store. - Python 3.10 or higher - Any MCP-compatible client (GitHub Copilot, Claude Desktop, Cline, Cursor, Windsurf etc.) - Configure MCP server in your chosen client> [!TIP]
> In enterprise environments, MCP server usage might be restricted by organizational policies. Check with your IT team about AI tool usage and ensure you have the necessary permissions before proceeding.
Installation
pip install mcp-windbg
Transport Options
The MCP server supports multiple transport protocols:
| Transport | Description | Use Case |
|-----------|-------------|----------|
| stdio (default) | Standard input/output | Local MCP clients like VS Code, Claude Desktop |
| streamable-http | Streamable HTTP | Modern HTTP clients with bidirectional streaming |
Starting with Different Transports
Standard I/O (default):
```bash
mcp-windbg
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
