SSH Real 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ssh_executeA | Execute a command on a remote server via SSH and return the output. Uses the system SSH binary so ssh-agent, ProxyCommand, and ~/.ssh/config are honoured automatically. |
| ssh_testB | Test SSH connectivity to a remote host. Verifies that the system SSH binary can reach the host using the current agent/config. |
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 2 tools
ssh_execute and ssh_test have distinct purposes: executing a command vs. testing connectivity. There is no overlap, so an agent can easily choose the correct tool.
Both tools follow the consistent pattern ssh_verb with snake_case, making them predictable and easy to understand.
With only two tools, the server feels too sparse for an SSH utility. Common operations like file transfer, session management, or port forwarding are missing, making the set incomplete for many use cases.
The tool surface covers only command execution and connectivity testing, leaving major gaps such as file operations (scp/sftp), port forwarding, or interactive sessions. This is insufficient for a general-purpose SSH server.