| FMRS | 61 / 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 | 12 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Advanced users who want composable, shareable elements for deep AI customization
- Security-conscious teams needing permission governance and auditable agent execution
- Users of MCP clients with full tool-call round-trip support, especially Claude Code
| - 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 require a server officially maintained by an upstream product owner (this is an independent community project)
- Users relying on Claude Desktop native permission-hook flows (not supported in this release)
- Beginners wanting a zero-config experience with no understanding of elements and permission policies
| - 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 | - Reads and writes local Markdown/YAML element files in ~/.dollhouse/portfolio/
- Optionally uses GITHUB_TOKEN for GitHub portfolio sync and community submissions
- Update/delete/execute MCP-AQL operations require per-operation confirmation by default (auto-approvable via policy)
- Agent execution may trigger high-risk operations (file deletion, external API calls, system commands), constrained by danger-zone enforcement and autonomy evaluation
| - 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 | - Activating elements immediately changes AI tool access and permissions; misactivating a restrictive element can block operations
- Third-party elements from the community collection may contain undesirable content or policies; review before installing
- Agents can execute multi-step tasks autonomously — danger zones and audits exist, but human oversight is still required
- AGPL-3.0 requires source disclosure for network use; verify compliance for commercial integrations
| - 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, Claude Desktop, Cursor, VS Code, Codex, Gemini CLI, Windsurf, Cline, LM Studio | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 7 | 26 | 11 |
|---|