SSH MCP Server
Related Servers
Alternatives to SSH MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceA local Model Context Protocol server that allows LLMs to securely execute shell commands on remote Linux and Windows systems via SSH connections.610 npm2-
- AlicenseNot gradedqualityDmaintenanceA local MCP server that enables LLMs to execute shell commands on remote Linux and Windows systems via SSH with configurable timeout and authentication options.19,226 npmMIT
- AlicenseNot gradedqualityBmaintenanceA local MCP server that enables LLMs to execute shell commands on remote hosts over SSH with multiple authentication methods.35 npm3MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server for secure local system operations, enabling shell command execution and file management via a standardized interface.141Apache 2.0
- AlicenseBqualityCmaintenanceA powerful Python-based Model Context Protocol (MCP) server that enables AI assistants to manage remote Linux machines over SSH directly from your chat interface.62MIT
- AlicenseBqualityDmaintenanceA server that enables remote command execution over SSH through the Model Context Protocol (MCP), supporting both password and private key authentication.19 npm2MIT
TDQS
Scored across 15 tools
The core command tools are cleanly separated by permission level (read-command allowlist, run-command arbitrary, privileged-command sudo), which is a strong distinction. The main fuzzy spots are the SFTP pairs (sftp-upload vs sftp-upload-file, sftp-download vs sftp-download-file), though their descriptions do explicitly explain the stream-vs-context tradeoff so an agent can choose correctly.
Everything is lowercase kebab-case and mostly verb-first (read-command, run-command, open-session, close-session, list-sessions, signal-process, reload-config). Deviations are the sftp-* prefix-namespaced tools where the verb follows the namespace (sftp-list, sftp-upload) and the noun-only privileged-command, plus -file suffix variants that shadow their base names.
Fifteen tools is at the top of the well-scoped range and each one maps to a real SSH capability: connection discovery, session lifecycle, tiered command execution, process signalling, file transfer, and config reload. Nothing looks like filler and the surface is not so large that selection becomes hard.
Coverage of exec, sessions, SFTP, and config lifecycle is solid, but there is no tool to send input to an interactive or background session — read-session-output exists without a corresponding write/send, which is a notable gap in the session lifecycle. There is also no way to add or remove profiles, manage keys, or set up tunnels, so some standard SSH workflows dead-end at run-command workarounds.