execute_commandLABSCO SUMMARY
The allowlist is the product.
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.
What it is
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.
What you get
execute_commandruns Windows CLI commands;execute_powershellruns PowerShell scriptslist_running_processesreturns active processes;get_system_infocollects configuration detailsget_network_inforeturns network adapter information;get_service_infoqueries Windows services;get_scheduled_taskslists and queries taskscreate_projectscaffolds a React, Node.js or Python project inside a sandboxed ~/AIProjects directorylist_allowed_commandstells you exactly what the server will accept before you ask it for something
Requirements
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.
Setup effort
One command — npx -y @smithery/cli install @alxspiker/Windows-Command-Line-MCP-Server --client claude
USE CASES
Working out why a machine is behaving oddly
Read processes, services and system configuration in one conversation instead of four consoles.
Checking a network problem
Pull adapter configuration and read it back without opening the control panel.
Starting a project from a sentence
Scaffold React, Node.js or Python into a sandboxed directory rather than wherever the shell happened to be.
Knowing the boundary before you hit it
Ask what the server will accept, then write your automation against that list.
9 tools
Listed in project docs. Your client may show a different list.
execute_powershellcreate_projectlist_running_processesget_system_infoget_network_infoget_scheduled_tasksget_service_infolist_allowed_commandsBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
Node.js 16 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
Build from source
git clone https://github.com/alxspiker/Windows-Command-Line-MCP-Server.git
cd Windows-Command-Line-MCP-Server
npm install
npm run buildnpx
npx -y @smithery/cli install @alxspiker/Windows-Command-Line-MCP-Server --client claudeMCP Clients
Claude Desktop
{
"mcpServers": {
"windows-cmd": {
"command": "node",
"args": [
"<YOUR_PATH_TO_DIST>/index.js"
]
}
}
}Build it with the steps above first; <YOUR_PATH_TO_DIST>/index.js is the full path of dist/index.js in your clone.