win-cli-mcp-tmyy
Related Servers
Alternatives to win-cli-mcp-tmyy
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to seamlessly integrate with the Windows operating system, performing tasks such as file navigation, application control, UI interaction, and QA testing via the MCP protocol.-
- AlicenseAqualityBmaintenanceEnables AI assistants to control Windows PCs by executing shell commands, managing files, capturing screenshots, and monitoring system information through a comprehensive set of MCP tools.181MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to securely control and interact with a local Windows machine through 218 configurable tools for files, Git, processes, Windows UI, browser automation, WSL, Office, recovery, skills, and child MCP servers.5 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to execute PowerShell commands, manage files, inspect projects, run Git operations, and monitor system information on Windows through a local MCP server.-
- AlicenseNot gradedqualityDmaintenanceEnables AI clients to automate Windows desktop applications through window manipulation, image recognition, OCR, keyboard/mouse simulation, and memory operations via the MCP protocol.MIT
TDQS
Scored across 24 tools
Most tools have clearly distinct purposes (file ops, system info, language checks). The only notable overlap is between cmd_exec and powershell_exec, which both execute arbitrary commands, and write_file/edit_file share the write action but differ in line-range specificity. Descriptions mostly resolve this ambiguity.
The dominant verb_noun pattern (list_drives, read_file, check_python) is used for many tools, but several deviate with noun_verb (cmd_exec, bom_manage) and a few are unclassifiable (deep_thinking, mcp_proxy). The mixed conventions are readable but not fully predictable.
24 tools is on the heavier side, including six language-specific check_* tools and meta tools like deep_thinking and mcp_proxy that are not strictly Windows CLI utilities. While each tool has a distinct function, the set could be consolidated without losing much capability.
The server covers core file operations, command execution via CMD and PowerShell, system info, environment variables, and basic language checks. Missing process management, registry, or network tools are workaroundable through cmd_exec/powershell_exec, so there are no major dead ends.