SSH 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ssh_execute_sshC | Execute command on remote Linux host via SSH |
| ssh_execute_sudoC | Execute command with sudo on remote Linux host |
| ssh_setup_credentialsC | Setup credentials for a Linux host using GUI prompts |
| ssh_clear_credentialsB | Clear all cached SSH credentials |
| ssh_get_system_infoC | Get basic system information from Linux host |
| ssh_get_running_processesC | Get running processes from Linux host |
| ssh_get_disk_usageC | Get disk usage information from Linux host |
| ssh_get_servicesC | Get systemd services status from Linux host |
| ssh_puppet_noopA | Run Puppet agent in no-op mode (dry run) with verbose output |
| execute_sshC | Legacy compatibility - Execute command on remote Linux host via SSH |
| execute_sudoC | Legacy compatibility - Execute command with sudo on remote Linux host |
| cache_credentialsD | Legacy compatibility - Pre-cache credentials |
| get_running_processesC | Legacy compatibility - Get running processes from Linux host |
| get_disk_usageC | Legacy compatibility - Get disk usage information from Linux host |
| get_servicesC | Legacy compatibility - Get systemd services status from Linux host |
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 15 tools
Five of fifteen tools are explicit 'Legacy compatibility' duplicates of newer tools with near-identical descriptions (get_running_processes vs ssh_get_running_processes, execute_ssh vs ssh_execute_ssh, execute_sudo vs ssh_execute_sudo, cache_credentials vs ssh_setup_credentials). An agent must guess whether the legacy or ssh_-prefixed variant is the intended entry point, and the descriptions offer no behavioral difference to disambiguate.
All names are snake_case, but two competing prefix schemes coexist (bare verb_noun vs ssh_-prefixed), and verb ordering flips between pairs like execute_ssh and ssh_execute_ssh. The result is a set where the same action is spelled two different ways, which undermines predictability.
Fifteen tools is within a reasonable range for an SSH/remote-admin server, and the functional surface (execute, sudo, credentials, system info, processes, disk, services, puppet) is sensibly scoped. However, roughly a third of the count is pure legacy duplication, so the effective tool set is ~10 padded out with redundant entries.
Core remote-admin workflows are covered: command execution, privileged execution, credential lifecycle (setup/clear/cache), system info, processes, disk, services, and Puppet dry-run. Gaps exist around file transfer/scp and host inventory listing, but agents can work around these via the execute tools.