Remote SSH MCP
Related Servers
Alternatives to Remote SSH MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to have persistent, fully interactive SSH sessions into remote hosts, behaving like a local terminal.18 npm2MIT
- FlicenseBqualityDmaintenancePersistent SSH sessions for AI assistants, enabling long-running remote shell connections with features like file transfer, port forwarding, and swarm mode.565 npm-
- AlicenseNot gradedqualityBmaintenanceGives AI agents a persistent, interactive PTY shell with multiple concurrent named sessions, supporting SSH and interactive prompts instead of one-shot exec.MIT
- AlicenseBqualityDmaintenanceExecute terminal commands locally or remotely via SSH with session persistence and environment variable support. Manage terminal sessions that maintain state for up to 20 minutes, enabling efficient command execution workflows. Connect using stdio or SSE for flexible integration with AI models and a12MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to run commands on remote SSH-accessible devices via persistent sessions, supporting both POSIX and CLI shells with safety filters.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely execute shell commands on local machines through an SSH interface with session management, command execution, and sudo support.1-
TDQS
Scored across 7 tools
Each tool maps to a discrete part of the SSH session lifecycle: discover hosts, open a session, run a command, interrupt, peek output, list sessions, and close. No two tools could plausibly be selected for the same action.
Most tools follow a consistent ssh_<verb> pattern: open, run, interrupt, peek, list, close. However, ssh_hosts is a noun-resource name rather than an action verb, and ssh_list is slightly generic, so the pattern has minor deviations.
Seven tools cover the full remote-shell workflow without redundancy. Each tool has a clear role, and none feel like filler or unnecessary overlap.
The lifecycle is complete: discover allowed hosts, open persistent shells, run commands, poll and interrupt active commands, enumerate live sessions, and cleanly close. There are no obvious missing operations for the stated remote-shell purpose.