| FMRS | 61 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 14 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 11 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Research and analysis agents that need citable page evidence.
- PDF workflows requiring tables, layout, and visual evidence.
- Teams seeking local-first document processing with trust reports.
| - 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 | - Workflows that only need a simple plain-text dump.
- Assuming complete pure-Rust Document Twin capabilities; the README states that pure Rust is still a work in progress.
- Unspecified remote authentication, write, or collaboration features.
| - 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 | - The server needs access to read the local PDF paths supplied in requests.
- URL loading, if used, must comply with configured host, private-IP, size, and HTTP policies.
- OCR and visual-enrichment providers are configured by the deployment environment; requests cannot select arbitrary executables or arbitrary provider URLs.
| - 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 | - PDFs may contain hostile, misleading, or prompt-injection-like content.
- Hidden text, nearly invisible text, overlapping text, unsafe links, and redaction signals may affect extraction or trust assessment.
- OCR, table extraction, and visual analysis can produce low-confidence results and should be checked against rendered pages or crops.
- The README and server manifest identify different product versions, so the intended version should be confirmed before installation.
| - 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, VS Code, Any MCP client | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 3 | 26 | 11 |
|---|