| FMRS | 70 / 100 · B | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 11 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 14 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 17 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Affiliate publishers who want natural-language access to multiple networks
- Agencies managing multiple brands' programs
- Teams needing periodic reporting and anomaly monitoring
| - 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 without an AI client (e.g., Claude Desktop)
- Advertisers needing write operations (e.g., link creation) since advertiser adapters are read-only
- Clients that are not yet officially supported (e.g., Cursor, VS Code) without testing
- Networks where clicks are essential, as many adapters lack click support
| - 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 | - Credentials for network APIs (API keys, tokens, etc.)
- Optional: local file write to `~/.affiliate-mcp/.env` and `brands.json`
- Optional: anonymous usage telemetry (off by default)
- Optional: local result cache (off by default; writes files when enabled)
| - 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 | - Experimental community adapters may be unreliable or return inaccurate data.
- Credentials stored in local files; risk if file permissions are loose or device compromised.
- Hosted connector stores credentials in encrypted vault but involves third-party service.
- API calls may incur rate limits or costs depending on the network.
- Untested client paths may not work; check support status table.
| - 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, Claude Code, Codex, Claude Cowork | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 0 | 26 | 11 |
|---|