| FMRS | 9 / 100 · D | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 2 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 1 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 3 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 2 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 1 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Endurance athletes (cycling, running, triathlon) seeking professional-level insights.
- Users who prefer self-hosting to have full control over their data.
- Athletes looking for AI guidance that considers a holistic view beyond just power numbers.
| - 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 | - Casual users who do not want to deal with technical setup.
- Individuals who want a simple step counter without multiple platform data collection.
- Users seeking advanced strength training plans for gym workouts, rather than endurance focus.
| - 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 user-authorized third-party fitness platforms (e.g., Strava, Whoop, Oura) to sync data.
- Authentication via OAuth 2.0 to securely access user data.
- Storage and processing of personal health and training data on a self-hosted server or cloud.
| - 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 | - Privacy risk: Aggregating health data requires access to multiple third-party accounts; if credentials are compromised, there is a risk of data breach.
- Data accuracy: Analysis depends on the accuracy of synced data; sync issues may lead to incorrect recommendations.
- AI errors: AI analysis powered by Gemini may have inaccuracies or misinterpretations, so it should not replace professional medical or coaching advice.
- Dependency on external services: AI and some integrations rely on Google services and third-party API keys; outages may affect functionality.
| - 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, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 0 | 26 | 11 |
|---|