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.
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
uvx · low
npx · high
Engagement
0 0 0 2
4 0 0 22
Tools
Not listed yet
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
