Windows-Command-Line

The Windows Command Line MCP Server provides a secure bridge between an AI model and Windows command-line operations. It exposes a controlled set of tools that allow retrieval of system information, management of processes and services, execution of safe Windows commands, and creation of development projects in a sandboxed environment. Tools include execute_command for running approved Windows CLI commands, execute_powershell for PowerShell scripts, create_project for generating React, Node.js, or Python projects in ~/AIProjects, and several information-gathering utilities such as get_system_info, get_network_info, get_scheduled_tasks, get_service_info, and list_running_processes. This design emphasizes strict input validation and an allowlist to minimize risk while enabling practical automation and development workflows. When integrated with Claude for Desktop, configure the server in claude_desktop_config.json and call on the toolbox of commands via natural language prompts to perform safe system operations.

Prerequisites:

• Node.js 16 or later
• npm or yarn
• Windows operating system

Installation steps:

1. Install via Smithery (optional): npx -y @smithery/cli install @alxspiker/Windows-Command-Line-MCP-Server --client claude

2. Manual setup: git clone https://github.com/alxspiker/Windows-Command-Line-MCP-Server.git cd Windows-Command-Line-MCP-Server npm install npm run build

3. Run the server: node dist/index.js

4. Optional configuration for Claude Desktop:

   • Add to claude_desktop_config.json with the appropriate path to your built index.js as shown in the example: { "mcpServers": { "windows-cmd": { "command": "node", "args": ["/path/to/dist/index.js"] } } }

Tips and considerations:

• By default, the server uses a safe command allowlist. Review and customize allowed commands as needed for your environment.
• For extended capabilities, you can enable --allow-all mode, but use with caution due to increased risk.
• Ensure the sandboxed development projects are stored in ~/AIProjects and that access permissions are correctly configured.
• If you integrate with Claude Desktop, ensure the dist/index.js path is an absolute path to the built file.
• Monitor logs for any blocked or non-approved operations to refine the allowlist over time.