MCP SSH Session
Related Servers
Alternatives to MCP SSH Session
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to establish and manage persistent SSH sessions, supporting smart command execution, async tasks, multi-host, sudo, and file operations through SFTP.1534 PyPIMIT
- AlicenseAqualityDmaintenanceEnables AI agents to establish and manage persistent SSH connections to remote hosts for executing commands. Supports SSH config files, multi-host management, and automatic reconnection with thread-safe concurrent operations.1559 PyPI11MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely execute commands, transfer files, and manage port forwarding on remote servers via SSH.158 npm38Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to maintain persistent SSH terminal sessions and transfer files to/from remote servers. Allows stateful command execution, natural language server management, and seamless file operations through SSH connections.5 npm36MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to have persistent, fully interactive SSH sessions into remote hosts, behaving like a local terminal.15 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to securely execute commands on remote hosts via SSH and SFTP, with persistent shells, file transfers, screenshots, and an audit log.5MIT
TDQS
Scored across 15 tools
The tools mostly target distinct areas: session lifecycle, command execution, async job control, file I/O, and interactive terminal input. There is some overlap among send_input, send_input_by_session, send_keys, and interrupt_command_by_id versus sending Ctrl+C, but descriptions clarify command-scoped versus session-scoped usage.
All tool names use snake_case with a verb-first pattern such as list_sessions, close_session, execute_command, read_file, get_command_status, and send_input. Suffixes like _async and _by_id are descriptive and do not break the overall convention.
Fifteen tools is at the high end of a reasonable range but matches the server's broad scope across SSH sessions, async commands, file operations, and interactive terminals. Most tools earn their place, though the interactive input surface adds some density.
Core SSH workflows are covered: session lifecycle, synchronous and asynchronous command execution, command monitoring, file read/write, and interactive input. Minor gaps include no explicit session-open tool and no dedicated directory or file-management operations like mkdir, rm, or listing, though these can be handled via execute_command.