MCP SSH Manager
Related Servers
Alternatives to MCP SSH Manager
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude to connect to servers via SSH, execute commands, transfer files, and manage connections through natural language.99 npm1MIT
- AlicenseAqualityDmaintenanceEnables SSH remote access to servers through Claude, allowing users to execute commands, transfer files via SFTP, and manage multiple remote connections using natural language.128MIT
- AlicenseNot gradedqualityNot gradedmaintenanceConnects Claude to remote servers via SSH to execute commands, manage files, and browse directories. It allows users to add, edit, and switch between multiple server configurations through natural language conversations.-
- -licenseNot gradedqualityNot gradedmaintenanceEnables Claude Code to control remote servers via SSH for automated deployment, testing, and operations, including command execution and file transfer.4-
- AlicenseNot gradedqualityFmaintenanceEnables Claude to execute commands on remote servers via SSH, with support for SSH config, private keys, password auth, and agent forwarding.72 npmISC
- AlicenseAqualityDmaintenanceEnables natural language SSH server management via Claude Code, allowing users to read logs, check services, run commands, and transfer files across multiple servers.6MIT
TDQS
Scored across 37 tools
Most tools have clear resource-action pairs, but a number of pairs overlap in purpose: ssh_monitor vs ssh_health_check, ssh_execute/ssh_execute_sudo/ssh_execute_group/ssh_session_send, and the two alias tools. The descriptions are detailed enough to separate them with careful reading, but there are more than one or two cases where an agent could select the wrong tool.
The ssh_ prefix and snake_case style are consistent, but the verb position is not: ssh_tunnel_list and ssh_backup_create are noun-first, while ssh_list_servers and ssh_execute_group are verb-first. Mixed commands like ssh_hooks, ssh_monitor, and ssh_history further break the pattern, creating several naming styles in one set.
With 37 tools, the surface is far above the 3-15 tool sweet spot, and even above the 16-25 'heavy but acceptable' range. Though the server tries to cover many SSH domains, the count feels bloated and could be consolidated, especially around execution and monitoring commands.
The server covers many core domains: execution, sessions, tunnels, file transfer, backups, databases, monitoring, and alerting. However, obvious gaps remain, such as no remote file deletion/listing, no server configuration mutation beyond listing, and no backup deletion tool. Agents can work around some gaps via shell commands, but not all lifecycle operations are covered.