| FMRS | 49 / 100 · D | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 7 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 12 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 9 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Enterprise agent teams that need governable, auditable policies
- Developers who want a generalist agent they only configure with domain tools and policies
- Hybrid workflows that must combine browser interaction with API calls
- Teams using the Python SDK or self-hosting on Kubernetes
| - 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 | - Lightweight scenarios that only need a single simple tool call
- Offline users who cannot supply any LLM API key or self-hosted model
- End users expecting zero-configuration out-of-the-box use
| - 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 | - Reading the repository and local workspace files (e.g. files under cuga_workspace)
- Network access to LLM providers, OpenAPI services, and MCP servers
- In hybrid/web mode, controlling browser pages through the browser extension and Playwright
- Accessing Docker/Podman or E2B cloud execution environments when sandboxing is enabled
- In manage mode, drafting and publishing agent configuration (tools, MCP, LLM, policies)
| - 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 agent can call real APIs and act on web pages on the user's behalf, so mistakes can have real business impact
- Misconfigured policies or sandboxes weaken isolation; local Python execution is the default and is less isolated
- Exposing the local registry to E2B via tunnels such as ngrok increases the attack surface
- The knowledge base and saved trajectories may contain sensitive enterprise data that you must store and access-control yourself
- Runs against self-hosted or internal models, so token and cost accounting must be converted with your own rates
| - 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 | CUGA SDK, MCP | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 2 | 26 | 11 |
|---|