winrm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WINRM_PASSWORD | Yes | Password for the guest administrator account | |
| WINRM_MCP_CONFIG | Yes | Path to the 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 config loading and WinRM connectivity by running a harmless command on the guest. |
| run_psC | Run a PowerShell script on the guest through WinRM. |
| run_cmdC | Run a cmd.exe command on the guest through WinRM. |
| open_shellA | Create a logical shell session. It preserves cwd and environment between session_run calls. |
| session_runA | Run a command in a logical shell session preserving cwd. shell must be powershell or cmd. |
| close_shellC | Close a logical shell session. |
| copy_to_guestB | Copy a file from the host running this MCP server to the Windows guest. |
| copy_from_guestC | Copy a file from the Windows guest to the host running this MCP server. |
| start_processC | Start a process on the guest. Use wait=true to wait for exit code. |
| rebootC | Reboot the guest VM via WinRM. |
| query_debug_settingsA | Return bcdedit debug settings from the guest. |
| configure_kdnetC | Configure guest boot settings for KDNET kernel debugging and optionally write a shared state file for kd-mcp. |
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 12 tools
Each tool has a clearly distinct purpose: shell session management, file transfer, debugging, reboot, process execution, health check, and command execution. No overlap between tools; an agent can easily differentiate.
All tool names follow a consistent verb_noun or verb_preposition_noun pattern, all lowercase with underscores. Examples: close_shell, copy_from_guest, run_ps. No mixing of styles.
With 12 tools covering shell sessions, file transfer, debugging, reboot, process execution, command execution, and health check, the count is well-scoped for a WinRM remote management server. Each tool earns its place.
The tool surface covers core WinRM operations: shell management, file transfer, debugging, reboot, process execution, and health check. Minor gaps exist (e.g., no tool to list running processes or manage services), but the set is complete for its primary use case.