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.
Administer a Linux server from an MCP client such as Cursor or VS Code: read files and tail logs, check/reload/restart systemd services, manage cron jobs inside a dedicated crontab section, run read-only MySQL queries, drive WP-CLI on WordPress sites, run safe Git commands, and execute sandboxed Python. Directories, services and WordPress sites are allowlisted in config.json, and every tool returns a uniform {success, data, error, meta} response. Runs as a systemd service over HTTP.
Full-text search over your shell history (zsh / bash / fish) via SQLite FTS5. Local-only. 11-pattern secret redaction runs BEFORE insert. Captures cwd / exit code / duration via opt-in shell hook. Tools: searchhistory, recentindir, failedcommands, commandchains, reindex.
Quality signal
44/100 (Fair)
49/100 (Fair)
Install path
uvx · low
npx · high
Engagement
0 0 0 2
1 0 0 4
Tools
Not listed yet
Full-text search with SQLite FTS5Local-only storage with secret redaction before insertOptional shell hook to capture cwd, exit code, and durationTools for searching, recent commands by directory, failed commands, and command chainsSupports zsh, bash, and fish shellsEasy integration with MCP clients via stdio
