Super Windows CLI MCP Server
by MCP-Mirror
An enhanced fork of the Windows CLI MCP Server providing unrestricted system access to Windows environments via a command-line interface (MCP). It allows complete access to Windows shell environments with SYSTEM-level privileges.
Last updated: N/A
What is Super Windows CLI MCP Server?
Super Windows CLI MCP Server is a tool that provides unrestricted system access to Windows environments via a command-line interface. It's designed to run with SYSTEM-level privileges, granting complete control over the operating system.
How to use Super Windows CLI MCP Server?
The server is installed as a Windows service using NSSM. After cloning the repository and installing dependencies, you need to configure the config.json file, paying close attention to security settings like allowedPaths and blockedCommands. Then, run the install-service.ps1 script to install the service. The server can also be run manually for debugging purposes.
Key features of Super Windows CLI MCP Server
Complete access to Windows shell environments (PowerShell, CMD, Git Bash)
Unrestricted command execution (configurable)
Full file system access (configurable)
SYSTEM-level service installation via NSSM
Automatic service recovery features provided by NSSM
Network binding controls
Disabled PowerShell telemetry
Process reuse for performance
Extended timeouts for long-running operations
Use cases of Super Windows CLI MCP Server
Remote system administration
Automated task execution
Script deployment
Configuration management
FAQ from Super Windows CLI MCP Server
What are the security implications of using this server?
What are the security implications of using this server?
This server runs with SYSTEM-level privileges, granting it complete access to the operating system. It should only be used in highly trusted environments with strict network security measures in place.
How do I configure the server?
How do I configure the server?
The server is configured via the config.json file. You should carefully review and modify the settings, especially security.allowedPaths and security.blockedCommands, to restrict access and prevent misuse.
What is NSSM and why is it required?
What is NSSM and why is it required?
NSSM (Non-Sucking Service Manager) is used to install the server as a persistent Windows service that runs with SYSTEM privileges and starts automatically. It also provides automatic service recovery features.
How do I manage the service after installation?
How do I manage the service after installation?
You can manage the service using standard Windows tools or NSSM commands from an administrative PowerShell/CMD in the project directory (start, stop, restart, status, edit configuration).
Can I run the server without installing it as a service?
Can I run the server without installing it as a service?
Yes, you can run the server directly for testing or debugging purposes by using the command npm run start in the project root.