Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.
Manage multiple SSH servers from one MCP: command execution, file transfer/rsync, database dump/import/query (MySQL/PostgreSQL/MongoDB), backups & restore, health monitoring, persistent sessions, tunnels, ProxyJump/bastion, and opt-in per-server security modes (readonly/restricted) with audit log. Linux, macOS & Windows OpenSSH.
Answers "what did that command print?" from your real terminal history: a per-command PTY session recorder (OSC 133) stores every command's full output, exit code, cwd, and duration in local SQLite/FTS5, and the MCP server searches, retrieves, and diffs those outputs — secret redaction on by default before anything reaches the model.
Quality signal
52/100 (Fair)
44/100 (Fair)
Install path
npx · high
npx · low
Engagement
3 0 0 405
1 0 0 6
Tools
Per-server SSH agent forwarding (ForwardAgent) supportOpt-in readonly and restricted security modes with audit loggingSupport for ProxyJump/bastion hosts and SSH tunnelsShell-quoted arguments to prevent command injectionCross-platform compatibility with Linux, macOS, and Windows OpenSSH
Per-command PTY session recording with OSC 133 semantic-prompt marksLocal SQLite database with FTS5 trigram full-text searchZstd-compressed command outputs with configurable head/tail captureAutomatic redaction of secrets before output reaches the modelCross-platform shell integration for Bash, Zsh, Fish, PowerShellNo cloud or telemetry; all data stored locally in a single SQLite file
