🚀 New Release: mcp-windbg 1.3.0

Posted on 2026-09-10 - ai debugging mcp-windbg claude-code crash-analysis plugin release

On this page

Three Separate Plugins
Skills and Agents for Your Existing Server
Upgrading from the Bundled Plugin

Version 1.3.0 of mcp-windbg separates the Claude Code integration into three plugins. If you've already installed mcp-windbg yourself, you can now add the debugging skills and crash-analysis agent to that connection.

Three Separate Plugins

The 1.2.0 release bundled the server, skills, and agent together. I split them so you can choose the parts you need:

Plugin	What it provides
`mcp-windbg-uvx`	The MCP server, launched with uvx, and default symbol settings
`mcp-windbg-skills`	Four debugging skills
`mcp-windbg-agents`	The `crash-analyst` agent

The uvx plugin now ships only the server configuration. Skills and agents are independent: install either, both, or neither.

Skills and Agents for Your Existing Server

If mcp-windbg is already registered in Claude Code, add the marketplace and install the workflows you want:

/plugin marketplace add svnscha/mcp-windbg
/plugin install mcp-windbg-skills@mcp-windbg
/plugin install mcp-windbg-agents@mcp-windbg

The skills cover the same four tasks:

analyze-dump for crash dump analysis.
debug-remote for live user-mode debugging.
kernel-debug for live kernel debugging.
windbg-doctor for checking the debugging setup.

They use your configured MCP connection, whether it runs a native executable, a Python installation, or an HTTP service. Setup diagnosis checks that server's actual launcher and host. It no longer assumes every installation needs uv.

For example:

/mcp-windbg-skills:analyze-dump C:\dumps\app.dmp

The agent is available as mcp-windbg-agents:crash-analyst. It investigates a dump and reports its likely cause, debugger evidence, and next steps. It uses the MCP tools directly and does not need the skills plugin.

If you want the plugin to start the server through uvx, install it as well:

/plugin install mcp-windbg-uvx@mcp-windbg

Windows and CDB/KD are still required on the debugging host. The server's built-in MCP prompts are available independently of these plugins.

Enterprise environments: Managed allowedMcpServers settings can cause Claude Code to silently skip plugin-bundled MCP servers (issue #32882). I recommend manual installation and registration plus the skills plugin, with the agents plugin if needed. The server must still be permitted by your organization's MCP policy.

Upgrading from the Bundled Plugin

Update the marketplace and server plugin:

/plugin marketplace update mcp-windbg
/plugin update mcp-windbg-uvx@mcp-windbg

Then install the skills and agents plugins using the commands above if you want to keep those workflows.

Skill commands now start with /mcp-windbg-skills: instead of /mcp-windbg:. For example, /mcp-windbg:analyze-dump becomes /mcp-windbg-skills:analyze-dump. References to the agent should use mcp-windbg-agents:crash-analyst. Restart Claude Code if the new components do not appear.

See the full v1.3.0 release notes and the plugin guide for installation, switching servers, and updating each plugin.