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, filesystem, and background-job tools for Claude Desktop on Linux/macOS. Zero npm deps, pure Node.
Quality signal
44/100 (Fair)
32/100 (Emerging)
Install path
npx · low
Remote · high
Engagement
1 0 0 6
3 0 0 2
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
Run shell commands via bash with stdout, stderr, and exit codeRead files with optional offset and limitWrite files with automatic parent directory creationList directory entries with type, size, and modification timeManage background jobs: spawn, read output, list, and killLocal-only operation with no external data transmission
