Reported issues for MCP Server for WinDbg Crash Analysis

Pod holds 14 of 14 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to MCP Server for WinDbg Crash Analysis.

Most discussed

Did you mean: 'MCPError'?

C:\Users\Administrator>mcp-windbg Traceback (most recent call last): File "", line 198, in run_module_as_main File "", line 88, in run_code File "C:\Users\Administrator\AppData\Local\Programs\Python\Python313\Scripts\mcp-windbg.exe_main.py", line 2, in from mcp_windbg import main File "C:\Users\Administrator\AppData\Local\Programs\Python\Python313\Lib\site-packages\mcp_windbg_init.py", line 1, in from .server import serve, s

Read the thread · 2026-08-18 · closed · external user · 4 comments

[BUG FIX] Commands sent after g silently re-halt the target via timeout + CTRL+BREAK

Environment

• mcp-windbg 1.0.0 (with g fire-and-forget fix from ISSUE_go_command.md applied)
• Windows 10 21H2 (build 19044) host, Windows 10 2004 (build 19041) VM target
• kd.exe from WDK 10
• Connection: com:pipe,port=\\.\pipe\com_1,baud=115200,reconnect,resets=0

Reproduction

1. open_kd_session with a pipe connection
2. run_kd_command with command g — target resumes correctly
3. run_kd_command with command vertarget (or any non-go command)
4. Observe: timeout error, tar

Read the thread · 2026-08-09 · closed · outside contributor · 2 comments

[BUG FIX] g (go) command re-halts the target immediately via timeout + CTRL+BREAK

@svnscha Found another bug after fixing piped Com requests.

Impact

Any workflow that needs the target running after a KD command (running a PoC, letting the OS boot past initial breakpoint, resuming after inspecting state) is broken. The target is always re-halted by the timeout handler.

Environment

• mcp-windbg 1.0.0
• Windows 10 21H2 (build 19044) host, Windows 10 2004 (build 19041) VM target
• kd.exe from WDK 10
• Connection: `com:pipe,port=\.\pipe\com_1,baud=115200,reconnect,rese

Read the thread · 2026-08-09 · closed · outside contributor · 2 comments

[BUG FIX] Named pipe (COM) kernel connections always time out

Hi Again, @svnscha!

Tested Environment

• mcp-windbg 1.0.0
• Windows 10 21H2 (build 19044) host, Windows 10 2004 (build 19041) VM target
• kd.exe from WDK 10 (C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\kd.exe)
• Connection: com:pipe,port=\\.\pipe\com_1,baud=115200,reconnect,resets=0

Reproduction

1. Set up a VM with kernel debugging over a named pipe (bcdedit /debug on, bcdedit /dbgsettings serial debugport:1 baudrate:115200)
2. Configure the VM to expose `\.\pipe\com

Read the thread · 2026-08-09 · closed · outside contributor · 3 comments

configuration for claude code

hey what's the config for using claude code ( on https ) , i am using this but not working :<

	"mcp-windbg": {
		"command": "uvx",
		"args": [
			"--from",
			"git+https://github.com/svnscha/mcp-windbg",
			"mcp-windbg"
		],
		"env": {
			"_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols;C:\\MyProject\\Symbols"
		}
	}

claude detects it but coudnt connect to it

Read the thread · 2026-03-22 · closed · external user · 2 comments

safeguard check for output returned from mcp-windbg

Is it possible to add some safeguard checks e.g. mask off anything are the personal identifiable information e.g. username, password, etc., prior to returning back to the MCP client? This will help with addressing privacy compliance related issues.

Read the thread · 2025-12-15 · closed · external user · 2 comments

Feature: Remote Debugging Server Alternative

HI @svnscha ,

In an enterprise secured environment where dumps can only be remotely examined, and it's not allowed to connect to my remote windows debugger ( .server tcp:port=5005 just returns access denied). In this case, I wonder if there is another alternative for mcp-windbg to connect with my remote debugger? Thanks.

Read the thread · 2025-09-10 · closed · external user · 8 comments

Setup with Continue in VS Code

@svnscha I'd like to use this MCP server with other LLMs, and I have tried setting an MCP block for use with Continue:

mcpServers:
  - name: mcp_server_windbg

    type: stdio
    version: 0.0.1
    schema: v1
    command: cmd
    args:
      - /c
      - C:\Development\mcp-windbg\.venv\Scripts\python.exe
      - -m
      - mcp_server_windbg
    env:
      _NT_SYMBOL_PATH: "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"
  - name: mcp_server_windbg2
    command: cmd
    arg

[Read the thread](https://github.com/svnscha/mcp-windbg/issues/2) · 2025-05-07 · closed · external user · 8 comments

## Most recent

### 1,2,3 issues 1) MCP server incorrectly uses -remote instead of kernel debugging -k

The MCP WinDbg server incorrectly launches `cdb.exe` using the `-remote` flag, which is intended for user-mode debugging server connections, instead of supporting kernel debugging sessions.

### Current behavior

In `cdb_session.py`:

```python
cmd_args.extend(["-remote", self.remote_connection])

This results in:

cdb.exe -remote net:port=50000,key=...

Expected behavior

For KDNET kernel debugging, CDB/WinDbg should be launched using:

cdb.exe -k net:port=50000,key=

[Read the thread](https://github.com/svnscha/mcp-windbg/issues/62) · 2026-07-02 · closed · external user · 0 comments

### [BUG] Piped requests will always fail

Dear svnscha, 
I have to appreciate what you're trying to accomplish here, as it's really helped me with various tasks! Thank you so much for this plugin, as copy and pasting is quite annoying at times. So, this really comes in handy with debugging and saving time!

I can confirm
- Http: Works
- Localnet: Works
- Pipes: Do not work yet.

Why do pipes not work yet? Let's first understand why the `pipe issue` happens. 
Upon debugging and logging, I have stumbled upon why this fails.
# The Pipe Iss

[Read the thread](https://github.com/svnscha/mcp-windbg/issues/47) · 2026-06-01 · closed · outside contributor · 1 comment

### 1 validation error for JSONRPCMessage

C:\Users\Administrator>mcp-windbg

Received exception from stream: 1 validation error for JSONRPCMessage
  Invalid JSON: EOF while parsing a value at line 2 column 0 [type=json_invalid, input_value='\n', input_type=str]
    For further information visit https://errors.pydantic.dev/2.12/v/json_invalid

  + Exception Group Traceback (most recent call last):
  |   File "<frozen runpy>", line 198, in _run_module_as_main
  |   File "<frozen runpy>", line 88, in _run_code
  |   File "C:\Users\Administ

[Read the thread](https://github.com/svnscha/mcp-windbg/issues/45) · 2026-04-02 · closed · external user · 0 comments

### Critical Remote Code Execution via Unvalidated Command Execution in MCP-WINDBG

## Executive Summary

- **Vulnerability Type:** Command Injection / Remote Code Execution (RCE)
- **Affected Component:** `MCP-WINDBG/src/mcp_windbg/cdb_session.py` (interaction with `server.py` tool handlers)
- **Overview:** The MCP client converts user input (including potentially attacker-controlled prompts) into JSON-RPC and sends it to the MCP-WINDBG service. The service’s tool handler (`run_windbg_cmd`) forwards the `command` parameter from the JSON-RPC directly to `session.send_command()`

[Read the thread](https://github.com/svnscha/mcp-windbg/issues/38) · 2025-12-17 · closed · external user · 1 comment

### other plan

Hello everyone, do you have any plans to create a project for analyzing crashes on the Mac side?

[Read the thread](https://github.com/svnscha/mcp-windbg/issues/23) · 2025-11-12 · closed · external user · 1 comment

### PII and Sensitive information exposure

I understand there may be some risk associated with a public LLM seeing sensitive or PII information in a system or other application dump file. 

Has there been any consideration for integration with a tool such as https://github.com/codelion/optillm to remove this potentially sensitive information before it's sent to a public LLM?

The tool I linked above specifically contains a privacy filter to proxy the LLM traffic and "Anonymize PII data in request and deanonymize it back to original value

[Read the thread](https://github.com/svnscha/mcp-windbg/issues/8) · 2025-06-24 · closed · external user · 1 comment

The remaining reports are on [the project's issue tracker](https://github.com/svnscha/mcp-windbg/issues).