| FMRS | 57 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 5 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 10 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 14 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Individual users needing shared persistent memory across multiple AI tools.
- Developers who want to self-host a memory layer on Cloudflare's free tier.
- Users prioritizing data privacy and control, as data stays in their own cloud account.
- Users wanting a quick setup with complete ecosystem support (desktop app, CLI, extensions, etc.).
| - 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 | - Teams needing collaborative memory (currently single-user design).
- Users wanting zero technical setup without touching Cloudflare (except desktop app).
- Users requiring offline or local-only memory (depends on cloud services).
- Strict compliance environments that require non-cloud infrastructure.
| - 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 | - Requires a Cloudflare account to deploy the Worker and infrastructure.
- Requires an AUTH_TOKEN (or password) to authorize all clients.
- Supports OAuth 2.0 dynamic client registration; clients do not need to embed the token in configs.
- For calendar, email, and Notion integrations, requires iCal links, app passwords, or Notion connection secrets.
| - 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 | - Self-hosting means you are responsible for maintenance and updates.
- Data is stored on Cloudflare, subject to Cloudflare's privacy policy (though within your own account).
- Free tier may have usage limits (e.g., vector index size).
- If you forget your password, you must log into Cloudflare to reset; you might temporarily lose access to memories.
- Deploying with incorrect parameters (e.g., Vectorize dimensions) can degrade search functionality.
| - 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, ChatGPT, Cursor, Codex CLI | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 8 | 26 | 11 |
|---|