winadm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_windows_servicesA | List Windows services with status and start type. Optionally filter by status (Running/Stopped/etc.) or substring of the service name. |
| service_action_toolA | Start, stop or restart a Windows service. Requires --allow-write. |
| list_windows_processesA | List processes with PID, working set (MB) and CPU seconds. |
| kill_process_toolA | Force-kill a process by PID. Requires --allow-write. |
| read_eventlogB | Read recent events from a Windows event log (default: System, levels error/warning/critical, newest first). |
| windows_system_infoB | OS name/version, hostname, last boot time and memory totals. |
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 6 tools
Each tool targets a distinct resource and action: list vs. act on services, list vs. kill processes, read event logs, and fetch system info. There is no meaningful overlap between any pair, and the write tools are explicitly separated from their read counterparts.
The set mixes several conventions: list_windows_services and list_windows_processes use a clear list_windows_ prefix, while service_action_tool and kill_process_tool use a vague _tool suffix, and read_eventlog/windows_system_info follow yet other patterns. Names are readable but not predictable as a family.
Six tools is well-scoped for a Windows administration server focused on services, processes, event logs, and system info. Each tool clearly earns its place without redundancy.
The surface covers the essential read and write operations for services, processes, event logs, and system info. Minor gaps remain, such as service configuration/creation, process start, or event log clearing, but core admin workflows are supported.