MCP Server for WinDbg

https://svnscha.github.io/mcp-windbg/
Admin
MCP Server for WinDbg is a Model Context Protocol (MCP) server that allows AI assistants to analyze...
Tokens:9,865
Snippets:152
Trust Score:9.7
Update:2 months ago
Show doc for...
Tokens:
Raw
### Development setup from source

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Clone and install the server from source for development.

```bash
git clone https://github.com/svnscha/mcp-windbg.git
cd mcp-windbg
python -m venv .venv
.\.venv\Scripts\activate
pip install -e .
```

--------------------------------

### Configure transport protocols

Source: https://svnscha.github.io/mcp-windbg/reference/cli

Examples for starting the server using either standard I/O or HTTP transport.

```bash
mcp-windbg
# equivalently
mcp-windbg --transport stdio
```

```bash
mcp-windbg --transport streamable-http --host 127.0.0.1 --port 8000
```

--------------------------------

### Verify server installation

Source: https://svnscha.github.io/mcp-windbg/troubleshooting

Run the help command to confirm the server is installed and reachable.

```bash
python -m mcp_windbg --help
```

--------------------------------

### Install mcp-windbg via pip

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Install the server package using pip.

```bash
pip install mcp-windbg
```

--------------------------------

### Perform an editable installation

Source: https://svnscha.github.io/mcp-windbg/development

Clones the repository and installs the package in editable mode to the user site.

```bash
git clone https://github.com/svnscha/mcp-windbg.git
cd mcp-windbg
python -m pip install --user -e .
```

--------------------------------

### Start mcp-windbg HTTP server

Source: https://svnscha.github.io/mcp-windbg/scenarios/http-service

Launch the server on the Windows host using the streamable-http transport.

```bash
mcp-windbg --transport streamable-http --host 127.0.0.1 --port 8000
```

--------------------------------

### Install WinDbg via winget

Source: https://svnscha.github.io/mcp-windbg/getting-started

Installs the Debugging Tools for Windows required for the server to function.

```bash
winget install 9PGJGD53TN86 --accept-source-agreements --accept-package-agreements
```

--------------------------------

### Verify editable installation path

Source: https://svnscha.github.io/mcp-windbg/development

Checks that the installed package points to the local source checkout.

```python
python -c "import mcp_windbg, inspect; print(inspect.getfile(mcp_windbg))"
```

--------------------------------

### Configure .env file

Source: https://svnscha.github.io/mcp-windbg/development

Example content for the .env file used by VS Code to manage kernel connection settings.

```text
MCP_WINDBG_KERNEL_CONNECTION=net:port=50005,key=1.2.3.4
```

--------------------------------

### Start server with filter script

Source: https://svnscha.github.io/mcp-windbg/reference/cli

Command to launch the server while applying a specific Python filter script.

```bash
mcp-windbg --filter-script C:\filters\pii_redaction.py
```

--------------------------------

### HTTP transport configuration

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Start the server with HTTP transport and configure the client to connect to it.

```bash
mcp-windbg --transport streamable-http --host 127.0.0.1 --port 8000
```

```json
{
    "servers": {
        "mcp_windbg_http": {
            "type": "http",
            "url": "http://localhost:8000/mcp"
        }
    }
}
```

--------------------------------

### Analyze crash dump path

Source: https://svnscha.github.io/mcp-windbg/scenarios/http-service

Example of specifying a file path that exists on the remote Windows host.

```text
Analyze the crash dump at C:\dumps\app.dmp
```

--------------------------------

### Retrieve Session ID

Source: https://svnscha.github.io/mcp-windbg/reference/tools

Example of the session ID format returned by open_* tools, which must be used for subsequent session operations.

```text
session_id: cdb-1a2b3c4d
```

--------------------------------

### VS Code custom arguments

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Example of adding custom arguments like a filter script or CDB path to the VS Code configuration.

```json
"args": ["-m", "mcp_windbg",
         "--cdb-path", "C:\\Program Files (x86)\\Windows Kits\\10\\Debuggers\\x64\\cdb.exe"]
```

--------------------------------

### Verify cdb.exe installation

Source: https://svnscha.github.io/mcp-windbg/getting-started

Checks if the debugger executable is accessible in the system path.

```bash
cdb.exe -version
```

--------------------------------

### Implement a redaction filter

Source: https://svnscha.github.io/mcp-windbg/reference/cli

Example of a filter script that replaces sensitive email addresses in tool commands and output.

```python
def process_input(text, context):
    if context["tool_name"] == "run_cdb_command" and context["argument_path"] == "$.command":
        return text.replace("user@example.com", "[redacted-email]")
    return text


def process_output(text, context):
    return text.replace("user@example.com", "[redacted-email]")
```

--------------------------------

### Run with uvx

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Use uvx to fetch and run the server on demand.

```json
{
    "command": "uvx",
    "args": ["--from", "git+https://github.com/svnscha/mcp-windbg", "mcp-windbg"]
}
```

--------------------------------

### Claude Desktop configuration

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Add the server to the claude_desktop_config.json file.

```json
{
    "mcpServers": {
        "mcp-windbg": {
            "command": "python",
            "args": ["-m", "mcp_windbg"],
            "env": {
                "_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"
            }
        }
    }
}
```

--------------------------------

### MCP Tools Overview

Source: https://svnscha.github.io/mcp-windbg/reference/tools

List of available MCP tools for interacting with WinDbg sessions.

```APIDOC
## MCP Tools

| Tool | Purpose |
| --- | --- |
| `list_dumps` | List crash dump files in a directory. |
| `open_cdb_dump` | Open a dump and run the standard triage commands (`cdb.exe`). |
| `open_cdb_remote` | Attach to a user-mode remote debug server (`-remote`). |
| `open_kd_session` | Attach to a kernel debugging target (`-k`, `kd.exe`). |
| `run_cdb_command` | Run a command on a user-mode (cdb) session. |
| `run_kd_command` | Run a command on a kernel (kd) session. |
| `close_cdb_session` | Close a user-mode session. |
| `close_kd_session` | Close a kernel session. |
| `send_ctrl_break` | Break into a running target. |
```

--------------------------------

### Run test suites

Source: https://svnscha.github.io/mcp-windbg/development

Executes different subsets of tests based on hardware availability and requirements.

```bash
uv run pytest src/mcp_windbg/tests/ -v                 # full suite (needs cdb.exe for live cases)
uv run pytest src/mcp_windbg/tests/ -v -m "not live"   # hermetic subset, no debugger needed
uv run pytest src/mcp_windbg/tests/ -v -m kernel       # kernel scenarios, needs a real target
```

--------------------------------

### Register with Autohand Code

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Register the server using the Autohand CLI.

```bash
autohand mcp add mcp-windbg python -m mcp_windbg
```

--------------------------------

### Build a wheel

Source: https://svnscha.github.io/mcp-windbg/development

Generates distributable artifacts in the dist/ directory.

```bash
uv build
```

--------------------------------

### VS Code MCP configuration

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Configure the server in .vscode/mcp.json for GitHub Copilot.

```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"
            }
        }
    }
}
```

--------------------------------

### Configure HTTP MCP client

Source: https://svnscha.github.io/mcp-windbg/scenarios/http-service

Add the HTTP server configuration to your client settings.

```json
{
    "servers": {
        "mcp_windbg_http": {
            "type": "http",
            "url": "http://localhost:8000/mcp"
        }
    }
}
```

--------------------------------

### Enable kernel debugging on target

Source: https://svnscha.github.io/mcp-windbg/scenarios/kernel-debugging

Configure the target machine for KDNET debugging and reboot to apply changes.

```text
bcdedit /debug on
bcdedit /dbgsettings net hostip:w.x.y.z port:50000
```

--------------------------------

### Open a kernel debugging session

Source: https://svnscha.github.io/mcp-windbg/scenarios/kernel-debugging

Initiate a connection to the target machine using the specified transport parameters.

```text
Open a kernel debugging session on net:port=50000,key=1.2.3.4
```

--------------------------------

### Development configuration

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Configuration for using the local virtual environment in VS Code.

```json
{
    "servers": {
        "mcp_windbg": {
            "type": "stdio",
            "command": "${workspaceFolder}/.venv/Scripts/python",
            "args": ["-m", "mcp_windbg"]
        }
    }
}
```

--------------------------------

### Expose mcp-windbg to network

Source: https://svnscha.github.io/mcp-windbg/scenarios/http-service

Bind the server to all interfaces to accept remote connections.

```bash
mcp-windbg --transport streamable-http --host 0.0.0.0 --port 8000
```

--------------------------------

### Analyze and compare dumps

Source: https://svnscha.github.io/mcp-windbg/scenarios/triage

Commands for batch analysis and comparison of crash dumps.

```text
Analyze each dump in C:\dumps and group them by faulting module and exception code
```

```text
For every dump under C:\dumps\incident-42, show the top stack frame and tell me
which ones share the same crash signature
```

--------------------------------

### Run a specific scenario

Source: https://svnscha.github.io/mcp-windbg/development

Executes a single parametrized test scenario by its name.

```bash
uv run pytest "src/mcp_windbg/tests/test_scenarios.py::test_scenario[Kernel session against a real target]" -v
```

--------------------------------

### run_kd_command

Source: https://svnscha.github.io/mcp-windbg/reference/tools

Executes a command on an active kernel (kd) session and returns the output.

```APIDOC
## run_kd_command

### Description
Run any command on an open kernel (kd) session and return its output.

### Parameters
- **session_id** (string) - Required - A kd session id from open_kd_session.
- **command** (string) - Required - The command to run, for example !process 0 0 or vertarget.
- **timeout_seconds** (integer) - Optional - Override the command timeout (default 120s).
```

--------------------------------

### GitHub Copilot CLI configuration

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Configure the server in the Copilot CLI mcp-config.json file.

```json
{
    "mcpServers": {
        "mcp-windbg": {
            "type": "local",
            "command": "python",
            "args": ["-m", "mcp_windbg"],
            "tools": ["*"],
            "env": {
                "_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"
            }
        }
    }
}
```

--------------------------------

### Configure CDB path

Source: https://svnscha.github.io/mcp-windbg/troubleshooting

Specify the absolute path to cdb.exe in the client configuration if auto-detection fails.

```json
"args": ["--from", "git+https://github.com/svnscha/mcp-windbg", "mcp-windbg",
         "--cdb-path", "C:\\Program Files (x86)\\Windows Kits\\10\\Debuggers\\x64\\cdb.exe"]
```

--------------------------------

### Connect to a remote debugging server

Source: https://svnscha.github.io/mcp-windbg/scenarios/remote-debugging

Initiates a connection to a remote debugging server using a specific connection string.

```text
Connect to tcp:Port=5005,Server=192.168.0.100
```

--------------------------------

### Inspect kernel target

Source: https://svnscha.github.io/mcp-windbg/scenarios/kernel-debugging

Execute standard WinDbg kernel commands to analyze the state of the target machine.

```text
Show the current bugcheck analysis with !analyze -v
List the loaded drivers with lm
Show the stack of every processor with !running
```

--------------------------------

### Analyze with custom symbol paths

Source: https://svnscha.github.io/mcp-windbg/scenarios/crash-dump

Specifies an additional directory for symbol resolution during the initial session creation.

```text
Analyze C:\dumps\app.dmp using symbols from C:\build\symbols
```

--------------------------------

### Investigate target state

Source: https://svnscha.github.io/mcp-windbg/scenarios/remote-debugging

Commands for inspecting registers, threads, CPU usage, and synchronization locks.

```text
Show the current registers and call stack
List all threads and point out any that look stuck
Check thread CPU time with !runaway
Look for held locks with !locks
```

--------------------------------

### Configure VS Code for development

Source: https://svnscha.github.io/mcp-windbg/development

Updates the VS Code MCP configuration file to include the development server.

```json
{
    "servers": {
        "mcp_windbg_dev": {
            "type": "stdio",
            "command": "C:\\Python314\\python.exe",
            "args": ["-m", "mcp_windbg", "--verbose"],
            "env": {
                "_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"
            }
        }
    }
}
```

--------------------------------

### Set symbol path

Source: https://svnscha.github.io/mcp-windbg/troubleshooting

Define the symbol server path in the client environment configuration to resolve function names.

```json
"env": {"_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"}
```

--------------------------------

### Claude Code configuration file

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Manual configuration for the .claude.json file.

```json
{
    "mcpServers": {
        "mcp-windbg": {
            "type": "stdio",
            "command": "python",
            "args": ["-m", "mcp_windbg"],
            "env": {
                "_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"
            }
        }
    }
}
```

--------------------------------

### run_cdb_command

Source: https://svnscha.github.io/mcp-windbg/reference/tools

Executes a WinDbg command on an active user-mode (cdb) session and returns the output.

```APIDOC
## run_cdb_command

### Description
Run any WinDbg command on an open user-mode (cdb) session and return its output.

### Parameters
- **session_id** (string) - Required - A cdb session id from open_cdb_dump or open_cdb_remote.
- **command** (string) - Required - The command to run, for example kb or !analyze -v.
- **timeout_seconds** (integer) - Optional - Override the command timeout (default 60s).
```

--------------------------------

### Register mcp-windbg with Claude Code

Source: https://svnscha.github.io/mcp-windbg/reference/clients

Register the server using the Claude CLI with the required symbol path environment variable.

```bash
claude mcp add mcp-windbg -s user -e _NT_SYMBOL_PATH="SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols" -- python -m mcp_windbg
```

--------------------------------

### open_kd_session

Source: https://svnscha.github.io/mcp-windbg/reference/tools

Attaches to a kernel debugging target launched with -k using kd.exe. Waits for the target to connect and breaks in, returning a session_id.

```APIDOC
## open_kd_session

### Description
Attach to a kernel debugging target, launched with -k using kd.exe. Waits for the target to connect, breaks in, and returns a session_id.

### Parameters
- **connection_string** (string) - Required - Kernel connection string (e.g., net:port=50000,key=1.2.3.4).
- **include_stack_trace** (boolean) - Optional - Include the stack trace. Defaults to false.
- **include_modules** (boolean) - Optional - Include loaded module information. Defaults to false.
- **include_threads** (boolean) - Optional - Include thread information. Defaults to false.
- **symbols_path** (string) - Optional - Extra symbol search path.
- **timeout_seconds** (integer) - Optional - Override the connect/break-in timeout (default 60s).
```

--------------------------------

### Run diagnostic checks

Source: https://svnscha.github.io/mcp-windbg/troubleshooting

Verify the availability of the debugger and the server module.

```bash
cdb.exe -version
python -m mcp_windbg --help
```

--------------------------------

### Typical bugcheck investigation workflow

Source: https://svnscha.github.io/mcp-windbg/scenarios/kernel-debugging

A sequence of steps for investigating a system crash using the kernel debugging session.

```text
1. Open a kernel debugging session on net:port=50000,key=1.2.3.4
2. Run !analyze -v and summarize the bugcheck
3. Show the faulting driver and its stack
4. List loaded modules and flag anything unsigned or unexpected
```

--------------------------------

### Add development server to Claude Code

Source: https://svnscha.github.io/mcp-windbg/development

Registers the development build with the Claude CLI using the full path to the Python interpreter.

```bash
claude mcp add mcp-windbg-dev -s user -e _NT_SYMBOL_PATH="SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols" -- C:\Python314\python.exe -m mcp_windbg --verbose
```

--------------------------------

### Execute follow-up analysis commands

Source: https://svnscha.github.io/mcp-windbg/scenarios/crash-dump

Performs additional diagnostic queries within an existing crash dump session.

```text
Show the call stack with kb and explain the access violation
Run .ecxr then u to disassemble around the faulting instruction
Dump the locals for frame 2
Check the heap around 0x1f2a0040 with !heap -p -a 0x1f2a0040
List the loaded modules with lm and flag anything unsigned
```

--------------------------------

### Configure the MCP server with a filter script

Source: https://svnscha.github.io/mcp-windbg/scenarios/redaction

Add the --filter-script argument to the server configuration to enable the redaction script.

```json
"args": ["--from", "git+https://github.com/svnscha/mcp-windbg", "mcp-windbg",
         "--filter-script", "C:\\filters\\redact.py"]
```

--------------------------------

### Configure Windows Error Reporting

Source: https://svnscha.github.io/mcp-windbg/scenarios/triage

Registry configuration for enabling local crash dump collection.

```text
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps
    DumpFolder  (REG_EXPAND_SZ)  e.g. C:\dumps
    DumpType    (REG_DWORD)      2 = full dump, 1 = mini dump
```

--------------------------------

### List crash dumps

Source: https://svnscha.github.io/mcp-windbg/scenarios/triage

Commands to list crash dump files in a specific directory or recursively.

```text
List all crash dumps in C:\dumps
```

```text
Find all crash dumps under C:\dumps including subdirectories
```

--------------------------------

### Enable verbose logging

Source: https://svnscha.github.io/mcp-windbg/troubleshooting

Add the --verbose flag to the server arguments to output diagnostic information to stderr.

```json
"args": ["--from", "git+https://github.com/svnscha/mcp-windbg", "mcp-windbg", "--verbose"]
```

--------------------------------

### Typical hang investigation workflow

Source: https://svnscha.github.io/mcp-windbg/scenarios/remote-debugging

A sequence of steps to diagnose a hung process.

```text
1. Connect to tcp:Port=5005,Server=192.168.0.100
2. Send CTRL+BREAK so we can inspect safely
3. Show current state - registers, stack, threads
4. Run ~*k and identify the thread holding things up
5. Run !locks to check synchronization objects
```

--------------------------------

### Analyze crash dump via Copilot

Source: https://svnscha.github.io/mcp-windbg/getting-started

Commands to initiate and interact with a crash dump analysis session in Copilot Chat.

```text
Analyze the crash dump at C:\dumps\app.dmp
```

```text
Show the call stack with kb and explain the access violation
Run .ecxr then u to disassemble around the fault
Check the heap around 0x1f2a0040 with !heap -p -a 0x1f2a0040
```

```text
Close the crash dump session for C:\dumps\app.dmp
```

--------------------------------

### Configure kernel target

Source: https://svnscha.github.io/mcp-windbg/development

Sets the environment variable for kernel connection strings before running kernel tests.

```powershell
$env:MCP_WINDBG_KERNEL_CONNECTION = "net:port=50005,key=1.2.3.4"
uv run pytest src/mcp_windbg/tests/ -m kernel -v
```

--------------------------------

### open_cdb_dump

Source: https://svnscha.github.io/mcp-windbg/reference/tools

Opens a crash dump file and executes common analysis commands.

```APIDOC
## open_cdb_dump

### Description
Open a crash dump and run the common analysis commands (.lastevent, !analyze -v, and optionally stack, modules, threads). Returns a session_id.

### Parameters
- **dump_path** (string) - Required - Path to the .dmp file.
- **include_stack_trace** (boolean) - Optional - Include the stack trace (kb). Defaults to false.
- **include_modules** (boolean) - Optional - Include loaded module information (lm). Defaults to false.
- **include_threads** (boolean) - Optional - Include thread information (~). Defaults to false.
- **symbols_path** (string) - Optional - Extra symbol search path.
- **timeout_seconds** (integer) - Optional - Override the open/analysis timeout (default 180s).
```

--------------------------------

### List latest crash dumps

Source: https://svnscha.github.io/mcp-windbg/scenarios/triage

Command to retrieve the most recent crash dump files.

```text
List the latest crash dumps
```

--------------------------------

### Session Management

Source: https://svnscha.github.io/mcp-windbg/reference/tools

Details on how to manage debugger sessions using session IDs.

```APIDOC
## Session Management

Every `open_*` tool returns a `session_id` (e.g., `cdb-1a2b3c4d`). This ID must be passed to follow-up calls for `run_*`, `close_*`, and `send_ctrl_break` operations. Sessions are persistent and identified by their prefix (`cdb-` or `kd-`).
```

--------------------------------

### Report coverage for specific modules

Source: https://svnscha.github.io/mcp-windbg/development

Generates a coverage report filtered by specific modules.

```bash
uv run pytest src/mcp_windbg/tests/ -m kernel
uv run coverage combine
uv run coverage report --include="*kd_session*,*debug_session*"
```

--------------------------------

### Implement a Python redaction filter script

Source: https://svnscha.github.io/mcp-windbg/scenarios/redaction

Define a process_output function to scrub email addresses from tool output text using regular expressions.

```python
import re

EMAIL = re.compile(r"[\w.+-]+@[\w-]+\.[\w.-]+")


def process_output(text, context):
    return EMAIL.sub("[redacted-email]", text)
```

--------------------------------

### send_ctrl_break

Source: https://svnscha.github.io/mcp-windbg/reference/tools

Sends a CTRL+BREAK signal to a live session to break into a running target.

```APIDOC
## send_ctrl_break

### Description
Send a CTRL+BREAK to a live session (remote or kernel) to break into a running target.

### Parameters
- **session_id** (string) - Required - A live session id (cdb remote or kd) to break into.
```

--------------------------------

### list_dumps

Source: https://svnscha.github.io/mcp-windbg/reference/tools

Lists crash dump files in a specified directory.

```APIDOC
## list_dumps

### Description
List crash dump files in a directory.

### Parameters
- **directory_path** (string) - Optional - Directory to search. Defaults to the configured local crash dump location.
- **recursive** (boolean) - Optional - Search subdirectories as well. Defaults to false.
```

--------------------------------

### Measure multi-process coverage

Source: https://svnscha.github.io/mcp-windbg/development

Measures coverage for both the pytest process and the server subprocess.

```bash
uv run coverage erase
$env:MCP_WINDBG_COVERAGE = "1"
uv run coverage run -m pytest src/mcp_windbg/tests/     # measures pytest AND the server
$env:MCP_WINDBG_COVERAGE = $null
uv run coverage combine                 # merge the per-process .coverage.* files
uv run coverage report                  # or: uv run coverage html  ->  htmlcov/
```

--------------------------------

### open_cdb_remote

Source: https://svnscha.github.io/mcp-windbg/reference/tools

Attaches to a user-mode remote debug server launched with the -remote flag. Returns a session_id upon successful connection.

```APIDOC
## open_cdb_remote

### Description
Attach to a user-mode remote debug server (a cdb/WinDbg -server), launched with -remote. Returns a session_id.

### Parameters
- **connection_string** (string) - Required - Remote connection string (e.g., tcp:Port=5005,Server=192.168.0.100).
- **include_stack_trace** (boolean) - Optional - Include the stack trace. Defaults to false.
- **include_modules** (boolean) - Optional - Include loaded module information. Defaults to false.
- **include_threads** (boolean) - Optional - Include thread information. Defaults to false.
- **symbols_path** (string) - Optional - Extra symbol search path.
- **timeout_seconds** (integer) - Optional - Override the connect timeout (default 60s).
```

--------------------------------

### Measure scenario-only coverage

Source: https://svnscha.github.io/mcp-windbg/development

Measures coverage specifically for end-to-end scenarios without the pytest wrapper overhead.

```bash
uv run coverage erase
$env:MCP_WINDBG_COVERAGE = "1"
uv run pytest src/mcp_windbg/tests/test_scenarios.py
$env:MCP_WINDBG_COVERAGE = $null
uv run coverage combine
uv run coverage html -d htmlcov-e2e      # browsable, line by line -> htmlcov-e2e/index.html
```

--------------------------------

### Close dump sessions

Source: https://svnscha.github.io/mcp-windbg/scenarios/triage

Command to terminate dump sessions to prevent accumulation of cdb.exe processes.

```text
Close each dump session after you have analyzed it
```

--------------------------------

### close_kd_session

Source: https://svnscha.github.io/mcp-windbg/reference/tools

Closes a kernel session and releases the associated kd.exe process, with an option to resume the target machine.

```APIDOC
## close_kd_session

### Description
Close a kernel session and release its kd.exe process. By default this resumes the target machine (sends g) so it runs again.

### Parameters
- **session_id** (string) - Required - The kd session id to close.
- **resume** (boolean) - Optional - Resume the machine on close. Defaults to true.
```

--------------------------------

### Interrupt and inspect the target

Source: https://svnscha.github.io/mcp-windbg/scenarios/remote-debugging

Sends a break signal to the target and retrieves thread stack information.

```text
Send CTRL+BREAK to interrupt the target, then show all thread stacks with ~*k
```

--------------------------------

### Close the kernel debugging session

Source: https://svnscha.github.io/mcp-windbg/scenarios/kernel-debugging

Terminate the session and resume the target machine execution.

```text
Close the kernel debugging session on net:port=50000,key=1.2.3.4
```

--------------------------------

### Define filter script hooks

Source: https://svnscha.github.io/mcp-windbg/reference/cli

Structure for Python scripts used to intercept and modify tool input and output text.

```python
def process_input(text, context):
    return text


def process_output(text, context):
    return text
```

--------------------------------

### Close the remote session

Source: https://svnscha.github.io/mcp-windbg/scenarios/remote-debugging

Terminates the connection and releases the debugging session.

```text
Close the connection to tcp:Port=5005,Server=192.168.0.100
```

--------------------------------

### close_cdb_session

Source: https://svnscha.github.io/mcp-windbg/reference/tools

Closes a user-mode session and releases the associated cdb.exe process.

```APIDOC
## close_cdb_session

### Description
Close a user-mode session and release its cdb.exe process.

### Parameters
- **session_id** (string) - Required - The cdb session id to close.
```

--------------------------------

### Close a crash dump session

Source: https://svnscha.github.io/mcp-windbg/scenarios/crash-dump

Terminates the active cdb.exe process associated with the specified crash dump.

```text
Close the crash dump session for C:\dumps\app.dmp
```
Tokens:
Raw