| FMRS | 34 / 100 · D | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 3 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 7 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 8 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 8 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 8 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Users who use multiple AI clients and want unified data access
- Those wanting a local-first personal infrastructure
- People who want to easily wire up RPA and automation via MCP
| - 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 don't want a local server
- Security-sensitive users who are uncomfortable exposing shell.exec
- Those expecting a hosted/managed solution
| - 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 | - Network access (defaults to 127.0.0.1)
- File system read/write (configured storage path)
- System command execution (shell.exec and script.run)
- Browser automation (Playwright and Chrome extension)
- Audio input for transcription
| - 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 | - The MCP endpoint is protected by a Bearer token, but leaking the token could allow arbitrary code execution via shell.exec.
- The local server could be exploited by malicious prompts to execute dangerous commands.
- API keys and tokens are encrypted with Fernet, but the key file must be strictly protected.
- autoMate Cloud is opt-in and sends no data unless AUTOMATE_CLOUD_URL is set.
- Using Web Push could expose personal devices.
- SaaS integrations require OAuth tokens, which are stored encrypted.
- Ensure you trust the AI clients you configure with MCP, as they can call shell.exec.
- Audit logs and recommended firewall rules help mitigate risks.
| - 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, OpenClaw, Cursor, Cline | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 15 | 26 | 11 |
|---|