| FMRS | 58 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 12 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - AI agents that need live public web data
- Research and analytics workflows requiring scraping or structured data
- Coding agents that need current npm or PyPI package information
- Users requiring browser automation through Pro mode
| - 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 | - Private, unauthorized, or internal data access
- Users unwilling to provide a Bright Data API key
- Offline environments or local setups without Node.js/npx
- Workflows that cannot accommodate usage-based Pro or web-data costs
| - 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 | - A Bright Data API_TOKEN is required
- The server needs access to Bright Data services and the public web
- WEB_UNLOCKER_ZONE and BROWSER_ZONE may be configured optionally
- PRO_MODE, GROUPS, TOOLS, timeout, and retry settings may be configured optionally
| - 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 | - Requests consume account credits; base tools are charged per request and web_data_* tools per returned record
- The free tier provides 5,000 credits per month and unused credits do not roll over
- PRO_MODE incurs additional usage-based charges
- API_TOKEN is a secret credential and should not be exposed in logs or shared configuration
- Live web content, availability, and scraping results may depend on target sites and network conditions
| - 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, Cursor, Windsurf | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 29 | 26 | 11 |
|---|