| FMRS | 55 / 100 · C | 77 / 100 · B | 75 / 100 · B |
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 11 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 9 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 17 / 20 |
| Best for | - Users creating images or videos inside AI coding tools
- Design workflows that benefit from curated prompts and prompt enhancement
- Users with a local GPU or an image-generation API backend
| - 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 | - Users who only need text or conventional coding capabilities
- Users who do not want prompts or reference images sent to third-party cloud APIs unless using local ComfyUI
- Users without a configured generation backend or API credentials who need image or video generation
| - 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 | - Run npx and access the npm package
- Provide an API key or token for MeiGen Cloud or an OpenAI-compatible API
- Access the configured ComfyUI service when using local generation
- Send prompts and, where applicable, reference images to the configured service; local reference images may be uploaded
- Write configuration and generated results to local configuration, image, and video directories
| - 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 | - Cloud backends receive prompts and reference images, with privacy handling determined by the provider
- Reference images are uploaded to Cloudflare R2 and expire automatically after 24 hours
- Image and video generation may incur service costs or be limited by model, resolution, and quality capabilities
- Local files may be compressed and uploaded when using non-ComfyUI backends
- Video generation can take several minutes and may fail if client timeouts are too short
| - 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 Code, Cursor, Codex, Windsurf, Roo Code, OpenClaw, Hermes Agent | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
| Tools | 8 | 26 | 11 |