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.
Developer toolkit: auto-detect stack for AI context files, catch port conflicts, validate .env schemas, spot docs drift, audit dependency licenses, and time coding tasks — 7 MCP tools, one install.
Quality signal
44/100 (Fair)
44/100 (Fair)
Install path
uvx · low
npx · high
Engagement
0 0 0 2
2 0 0 3
Tools
Not listed yet
Six integrated tools accessible via one MCP serverEndpoints for stack detection, port checks, env validation, docs drift, license scanning, and task…Unified health report aggregating all tool resultsCLI commands for project onboarding, health checks, and MCP server managementSupports Node.js 20+ with stdio communication
