NikolaNddTesla/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 |
|---|---|
| list_serversA | List all configured servers and active connections |
| get_serverB | View server configuration details |
| connectB | Manually connect to server (usually not needed, tools auto-connect) |
| quick_connectA | Temporary server connection (not saved). Returns host:port as server_id for subsequent operations |
| disconnectC | Disconnect from server |
| test_connectionA | Test server connectivity (does not affect existing connections) |
| executeC | Execute shell command on remote server |
| write_fileA | Write content to remote file (overwrite) |
| read_fileA | Read remote file content (supports line range, suitable for logs and config files) |
| upload_fileA | Upload local file to remote server (path-based, zero token cost. Use async mode for large files) |
| upload_directoryA | Upload local directory to remote server (auto compress, transfer, and extract. Use async for large dirs) |
| download_fileB | Download file from remote server (use async mode for large files) |
| download_directoryA | Download remote directory (remote compress → download → local extract. Use async for large dirs) |
| transfer_statusA | Check background transfer task progress (use with async_transfer=true) |
| add_serverC | Add or update server configuration |
| update_serverA | Update server configuration (only pass fields to change, rest unchanged) |
| delete_serverC | Delete server configuration |
| rename_serverC | Rename server ID (alias) |
| list_proxiesA | List all configured SOCKS proxies |
| add_proxyC | Add or update SOCKS proxy preset |
| delete_proxyC | Delete proxy preset |
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 21 tools
Each tool targets a distinct operation: file transfer, server configuration, proxy management, connection handling, or command execution. Even similar tools like connect and quick_connect have clear differences (persistent vs temporary). No two tools appear to do the same thing.
Tool names mostly follow a verb_noun pattern (upload_directory, add_server, list_proxies), but a few single-word verbs like connect, disconnect, and execute break the pattern slightly. The inconsistency is minor and does not cause confusion.
With 21 tools, the server spans multiple sub-domains (file transfer, server CRUD, proxy management, connection lifecycle), making the count feel heavy but not excessive. It is on the borderline for a typical MCP server scope.
The tool surface covers server CRUD, proxy management, file transfer (upload/download, file/directory), file read/write, and command execution. Notable gaps include remote file deletion and remote directory listing, which agents might need but can work around.