WinDbg

listing.by

Analyze Windows crash dumps and debug live user-mode or kernel targets through WinDbg (CDB and KD) in natural language.

state.local.long (state.local.title)listing.badge.runs_with

listing.install

listing.local.explain

uvx mcp-windbg

listing.local.needs listing.local.note

  • CDB_PATH listing.env.optional Custom path to cdb.exe (optional)
  • _NT_SYMBOL_PATH listing.env.optional Symbol path for Windows debugging (optional, defaults to Microsoft symbol server)
act.add_to a11y.new_tabact.add_to a11y.new_tab

listing.share.h

listing.share.p_local

mcp.tc/i/windbg

listing.about

Wraps the Windows debuggers cdb.exe and kd.exe so an assistant can open crash dumps, run triage such as !analyze -v, attach to remote user-mode debug servers, attach to kernel targets, and run arbitrary debugger commands. Several sessions can be open at once, and a directory of dumps can be listed and compared.

It runs locally over stdio with uvx mcp-windbg, or as a streamable-HTTP service. No sign-in or API key is needed. Windows is required, with Debugging Tools for Windows or WinDbg from the Microsoft Store installed. Optional environment variables are CDB_PATH and _NT_SYMBOL_PATH.

listing.can

  • Open and triage .dmp crash dumps
  • Attach to user-mode remote debug servers
  • Attach to kernel targets over KDNET, pipe or serial
  • Run any WinDbg or KD command in an open session
  • Break into running live sessions and wait for the next stop
  • List and compare dumps in a directory
  • Redact sensitive output with an optional filter script

listing.tools

listing.notools.local

listing.prompts

  • List the crash dumps in C:\Dumps and open the newest one.

  • Show me the call stack and explain this access violation.

  • Open a kernel session and tell me which driver bugchecked.

  • Triage all dumps in this folder and find the common signature.

listing.setup.h

listing.setup.local

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio windbg -- uvx mcp-windbg
  1. Start Claude Code and type /mcp. windbg should show as connected.

Add --scope user to make it available in every project.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "windbg": {
      "command": "uvx",
      "args": [
        "mcp-windbg"
      ]
    }
  }
}
  1. Save the file and restart Claude Desktop.

Needs uv (Python) on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "windbg": {
      "command": "uvx",
      "args": [
        "mcp-windbg"
      ]
    }
  }
}

Needs uv (Python) on your computer.

VS Code

Install in VS Code a11y.new_tab

Or from a terminal:

code --add-mcp '{"name":"windbg","type":"stdio","command":"uvx","args":["mcp-windbg"]}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "windbg": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-windbg"
      ]
    }
  }
}

Needs uv (Python) on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "windbg": {
      "command": "uvx",
      "args": [
        "mcp-windbg"
      ]
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add windbg -- uvx mcp-windbg

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.windbg]
command = "uvx"
args = ["mcp-windbg"]

Needs uv (Python) on your computer.

Gemini CLI

gemini mcp add windbg uvx mcp-windbg

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "windbg": {
      "command": "uvx",
      "args": [
        "mcp-windbg"
      ]
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs uv (Python) on your computer.

listing.faq

Can I paste mcp.tc/i/windbg into my MCP client?

No. WinDbg runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is uvx mcp-windbg.

Does WinDbg need an API key?

No. It doesn't declare any keys or environment variables. It runs with your user account's permissions, so check what its tools can reach.

Is WinDbg a remote or a local server?

Local. Your client starts it as a process on your computer with uvx mcp-windbg, which needs uv (Python).

What can WinDbg do?

You can open and triage .dmp crash dumps, attach to user-mode remote debug servers and attach to kernel targets over KDNET, pipe or serial.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc's robot read WinDbg's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead_local listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![WinDbg on mcp.tc](https://mcp.tc/i/windbg/badge.svg)](https://mcp.tc/i/windbg)
HTML
<a href="https://mcp.tc/i/windbg"><img src="https://mcp.tc/i/windbg/badge.svg" alt="WinDbg on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/windbg.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/windbg" title="WinDbg on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json_local

https://mcp.tc/i/windbg.json

listing.em.fields

listing.related

listing.more_in

  • Agent Device

    Callstack

    state.local.label (state.local.title)

    Drive iOS and Android apps on simulators, emulators and devices so coding agents can verify their changes.

    mcp.tc/i/agent-device

  • ROS MCP Server

    robotmcp

    state.local.label (state.local.title)

    Connect LLMs to ROS and ROS 2 robots to work with topics, services, actions and parameters through rosbridge.

    mcp.tc/i/ros

  • MATLAB

    MathWorks

    state.local.label (state.local.title)

    Run MATLAB code, tests and static code analysis from an AI assistant using a local MATLAB install.

    mcp.tc/i/matlab

  • Google Colabvf.sr

    Google (Colab)

    state.local.label (state.local.title)

    Connect a local agent to a Google Colab notebook session open in your browser.

    mcp.tc/i/colab

  • Jupyter MCP Server

    Datalayer

    state.local.label (state.local.title)

    Read, edit and execute cells in live Jupyter notebooks from your AI assistant.

    mcp.tc/i/jupyter

  • Nx

    Nx (Nrwl)

    state.local.label (state.local.title)

    Give your AI assistant Nx workspace context: project graph, project details, generators and up-to-date Nx docs.

    mcp.tc/i/nx

listing.disclaimer_checked