← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionUniFi MCP ServerMCP server for managing UniFi network devices, WiFi, and firewalls via the official UniFi APIHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS48 / 100 · D77 / 100 · B
Reliability6 / 2012 / 20
Security and permissions10 / 2016 / 20
Maintenance15 / 2016 / 20
Documentation9 / 2018 / 20
Setup experience8 / 2015 / 20
Best for
  • Home or small-office users running a local UniFi gateway who want AI-assisted network operations
  • Technically comfortable users familiar with UniFi controller concepts who will validate tool behavior incrementally
  • Hevy PRO users who want AI assistants to directly access their workout data
  • People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
  • Anyone needing summaries and insights from their training data
Not for
  • Users limited to cloud API access who need full device/client-level control (cloud modes are largely read-only)
  • Enterprise deployments requiring production-grade audit logging, RBAC, or dry-run safeguards that are already fully implemented (per the README, these are still planned)
  • Users without a Hevy PRO subscription (API key required)
  • Users who want to use the server without an API key
  • Those needing delete workflows (Hevy API does not expose delete endpoints)
Required permissions
  • UniFi controller address (local gateway IP or cloud API) and login credentials (username/password or API key)
  • Direct network reachability to the controller (local gateway mode requires LAN access)
  • Write access to firewall rules, networks/VLANs, WiFi, and device state if mutating tools are used
  • Requires HEVY_API_KEY environment variable for Hevy API authentication
  • Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
  • Read operations can fetch workouts, routines, folders, templates, history, and user info
Risks and side effects
  • The server can perform broad administrative operations on network infrastructure (restart/upgrade devices, modify firewall and WiFi settings); misconfiguration can disrupt network connectivity
  • Credentials (API key or username/password) are configured as plaintext environment variables and must be handled carefully
  • The README indicates local gateway mode defaults SSL certificate verification to false (UNIFI_LOCAL_VERIFY_SSL), which carries a man-in-the-middle risk
  • The server.json manifest and the README describe different versions, packaging, and auth variables — copying either config verbatim without reconciling may fail to connect
  • Dry-run mode, audit logging, and RBAC are documented as 'planned' rather than shipped, so they cannot be relied on as active safeguards
  • API key can be misused if leaked; do not expose in URLs, logs, or screenshots
  • Create operations may produce duplicates on retry; update operations replace existing records
  • The server sends data to the Hevy API and may send telemetry to external services unless disabled
Supported clientsClaude Desktop, CursorClaude Desktop, Cursor, Codex, Antigravity
Tools526