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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandB | Execute a command in the specified shell (powershell, cmd, or gitbash) Example usage (PowerShell): Example usage (CMD): Example usage (Git Bash): |
| get_command_historyA | Get the history of executed commands Example usage: Example response: |
| ssh_executeA | Execute a command on a remote host via SSH Example usage: Configuration required in config.json: |
| ssh_disconnectA | Disconnect from an SSH server Example usage: Use this to cleanly close SSH connections when they're no longer needed. |
| create_ssh_connectionC | Create a new SSH connection |
| read_ssh_connectionsB | Read all SSH connections |
| update_ssh_connectionC | Update an existing SSH connection |
| delete_ssh_connectionC | Delete an existing SSH connection |
| get_current_directoryA | Get the current working directory |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current Working Directory | The current working directory of the CLI server |
| SSH Configuration | All SSH connection configurations |
| CLI Server Configuration | Main CLI server configuration (excluding sensitive data) |
TDQS
Scored across 9 tools
Most tools have distinct purposes: SSH connection management (create/delete/read/update), SSH operations (execute/disconnect), and local shell operations (execute_command/get_history/get_directory). However, execute_command and ssh_execute both execute commands but in different contexts (local vs remote), which could cause minor confusion if not carefully distinguished by the agent.
All tool names follow a consistent verb_noun pattern with snake_case throughout (e.g., create_ssh_connection, execute_command, get_command_history). The naming is predictable and readable, with no deviations in style or convention.
With 9 tools, the count is well-scoped for a Windows CLI server covering SSH management and command execution. Each tool earns its place by addressing specific operations like connection lifecycle, remote execution, and local shell interactions, without being overly sparse or bloated.
The tool set provides good coverage for SSH connection CRUD (create, read, update, delete) and remote command execution, plus local shell operations. A minor gap exists in local file operations (e.g., read/write files) which could enhance the CLI functionality, but core workflows are adequately supported without dead ends.