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.
What Chrome DevTools MCP is for the browser, tui-mcp is for the terminal. Launch, screenshot, and interact with any TUI app.
Quality signal
44/100 (Fair)
43/100 (Fair)
Install path
npx · low
npx · high
Engagement
1 0 0 6
2 0 0 12
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
Launch and manage persistent terminal sessions with real PTYsCapture terminal screenshots as PNG or text snapshotsSend keystrokes, text input, and mouse events to appsRead terminal buffer, scrollback, cursor position, and raw outputWait for text patterns, idle state, or process exitResize terminal and list or kill sessions
