Alolite 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ssh_executeB | Execute a command on a remote server via SSH and return the output |
| ssh_connectionsC | Manage SSH connections (list active connections, close connections, get connection status) |
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
The two tools are clearly distinct: one executes commands, the other manages connections. There is no overlap or ambiguity between them.
Both tools share the 'ssh_' prefix, but 'ssh_execute' is a verb while 'ssh_connections' is a noun. This inconsistency in verb/noun pattern makes the naming slightly mixed, though still readable.
With only two tools, the server feels minimal. While the scope is narrow (SSH command execution and connection management), the modest count is borderline—not quite enough to feel comprehensive, but not excessive.
The tool set covers executing commands and managing existing connections, but lacks common SSH operations like creating new connections or transferring files. These gaps are significant for a server intended to provide SSH functionality.