kd-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KD_MCP_CONFIG | No | Path to the kd-mcp configuration YAML file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Verify kd-mcp config and kd.exe path. |
| start_kdB | Start kd.exe for KDNET using explicit port/key values. |
| start_from_stateC | Start kd.exe using the shared state file written by winrm-mcp configure_kdnet. |
| kd_commandB | Send a command to a running kd.exe session and collect output. |
| break_inA | Send a break signal to kd.exe. On Windows this uses CTRL_BREAK_EVENT when possible. |
| continue_goC | Send the KD 'g' command to continue target execution. |
| read_outputC | Return buffered kd.exe output for a session. |
| stop_kdB | Stop kd.exe. By default only the debugger process is stopped, not the target. |
| list_sessionsA | List active KD sessions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes. The two start tools (start_from_state and start_kd) could be confused but are differentiated by their descriptions (state file vs explicit params). All others are clearly distinct.
Naming convention is mixed: some verb_noun (list_sessions, read_output, start_kd, stop_kd), others follow different patterns (break_in, continue_go, health_check, kd_command). This inconsistency may confuse an agent expecting a uniform pattern.
9 tools is a reasonable count for a KD session manager. It covers starting, stopping, sending commands, reading output, and session listing without being excessive or too sparse.
The tool set covers the core lifecycle of KD sessions: start, stop, interact (break, continue, command), and monitor (list, read, health). Missing advanced debugging features, but those are beyond the server's stated scope.