WinDbg
A Model Context Protocol server for Windows crash dump analysis using WinDbg/CDB
What is WinDbg?
WinDbg is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to model context protocol server for windows crash dump analysis using windbg/cdb
A Model Context Protocol server for Windows crash dump analysis using WinDbg/CDB
This server falls under the Developer Tools category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- A Model Context Protocol server for Windows crash dump analy
Use Cases
Maintainer
Works with
Installation
NPM
npx -y mcp-windbgPIP
pip install mcp-windbgManual Installation
npx -y mcp-windbgConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use WinDbg
The mcp-windbg server bridges AI coding assistants to the Windows Debugging Tools (WinDbg/CDB), enabling AI-assisted analysis of Windows crash dumps and live debugging sessions directly from your MCP-compatible client. It exposes tools to open dump files, execute WinDbg commands, inspect memory, manage debugging sessions, and connect to remote debug targets — turning what would normally require deep WinDbg expertise into a conversational debugging workflow. This server is particularly valuable for Windows systems engineers and application developers who deal with crash reports, heap corruption, and threading issues, as it lets an AI assistant interpret raw dump output and suggest root causes.
Prerequisites
- Windows operating system (the server only supports Windows)
- Windows Debugging Tools installed — either via 'Debugging Tools for Windows' from the Windows SDK, or WinDbg from the Microsoft Store
- Python 3.10+ installed on the Windows machine
- An MCP-compatible client such as Claude Desktop, GitHub Copilot in VS Code, Cursor, or Windsurf
- Symbol server access configured via the _NT_SYMBOL_PATH environment variable (optional but strongly recommended)
Install mcp-windbg via pip
Install the package from PyPI on your Windows machine. Python 3.10 or higher is required.
pip install mcp-windbgConfigure the symbol server path
Set the _NT_SYMBOL_PATH environment variable to point to the Microsoft public symbol server. This is critical for meaningful stack traces — without symbols, WinDbg output will show only addresses.
set _NT_SYMBOL_PATH=SRV*C:\Symbols*https://msdl.microsoft.com/download/symbolsAdd mcp-windbg to your MCP client configuration
Add the server entry to your client config. For VS Code with GitHub Copilot, edit .vscode/mcp.json. For Claude Desktop, edit claude_desktop_config.json.
{
"servers": {
"mcp_windbg": {
"type": "stdio",
"command": "python",
"args": ["-m", "mcp_windbg"],
"env": {
"_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"
}
}
}
}Restart your MCP client
Reload or restart the client application so it picks up the new server configuration and registers the WinDbg tools.
Open a crash dump for analysis
Ask your AI assistant to open a .dmp file using the open_windbg_dump tool. Provide the full path to the dump file.
Run WinDbg commands via the AI
Use the run_windbg_cmd tool to execute any WinDbg command (e.g. !analyze -v, k, !heap -x) and ask the AI to interpret the results.
WinDbg Examples
Client configuration
Configuration for Claude Desktop on Windows. Adjust the symbol cache path as needed.
{
"mcpServers": {
"mcp_windbg": {
"command": "python",
"args": ["-m", "mcp_windbg"],
"env": {
"_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"
}
}
}
}Prompts to try
Example prompts for analyzing Windows crash dumps with AI assistance.
- "Open the crash dump at C:\\Dumps\\app_crash.dmp and give me a summary of what caused it"
- "Run !analyze -v on the open dump and explain the exception record"
- "Show me the call stack for all threads and identify which thread caused the crash"
- "Check for heap corruption in the open dump using !heap -x"
- "Connect to a remote debug target at localhost:5005 and list all running threads"
- "List all available crash dumps in C:\\Dumps\\ and open the most recent one"Troubleshooting WinDbg
Server fails to start with 'cdb.exe not found' or 'WinDbg not found'
Install the Windows Debugging Tools from the Windows SDK installer (select 'Debugging Tools for Windows' component) or install WinDbg Preview from the Microsoft Store. The mcp_windbg module searches standard installation paths automatically.
Stack traces show only hex addresses with no symbol names
The _NT_SYMBOL_PATH environment variable is either missing or incorrect. Set it to 'SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols' and ensure C:\Symbols exists and is writable. First-time symbol downloads can be slow while the cache is populated.
'python -m mcp_windbg' fails with module not found
Confirm the package installed correctly with 'pip show mcp-windbg'. If using a virtual environment, activate it before starting the MCP client. Alternatively, use uvx: 'uvx --from git+https://github.com/svnscha/mcp-windbg mcp-windbg' as the command in your config.
Frequently Asked Questions about WinDbg
What is WinDbg?
WinDbg is a Model Context Protocol (MCP) server that model context protocol server for windows crash dump analysis using windbg/cdb It connects AI assistants to external tools and data sources through a standardized interface.
How do I install WinDbg?
Install via npm with the command: npx -y mcp-windbg. Then add the server configuration to your AI client's JSON config file (e.g., claude_desktop_config.json or .cursor/mcp.json).
Which AI clients work with WinDbg?
WinDbg works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is WinDbg free to use?
Yes, WinDbg is open source and available under the MIT license. You can use it freely in both personal and commercial projects.
WinDbg Alternatives — Similar Developer Tools Servers
Looking for alternatives to WinDbg? Here are other popular developer tools servers you can use with Claude, Cursor, and VS Code.
Ecc
★ 188.2kThe agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Javaguide
★ 155.8kJava 面试 & 后端通用面试指南，覆盖计算机基础、数据库、分布式、高并发、系统设计与 AI 应用开发
Gemini CLI
★ 104.5kA secure MCP server that wraps the Google Gemini CLI, allowing clients to query Gemini models using local OAuth sessions without requiring an API key. It provides tools for model interaction and diagnostics with built-in protection against command in
Awesome MCP Servers
★ 87.3k⭐ Curated list of Model Context Protocol (MCP) servers - tools that extend Claude Desktop, Cursor, Windsurf, and other MCP clients with custom capabilities.
MCP Servers
★ 86.0kModel Context Protocol Servers
CC Switch
★ 77.5kA cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io
Browse More Developer Tools MCP Servers
Explore all developer tools servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up WinDbg in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use WinDbg?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.