| FMRS | 48 / 100 · D | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 6 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 10 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 15 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 9 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 8 / 20 | 15 / 20 | 17 / 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
| - Scenarios needing clean, structured web context fed to an AI assistant
- Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
|
|---|
| 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)
| - Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
- Sites that explicitly disallow automated access (robots.txt)
|
|---|
| 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
| - Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
- firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
|
|---|
| 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
| - Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
- firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
|
|---|
| Supported clients | Claude Desktop, Cursor | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 5 | 26 | 11 |
|---|