| FMRS | 25 / 100 · D | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 2 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 7 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 10 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 4 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 2 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Privacy-conscious users who want data to remain on-device
- Users needing local AI capabilities on mobile or Mac
- Users working with GGUF models or local-network model servers
| - 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 seeking a server with explicitly documented MCP tools and transport configuration
- Users requiring cloud hosting, remote APIs, or verified MCP client compatibility
- Devices without sufficient hardware resources for the selected 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 | - Use device CPU, GPU, or NPU for local model inference
- Access the microphone for on-device Whisper transcription
- Access the camera for vision analysis
- Access local files or documents for attachments and knowledge-base processing
- Access the local network to connect to OpenAI-compatible remote LLM servers
| - 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 | - Model inference and image generation can consume substantial device resources and memory
- Hexagon NPU support is marked experimental; some quantizations or model architectures may fall back to CPU or produce garbled output
- When connected to a remote LLM server on the local network, data is sent to that service; the README does not specify its privacy policy
- Tool calling may perform searches or query device information and the local knowledge base; no separate MCP permission boundary is documented
| - 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, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 0 | 26 | 11 |
|---|