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.
Local-first CLI and MCP wrapper for AI coding agents. Routes shell commands through sage run --, stores command history locally, and returns compressed terminal output to reduce context noise.
Quality signal
44/100 (Fair)
52/100 (Fair)
Install path
uvx · low
npx · high
Engagement
0 0 0 2
2 0 0 10
Tools
Not listed yet
Runs commands and returns compressed terminal output summariesKeeps full raw output and command history locallySupports shortcuts for common commands (e.g., pytest, npm test, git status)Tracks token savings and command success metricsOptional cloud mode for sending aggregate proof metricsCompatible with multiple AI coding agents and CI scripts
