Skip to main content
Glama
mhprol

win-cli-mcp-server

by mhprol

Related Servers

Alternatives to win-cli-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      F
      maintenance
      A 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.
      9
      750 npm
      269
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables remote SSH command execution and bidirectional file transfers through a standardized interface. It allows AI assistants to securely manage remote servers while keeping credentials isolated and applying command-level security controls.
      ISC
    • A
      license
      B
      quality
      A
      maintenance
      A secure MCP server for shell operations, terminal management, and process control, enabling AI assistants to safely execute commands and manage interactive sessions.
      13
      161 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A secure, context-aware MCP server for shell command execution with comprehensive logging and AI optimizations, enabling interactive sessions and safe system administration via Claude Desktop.
      9 npm
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      An MCP server that enables secure execution of shell commands across Windows, macOS, and Linux with built-in whitelisting and approval mechanisms for enhanced security.
      9
      73 npm
      21
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A hardened MCP desktop control server for secure process execution with strict session, buffer, and path limits. It enables reliable desktop automation via any MCP client and emits outcome events for integration with automation flywheels.
      -

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: local execution, history retrieval, remote execution, and remote disconnection. There is no overlap or ambiguity between the four tools.

    Naming Consistency4/5

    Names are mostly predictable: local tools use simple verb_noun (execute_command, get_command_history), while SSH tools consistently use the ssh_ prefix (ssh_execute, ssh_disconnect). The slight inconsistency is that ssh_execute uses 'execute' while the local counterpart is 'execute_command' with an extra noun.

    Tool Count5/5

    Four tools is well-scoped for a Windows CLI MCP server. Each tool serves a core function without unnecessary bloat.

    Completeness4/5

    The local command execution and history retrieval cover the primary workflow. SSH execute and disconnect provide a basic remote capability, though there is no explicit ssh_connect (likely implied by ssh_execute) and no way to manage connections beyond disconnecting.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues