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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_ssh_commandC | Execute command on remote server via SSH |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct as it is the sole operation available.
The single tool name follows a clear verb_noun pattern (execute_ssh_command), and with only one tool, consistency is inherently perfect as there are no other names to compare against.
One tool is too few for a server named 'SSH MCP Server', which implies broader SSH functionality. A single command execution tool feels thin and incomplete for managing SSH connections, lacking operations like file transfer, session management, or configuration.
The tool surface is severely incomplete for SSH operations. It only covers command execution, missing essential functions such as scp for file transfer, key management, or connection setup, which are core to SSH workflows and expected from the server's name.