ssh-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SSH_HOST | No | SSH server host address | |
| SSH_PORT | No | SSH server port (default: 22) | 22 |
| SSH_TIMEOUT | No | Default command timeout in milliseconds (default: 30000) | 30000 |
| SSH_PASSWORD | No | SSH password | |
| SSH_USERNAME | No | SSH username | |
| SSH_BLACKLIST | No | Command blacklist, comma-separated regular expressions | |
| SSH_WHITELIST | No | Command whitelist, comma-separated regular expressions | |
| SSH_PASSPHRASE | No | Private key passphrase | |
| SSH_PRIVATE_KEY | No | SSH private key file path | |
| SSH_SOCKS_PROXY | No | SOCKS proxy server address (e.g., socks://user:password@host:port) |
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 |
|---|---|
| execute-commandC | Execute command on connected server and get output result |
| execute-batchC | Execute multiple commands in sequence on connected server |
| uploadC | Upload file to connected server |
| downloadC | Download file from connected server |
| read-fileC | Read contents of a file from the remote server |
| write-fileC | Write content to a file on the remote server |
| list-serversB | List all available SSH server configurations |
| test-connectionC | Test SSH connection and return server information |
| get-statusB | Get comprehensive system status information from the remote server (OS, CPU, memory, disk, processes, services) |
| check-portC | Check if a port is open/listening on the remote server or test connectivity to external hosts |
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 10 tools
Each tool has a clearly distinct purpose with no significant overlap: check-port tests connectivity, execute-command and execute-batch handle command execution, get-status retrieves system info, list-servers manages configurations, and read-file/write-file/upload/download handle file operations. The descriptions clearly differentiate these functions, making misselection unlikely.
All tools follow a consistent verb-noun naming pattern using kebab-case (e.g., check-port, execute-command, list-servers). This uniformity makes the tool set predictable and easy to understand, with no deviations in style or convention.
With 10 tools, the count is well-scoped for an SSH server management domain. Each tool serves a distinct and necessary function, such as connection testing, command execution, file management, and system monitoring, without being excessive or insufficient for the intended purpose.
The tool set provides comprehensive coverage for SSH server operations, including connection management (test-connection, list-servers), system monitoring (get-status, check-port), command execution (execute-command, execute-batch), and full file CRUD operations (read-file, write-file, upload, download). No obvious gaps exist for core workflows.