Skip to main content
Glama
Faucet94

Super Windows CLI MCP Server

by Faucet94
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Super Windows CLI MCP Server

No user-submitted related servers found.

    Related Servers

    • Windows CLI MCP Server

      s2005
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      6
      37 npm
      4
      MIT

    • Windows CLI MCP Server

      simon-ami
      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

    • Windows CLI MCP Server

      quanticsoul4772
      A
      license
      B
      quality
      D
      maintenance
      Enables secure command-line interactions on Windows systems through PowerShell, CMD, and Git Bash, with support for SSH remote connections, SFTP file transfers, system monitoring, and configurable security controls including command blocking and path restrictions.
      34
      2
      MIT

    • winrdp-mcp

      emog33k
      A
      license
      Not graded
      quality
      A
      maintenance
      A zero-config MCP server that provisions and fully administers Windows RDP boxes (Windows 10/11 and Server 2016–2025), exposing 144 tools for shell, files, registry, GUI automation, UAC elevation, health reports, and more, plus guided workflows.
      144 PyPI
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 4 tools

    Disambiguation3/5

    The tools have some overlap in purpose that could cause confusion. Both execute_command and ssh_execute run commands, differing only in local vs. remote execution, which might lead to misselection if the agent doesn't carefully note the distinction. However, get_command_history and ssh_disconnect are clearly distinct, and the descriptions help clarify the differences.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern throughout (e.g., execute_command, get_command_history, ssh_disconnect, ssh_execute), which is predictable and readable. There are minor deviations, such as the use of 'disconnect' versus 'execute' in the SSH tools, but overall, the pattern is maintained.

    Tool Count3/5

    With 4 tools, the count is borderline for the server's purpose as a 'Super Windows CLI MCP Server'. It feels thin, lacking coverage for common CLI operations like file management, process control, or network utilities, which might be expected in such a domain. However, it's not severely under-scoped.

    Completeness2/5

    There are significant gaps in the tool surface for a Windows CLI server. It lacks basic operations like listing files, managing processes, or handling network configurations, and the SSH tools seem like an add-on rather than core functionality. This incompleteness will likely cause agent failures when trying to perform common CLI tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources