| FMRS | 66 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 11 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 13 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 14 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Home-automation users with a local UniFi controller
- Users who want an AI assistant to query Protect cameras, recordings, and detection events
- UniFi Protect deployments that can provide a local administrator or service account
| - 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 who only have a Ubiquiti SSO cloud account
- Users seeking Network or Access server functionality
- Evaluations that require canonical tool names and a complete tool list when those identifiers are not provided in the source
| - 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 | - Access to the UniFi controller IP address or hostname
- A local administrator account username and password
- An optional API key for selected capabilities; the manifest labels this experimental
- Account permissions within the scope the user is comfortable granting to the MCP server
| - 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 | - Camera events and recordings may contain sensitive information about people and locations
- The server can manage Protect data and devices, so overly broad account permissions increase potential impact
- UNIFI_VERIFY_SSL defaults to false, so SSL certificates may not be verified
- The username, password, and optional API key are sensitive configuration values and should be protected
| - 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, Codex, OpenClaw | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 0 | 26 | 11 |
|---|