Shell access from a model is only as good as what it cannot do, and this one starts closed: system information, network configuration, process management and development tooling are permitted, while disk formatting, user management, shutdown and critical registry edits are blocked regardless of mode. `list_allowed_commands` is worth calling first — it means the boundary is inspectable rather than something you discover by hitting it. `--allow-all` exists, and turning it on gives up the guarantee.
A Windows command-line server. It runs CLI commands and PowerShell scripts against an allowlist of safe commands, and adds a set of read-only system-inspection tools on top.
- `execute_command` runs Windows CLI commands; `execute_powershell` runs PowerShell scripts
- `list_running_processes` returns active processes; `get_system_info` collects configuration details
- `get_network_info` returns network adapter information; `get_service_info` queries Windows services; `get_scheduled_tasks` lists and queries tasks
- `create_project` scaffolds a React, Node.js or Python project inside a sandboxed ~/AIProjects directory
- `list_allowed_commands` tells you exactly what the server will accept before you ask it for something
Node.js 16 or later on Windows. Clone, `npm install`, `npm run build`, and point your client at the built `dist/index.js`. It starts with the default safe command set; passing command names as arguments narrows it, and `--allow-all` widens it.
One command — npx -y @smithery/cli install @alxspiker/Windows-Command-Line-MCP-Server --client claude