Windows CLI 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandA | Execute a command in the specified shell (powershell, cmd, gitbash, bash, wsl) IMPORTANT GUIDELINES:
Shell-Specific Settings: powershell:
cmd:
gitbash:
bash:
wsl:
Working Directory:
Output Truncation:
Command Timeout:
Examples: Windows CMD: WSL: With custom timeout: Bash: Git Bash: With custom output limit: |
| get_command_outputA | Retrieve the full output from a previous command execution. Use this tool when command output was truncated and you need to see the complete result. The executionId is provided in the truncation message of the original command. Parameters:
Examples: |
| get_current_directoryA | Get the current working directory |
| set_current_directoryC | Set the current working directory |
| get_configA | Get the windows CLI server configuration Returns:
Only enabled shells are included and technical fields like executables are omitted. |
| validate_directoriesA | Check if directories are within allowed paths (only available when restrictWorkingDirectory is enabled) Validation Modes:
Shell-Specific Validation: Add the "shell" parameter to validate for a specific shell: |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| CLI Server Configuration | Complete server configuration with global and shell-specific settings |
| Global Configuration | Global default settings applied to all shells |
| bash Shell Configuration | Resolved configuration for bash shell |
| Security Information | Current security settings and restrictions |
| Command Execution Logs List | List all stored command execution logs with metadata |
| Recent Command Logs | Get most recent command execution logs (supports ?n=<count> and ?shell=<shell>) |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: executing commands, retrieving truncated output, getting configuration, managing current directory, validating paths. No overlap or ambiguity.
All tools use a consistent verb_noun pattern in snake_case (e.g., execute_command, set_current_directory), making them predictable and easy to understand.
Six tools is appropriate for a CLI execution server. They cover core functionality (command execution, output retrieval, directory management, configuration, path validation) without bloat.
The tool set covers the main workflows: executing commands, retrieving full output, managing the working directory, and validating paths. A minor gap is the lack of a tool to list available shells or see shell-specific settings without calling get_config, but it's not essential.