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.
Terminal MCP server for AI coding agents with persistent PTY sessions, ring-buffer incremental reads, headless xterm screen capture, multi-agent orchestration, and a real-time web dashboard.
Quality signal
44/100 (Fair)
45/100 (Fair)
Install path
npx · low
npx · high
Engagement
1 0 0 6
4 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
Real PTY support via node-pty for interactive programs and TUIsIncremental ring-buffer reads returning only new terminal outputServer-side headless xterm rendering for clean screen snapshotsMulti-agent orchestration with session groups and event subscriptionsPreact-based real-time web dashboard for terminal and chat monitoringZero-configuration startup with HTTP MCP endpoint
