| FMRS | 72 / 100 · B | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 11 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 16 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 17 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Garmin users wanting to centralize fitness data in AI assistants
- Runners or cyclists needing automated workout generation and scheduling
- Analytical users who prefer natural language queries for health trends
- Developers and hobbyists integrating Garmin data into custom toolchains
| - 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 | - Non-Garmin users or those without a Garmin account
- Applications requiring real-time GPS tracking or instant data push
- Users who want to bypass authentication (requires Garmin account and OAuth tokens)
- Destructive operations like deleting activities (not implemented for safety)
| - 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 | - Read and edit Garmin Connect data (activities, health metrics, workouts, etc.)
- Download activity files to local directory
- Create and schedule workout plans
- Access user's health metrics and body composition data
| - 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 | - Stores OAuth tokens which expire after ~6 months, requiring re-authentication
- HTTP transport has no authentication; if exposed on public network, place behind a reverse proxy
- Some destructive operations (e.g., delete activity) are intentionally not implemented to avoid accidents
- Many tools may increase LLM context overhead, but can be filtered via environment variables
| - 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, opencode | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 0 | 26 | 11 |
|---|