Windows CLI MCP Server
Related Servers
Alternatives to Windows CLI MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables secure command-line interactions on Windows systems with support for PowerShell, CMD, Git Bash, and WSL shells, providing controlled file access, command execution, and configurable security restrictions.614 npm4MIT
- AlicenseAqualityCmaintenanceEnables remote server administration via SSH, supporting command execution, SFTP file transfers, and multi-profile management. It features security safeguards like destructive command detection and audit logging to ensure safe interaction with remote Linux/Unix environments.176 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides secure execution of terminal commands (PowerShell, CMD, shell) with configurable security policies including command blocking, path restrictions, and timeout.1-
- AlicenseAqualityCmaintenanceEnables SSH remote command execution, passwordless key management, Windows Session 0 desktop process launching, and SFTP file transfers across Windows, Linux, and macOS.81 npmMIT
- FlicenseBqualityDmaintenanceEnables secure SSH command execution on remote servers and local PowerShell automation through Claude Desktop. Features enterprise-grade security with SSH key authentication, network scanning, and comprehensive logging for Windows and Linux system administration.4-
- AlicenseBqualityFmaintenanceA Model Context Protocol server that provides secure command-line access to Windows systems, allowing MCP clients like Claude Desktop to safely execute commands in PowerShell, CMD, and Git Bash shells with configurable security controls.9809 npm269MIT
TDQS
Scored across 34 tools
Each tool targets a distinct function within clear categories (Diagnostics, Command Execution, SSH Operations, System Info). Descriptions are detailed and differentiate overlapping potentials (e.g., list_environment_variables vs. read_environment_variable, test_connection vs. test_connectivity).
Tool names predominantly follow a consistent verb_noun pattern with underscores (e.g., create_ssh_connection, get_cpu_usage). Minor inconsistencies exist, such as ssh_disconnect instead of disconnect_ssh_connection, and mix of prefixes like 'list_' vs 'read_' for similar actions.
34 tools is excessive for a single MCP server, indicating potential overloading. While the tools cover distinct sub-domains, the count exceeds the recommended 3-15 range, and many diagnostic tools could be collapsed into fewer, more generic tools.
Core workflows for command execution and SSH operations are covered, including CRUD for connections and SFTP. However, notable gaps exist: no process management (kill), no configuration writing, no memory or network diagnostics, limiting the server's ability to perform full lifecycle management.