winadm-mcp
Related Servers
Alternatives to winadm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to run PowerShell commands and manage Windows services without intrusive console windows, while also supporting remote execution via SSH and WinRM.20304 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to safely perform file operations, run terminal sessions, manage processes, search content, and inspect Git repositories on a local Windows machine under configurable permission and audit controls.Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to administer a local Windows machine by listing and controlling services, processes, event logs, ports, network lookups and system diagnostics through sharply typed tools. A built-in web interface lets the operator switch every tool on or off individually, with least privilege as the default.2MIT
- AlicenseBqualityAmaintenanceEnables AI agents to securely manage and execute commands on remote Windows servers via WinRM, including PowerShell execution, system information retrieval, and service management.618 PyPI6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to perform extensive Windows system administration, file operations, process management, network configuration, registry editing, GUI automation, and more through a comprehensive set of MCP tools.1MIT
- AlicenseBqualityDmaintenanceProvides Windows system diagnostic capabilities to AI agents, allowing them to access event logs, crash information, system uptime, and perform stability analysis.113MIT
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.