winrm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WINRM_MCP_SSL | No | Enable SSL (true/false) to use HTTPS (port 5986) instead of HTTP. | |
| WINRM_MCP_AUTH | No | Authentication mechanism (e.g., ntlm). | |
| WINRM_MCP_HOST | No | The Windows host to connect to. | |
| WINRM_MCP_PATH | No | Custom WinRM path. | |
| WINRM_MCP_PORT | No | The WinRM port (default 5985 for HTTP, 5986 for HTTPS). | |
| WINRM_MCP_PASSWORD | No | The password to authenticate with. Prefer WINRM_MCP_PASSWORD_ENV for security. | |
| WINRM_MCP_USERNAME | No | The username to authenticate with. | |
| WINRM_MCP_TRANSPORT | No | Transport type (e.g., stdio). | |
| WINRM_MCP_ENCRYPTION | No | WinRM encryption setting. | |
| WINRM_MCP_PROJECT_DIR | No | Project directory used for project-scoped inventory. | |
| WINRM_MCP_SERVER_HOST | No | Server host for non-stdio transports. | |
| WINRM_MCP_SERVER_PORT | No | Server port for non-stdio transports. | |
| WINRM_MCP_PASSWORD_ENV | No | Name of the environment variable containing the password. | |
| WINRM_MCP_READ_TIMEOUT | No | Read timeout in seconds. | |
| WINRM_MCP_INVENTORY_FILE | No | Path to a custom inventory file. Used when no explicit scope is provided. | |
| WINRM_MCP_CERT_VALIDATION | No | Enable certificate validation (true/false). Set to false for self-signed certificates. | |
| WINRM_MCP_CONNECT_TIMEOUT | No | Connection timeout in seconds. | |
| WINRM_MCP_INVENTORY_SCOPE | No | Inventory scope: 'user' (default) or 'project'. | user |
| WINRM_MCP_OPERATION_TIMEOUT | No | Operation timeout in seconds. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Execute PowerShell or CMD commands on Windows hosts over WinRM. Use a saved host from a project/user inventory, pass an ad-hoc connection object, or configure WINRM_MCP_* environment defaults. Commands run with the remote account's full rights; confirm destructive actions with the user first. Use output_format='json' for structured PowerShell results and winrm_execute_many for several saved hosts. Call winrm_policy to see which hosts, secrets and file transfers the operator allows.
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 |
|---|---|
| winrm_policyA | Show the server version and the operator's security policy: allowed hosts, whether ad-hoc connections are allowed, which environment variables password_env may read, and whether file transfer is enabled. |
| winrm_inventory_statusB | Show the project or user inventory path, existence, and saved host count. |
| winrm_inventory_initB | Create an empty project or user inventory without replacing existing data by default. |
| winrm_inventory_validateB | Validate an inventory file and every saved WinRM host. |
| winrm_host_listB | List saved WinRM hosts with passwords redacted; optionally only hosts carrying a tag. |
| winrm_host_getB | Get one saved WinRM host with its password redacted. |
| winrm_host_saveB | Save a WinRM host in the project or user inventory. Prefer password_env over password; tags (a list of strings) group hosts for winrm_execute_many. |
| winrm_host_updateB | Update selected settings on a saved host; remove optional values with remove_fields. |
| winrm_host_deleteC | Delete a saved WinRM host. |
| winrm_testB | Test a WinRM connection with a harmless PowerShell marker command; reports whether the account is a local administrator. |
| winrm_execute_powershellA | Execute PowerShell over WinRM and return stdout, stderr (error/warning/verbose streams) and the exit code, including |
| winrm_execute_cmdA | Execute a CMD command over WinRM and return stdout, stderr, and exit code. env sets real process environment variables (usable as %NAME%). On timeout the remote process is terminated. |
| winrm_execute_manyB | Run one command on several saved hosts (listed by name and/or selected by tag) in parallel. Returns one result or error per host, so one unreachable host does not hide the others. |
| winrm_uploadA | Copy a local file to the Windows host. local_path is relative to WINRM_MCP_LOCAL_ROOT (file transfer is disabled unless the operator sets it); remote_path is a full Windows path. |
| winrm_downloadA | Copy a file from the Windows host to WINRM_MCP_LOCAL_ROOT/local_path (file transfer is disabled unless the operator sets it). Existing local files are kept unless overwrite=true. |
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 15 tools
Each tool has a clearly distinct resource and action: inventory management, host CRUD, connection testing, policy inspection, command execution, and file transfer are all separated. The only mild similarity is between winrm_test and winrm_inventory_validate, but their descriptions make the distinction clear: one tests a single connection, the other validates inventory and saved hosts.
All tools use a consistent winrm_ prefix and snake_case, mostly following a resource_action pattern such as winrm_host_list or winrm_inventory_validate. A few names like winrm_test and winrm_policy are less structurally explicit, but they remain predictable and readable.
Fifteen tools is well within a reasonable range for a WinRM management server and each tool appears to earn its place. Inventory, host lifecycle, execution, testing, policy, and transfer operations are all meaningfully separated without obvious filler.
The surface covers host CRUD, inventory initialization/status/validation, connection testing, policy inspection, PowerShell/CMD execution, multi-host execution, and file upload/download. Minor gaps remain, such as no explicit inventory deletion or richer inventory editing, but core workflows are well supported.