MCP SSH Orchestrator
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ssh_pingC | Health check. |
| ssh_list_hostsB | List configured hosts. |
| ssh_describe_hostA | Return host definition in JSON. |
| ssh_planC | Show what would be executed and if policy allows. |
| ssh_runC | Execute SSH command with policy, network checks, progress, timeout, and cancellation. |
| ssh_run_on_tagC | Execute SSH command on all hosts with a tag (with network checks). |
| ssh_cancelC | Request cancellation for a running task. |
| ssh_reload_configC | Reload configuration files. |
| ssh_run_asyncB | Start SSH command asynchronously (SEP-1686 compliant). |
| ssh_get_task_statusA | Get current status of an async task (SEP-1686 compliant). Returns task state, progress, elapsed time, and output summary. |
| ssh_get_task_resultA | Get final result of completed task (SEP-1686 compliant). Returns complete output, exit code, and execution metadata. |
| ssh_get_task_outputB | Get recent output lines from running or completed task. |
| ssh_cancel_async_taskC | Cancel a running async task. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ssh_orchestrator_usage | Explain how to safely use the SSH orchestration tools. This is exposed as a prompt template to MCP clients. |
| ssh_policy_denied_guidance | How the LLM should respond when a command is denied by policy. |
| ssh_network_denied_guidance | How the LLM should respond when network policy denies a host. |
| ssh_missing_host_guidance | What to do when a host alias doesn't exist in servers.yml. |
| ssh_missing_credentials_guidance | How to handle missing or incomplete credentials entries. |
| ssh_config_change_workflow | Global rules for suggesting config changes (servers, credentials, policy). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_hosts | Sanitized inventory of all configured host aliases. |
TDQS
Scored across 13 tools
Most tools have distinct purposes. ssh_cancel and ssh_cancel_async_task could cause confusion, but their names and descriptions distinguish them. The three task retrieval tools (output, result, status) are well-differentiated.
All tools follow a consistent ssh_verb_noun pattern with underscores. Naming is predictable and uniform, making it easy for agents to infer tool purpose.
13 tools cover the core SSH orchestration functionality without being excessive. A few additional operations (e.g., adding hosts) could be justified, but the current count is well-scoped.
The tool set covers key workflows: listing/configuring hosts, running commands (sync/async/tag-based), and monitoring tasks. Missing host CRUD operations, but the domain appears focused on execution rather than inventory management.