MCP SSH 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 |
|---|---|
| ssh_connectC | Connect to an SSH server |
| ssh_disconnectC | Disconnect from an SSH server |
| ssh_executeC | Execute a command on a remote SSH server |
| ssh_copy_fileB | Copy files between local and remote servers or between remote servers |
| ssh_list_filesC | List files and directories on local or remote server |
| ssh_file_infoC | Get file information (size, permissions, etc.) |
| ssh_start_interactive_shellC | Start an interactive shell session with PTY support for typing simulation |
| ssh_send_inputC | Send input to an interactive shell session with optional typing simulation |
| ssh_read_outputC | Read output from an interactive shell session |
| ssh_close_interactive_shellC | Close an interactive shell session |
| ssh_save_credentialC | Save SSH credentials for reuse |
| ssh_list_credentialsB | List all saved SSH credentials |
| ssh_delete_credentialC | Delete a saved SSH credential |
| ssh_connect_with_credentialC | Connect to SSH server using saved credentials |
| ssh_set_working_directoryC | Set the current working directory for a connection |
| ssh_get_working_directoryB | Get the current working directory for a connection |
| ssh_docker_deployC | Deploy Docker containers with working directory context |
| ssh_docker_statusC | Check Docker container status in working directory |
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 18 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, ssh_connect, ssh_execute, ssh_copy_file, and ssh_docker_deploy target different operations (connection, command execution, file transfer, and container deployment), and interactive shell tools (start, send_input, read_output, close) are well-separated from credential management and file operations.
All tool names follow a consistent 'ssh_' prefix with snake_case and descriptive verb_noun patterns (e.g., ssh_connect, ssh_execute, ssh_list_files). This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming style.
With 18 tools, the count is slightly high but reasonable for the SSH server domain, covering connection management, file operations, Docker interactions, credential handling, and interactive shells. It's well-scoped, though some tools like ssh_docker_deploy and ssh_docker_status might be considered optional extensions.
The tool surface provides complete coverage for SSH operations, including CRUD for connections (connect, disconnect), credentials (save, list, delete), files (list, copy, info), directories (get/set working directory), command execution, and interactive shells with full lifecycle support. No obvious gaps exist for the stated purpose.