| FMRS | 68 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 13 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 15 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - AI agents needing cross-platform desktop automation
- Scenarios requiring safety controls with allow/confirm/block
- Privacy-sensitive tasks that should stay local
- Agents wanting to avoid high vision model costs
| - 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 | - Browser-only automation where specialized tools exist
- Cloud-hosted or non-local execution
- Tasks requiring strict human approval
- Pure pixel-based manipulation without vision models
| - 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 | - Desktop control (click, type)
- Read screen content (accessibility tree, OCR, screenshots)
- Open apps and files
- Browser control (CDP)
- Clipboard read/write
- System-level hotkeys
| - 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 | - Agent may perform unintended actions, leading to data loss or system changes
- Sensitive information on screen could be read by the agent
- Potential for malicious actions if agent misbehaves
- Requires proper permission grants, otherwise may not work
- Confirmation mode may interrupt automation flow
| - 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, Claude Code, Cursor, Windsurf, Zed, OpenAI Codex | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 14 | 26 | 11 |
|---|