Skip to main content
Glama
Super Windows CLI MCP Server

Super Windows CLI MCP Server

by delorenj

Super Windows CLI MCP Server

An enhanced fork of the Windows CLI MCP Server with unrestricted system access capabilities.

Enhancements

  • Full system access through SYSTEM service installation

  • Unrestricted command execution

  • Network-level access controls

  • Unlimited process capabilities

  • Auto-recovery and fault tolerance

  • PowerShell telemetry disabled

Related MCP server: Super Windows CLI MCP Server

Security Notice

This version removes application-level restrictions in favor of network-level security. It is designed for use in trusted environments where full system access is required.

Features

  • Complete access to Windows shell environments (PowerShell, CMD, Git Bash)

  • No command or argument restrictions

  • Full file system access

  • SYSTEM-level service installation

  • Automatic service recovery

  • Network binding controls

  • Process reuse for performance

  • Extended timeouts for long-running operations

Installation

  1. Build the project:

npm install
npm run build
  1. Copy the built files to your Windows machine

  2. Run the installation script as administrator:

.\install-service.ps1

Configuration

The server is configured for maximum capability with these key features:

  • No command restrictions

  • Full filesystem access

  • Disabled injection protection

  • Unlimited process resources

  • Network-level access control

  • SYSTEM-level privileges

See config.json for the complete configuration.

Service Management

Installation

.\install-service.ps1

Removal

.\uninstall-service.ps1

Network Security

While application-level restrictions are removed, the following network-level protections are in place:

  • Localhost binding by default

  • Configurable allowed IP ranges

  • Local network restriction

  • Optional VPN integration

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

Based on the original win-cli-mcp-server by SimonB97.

Available Tools

4 tools
execute_commandB

Execute a command in the specified shell (powershell, cmd, or gitbash)

Example usage (PowerShell):

{
  "shell": "powershell",
  "command": "Get-Process | Select-Object -First 5",
  "workingDir": "C:\Users\username"
}

Example usage (CMD):

{
  "shell": "cmd",
  "command": "dir /b",
  "workingDir": "C:\Projects"
}

Example usage (Git Bash):

{
  "shell": "gitbash",
  "command": "ls -la",
  "workingDir": "/c/Users/username"
}

Inputs: shell (required), command (required), workingDir.

get_command_historyA

Get the history of executed commands

Example usage:

{
  "limit": 5
}

Example response:

[
  {
    "command": "Get-Process",
    "output": "...",
    "timestamp": "2024-03-20T10:30:00Z",
    "exitCode": 0
  }
]

Inputs: limit.

ssh_disconnectA

Disconnect from an SSH server

Example usage:

{
  "connectionId": "raspberry-pi"
}

Use this to cleanly close SSH connections when they're no longer needed.

Inputs: connectionId (required).

ssh_executeA

Execute a command on a remote host via SSH

Example usage:

{
  "connectionId": "raspberry-pi",
  "command": "uname -a"
}

Configuration required in config.json:

{
  "ssh": {
    "enabled": true,
    "connections": {
      "raspberry-pi": {
        "host": "raspberrypi.local",
        "port": 22,
        "username": "pi",
        "password": "raspberry"
      }
    }
  }
}

Inputs: connectionId (required), command (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 4 tools

    Disambiguation3/5

    The tools have some overlap in purpose that could cause confusion. execute_command and ssh_execute both execute commands but in different contexts (local vs remote), which might lead to misselection if the agent doesn't carefully distinguish between local and remote execution. However, get_command_history and ssh_disconnect are clearly distinct from the execution tools.

    Naming Consistency4/5

    The naming follows a mostly consistent verb_noun pattern with clear actions like execute, get, and disconnect. All tools use snake_case consistently. The minor deviation is that ssh_disconnect uses 'disconnect' while others use more specific verbs, but overall it's readable and predictable.

    Tool Count3/5

    With only 4 tools, the count feels borderline thin for a 'Super Windows CLI MCP Server' that implies broader command-line capabilities. It covers basic execution and SSH operations but lacks tools for file management, process control, or other common CLI tasks, making the scope seem underdeveloped.

    Completeness2/5

    There are significant gaps in the tool surface for a Windows CLI server. It includes command execution and SSH operations but misses core functionalities like file operations (e.g., copy, move, delete), process management (e.g., start, stop), system information retrieval, or network utilities. The SSH tools are incomplete without a corresponding ssh_connect tool to establish connections.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An enhanced MCP server that grants AI assistants the ability to execute terminal commands on a user's system with improved security controls, designed for use in controlled environments.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables remote filesystem and CLI access to a Windows machine over LAN through MCP, with file read/write and command execution capabilities.
      MIT