Windows CLI MCP Server
by MCP-Mirror / SimonB97
MCP server for secure command-line interactions on Windows systems, enabling controlled access to PowerShell, CMD, Git Bash shells, and remote systems via SSH. It allows MCP clients to perform operations on your system, similar to Open Interpreter.
Last updated: N/A
What is Windows CLI MCP Server?
A secure MCP server for Windows that allows controlled command-line interactions via PowerShell, CMD, Git Bash, and SSH. It enables MCP clients to execute commands on the system while enforcing security policies.
How to use Windows CLI MCP Server?
Configure the server using a JSON configuration file to define security rules, shell settings, and SSH connection profiles. Integrate it with MCP clients like Claude Desktop by adding the server configuration to the client's configuration file. Use the provided API tools to execute commands, retrieve command history, and manage SSH connections.
Key features of Windows CLI MCP Server
Multi-Shell Support (PowerShell, CMD, Git Bash)
SSH Support for remote command execution
Configurable security controls (command blocking, directory validation, command length limits)
Command logging and history tracking
Smart argument validation
Use cases of Windows CLI MCP Server
Securely automate tasks on Windows systems
Enable AI assistants to interact with the system's command line
Remotely manage Windows servers via SSH
Provide a controlled environment for executing commands from untrusted sources
FAQ from Windows CLI MCP Server
What is the default configuration?
What is the default configuration?
The default configuration is designed to be restrictive and secure, with limited allowed paths and a list of blocked commands.
How do I configure SSH connections?
How do I configure SSH connections?
You can define SSH connection profiles in the ssh.connections section of the configuration file, specifying host, port, username, and authentication method (password or private key).
What security measures are in place?
What security measures are in place?
The server provides command blocking, working directory validation, command length limits, command logging, argument validation, and command injection protection.
How do I integrate this with Claude Desktop?
How do I integrate this with Claude Desktop?
Add the server configuration to your claude_desktop_config.json file, specifying the command and arguments to start the server.
Where does the server look for the configuration file?
Where does the server look for the configuration file?
The server looks for the configuration file in the following order: Path specified by --config flag, ./config.json in current directory, ~/.win-cli-mcp/config.json in user's home directory.