Windows Command Line MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_running_processesA | List all running processes on the system. Can be filtered by providing an optional filter string that will match against process names. |
| get_system_infoB | Retrieve system information including OS, hardware, and user details. Can provide basic or full details. |
| get_network_infoB | Retrieve network configuration information including IP addresses, adapters, and DNS settings. Can be filtered to a specific interface. |
| get_scheduled_tasksB | Retrieve information about scheduled tasks on the system. Can query all tasks or get detailed status of a specific task. |
| get_service_infoB | Retrieve information about Windows services. Can query all services or get detailed status of a specific service. |
| list_allowed_commandsA | List all commands that are allowed to be executed by this server. This helps understand what operations are permitted. |
| execute_commandB | Execute a Windows command and return its output. Only commands in the allowed list can be executed. This tool should be used for running simple commands like 'dir', 'echo', etc. |
| execute_powershellB | Execute a PowerShell script and return its output. This allows for more complex operations and script execution. PowerShell must be in the allowed commands list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no overlap: execute_command for basic commands, execute_powershell for scripts, get_network_info for networking, get_scheduled_tasks for tasks, get_service_info for services, get_system_info for system details, list_allowed_commands for permissions, and list_running_processes for processes. The descriptions clearly differentiate them, preventing misselection.
The naming is mostly consistent with a verb_noun pattern (e.g., execute_command, get_network_info, list_allowed_commands), but there is a minor deviation with 'list_running_processes' using 'running' as an adjective instead of a simple noun like 'processes'. This slight inconsistency does not significantly hinder readability.
With 8 tools, the count is well-scoped for a Windows command line server, covering essential operations like command execution, system queries, and permissions. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides good coverage for querying system state (e.g., network, services, tasks) and executing commands, but there are minor gaps such as no tools for managing or modifying these elements (e.g., starting/stopping services, creating tasks). Agents can work around this by using execute_powershell for such operations.