| FMRS | 58 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 12 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 14 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 10 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Individuals or teams who want control over their data and need a self-hosted AI chat workspace
- Developers familiar with Next.js, React, and TypeScript
- Users needing multi-provider integration and plugin extensibility
| - 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 | - Public multi-user services requiring a turnkey SaaS security boundary (accounts, tenant isolation)
- Users who do not want to manage their own deployment and configuration
- Users needing native agent orchestration (only limited Agent mode in browser)
| - 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 | - Browser storage access (localStorage, IndexedDB, OPFS)
- Network access to connect to model providers, search, RAG, voice, and MCP servers
- Server-side API routes execute plugins, MCP, and proxy requests
- Optional server environment variables for deployment defaults and security
- Docker deployments may expose port 3000
| - 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 entails security responsibilities; public exposure requires additional hardening
- User-entered provider credentials are encrypted in the browser, but server misconfiguration could expose them
- Hosted mode depends on shared stores like Upstash and restricts network policies
- Remote MCP servers can execute tools; configure carefully
- Data is stored in the browser by default; clearing browser data may cause loss unless backed up or synced
| - 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 |
|---|