| FMRS | 77 / 100 · B | 75 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 12 / 20 | 13 / 20 | 10 / 20 |
|---|
| Security and permissions | 16 / 20 | 12 / 20 | 16 / 20 |
|---|
| Maintenance | 16 / 20 | 16 / 20 | 18 / 20 |
|---|
| Documentation | 18 / 20 | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 15 / 20 | 17 / 20 | 14 / 20 |
|---|
| Best for | - 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
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - 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)
| - Users needing to write to upstream databases (read-only)
- Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
- Users expecting all advanced features without API keys
|
|---|
| Required permissions | - 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
| - Requires internet access to query public biomedical APIs
- Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
- Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
|
|---|
| Risks and side effects | - 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
| - Upstream API rate limits may affect performance
- Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
- Features requiring API keys (e.g., OncoKB) may be incomplete without them
- Local binary installations need regular updates for compatibility
|
|---|
| Supported clients | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 26 | 11 | 11 |
|---|