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.
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.
Manage AWS EC2, Hetzner, OVH and custom SSH servers: run commands, fetch logs, CloudWatch/CloudTrail queries, fleet health snapshots, IP banning, S3 — with readonly/standard/dangerous guard tiers and a JSONL audit trail.
Quality signal
44/100 (Fair)
44/100 (Fair)
Install path
npx · low
Remote · high
Engagement
1 0 0 6
1 0 0 22
Tools
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
Interactive TUI with mouse and keyboard supportMulti-provider fleet view including AWS, OVHcloud, Hetzner, and custom serversPer-instance dashboards with live resource monitoring and memory snapshotsSSH and SCP integration with auto-detected terminal emulatorRemote command execution with real-time output and historyCloud provider management for OVHcloud and Hetzner including instance lifecycle and billing
