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