| FMRS | 71 / 100 · B | 77 / 100 · B |
|---|
| Reliability | 11 / 20 | 12 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 |
|---|
| Maintenance | 16 / 20 | 16 / 20 |
|---|
| Documentation | 17 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - Developers building AI applications that need real geocoding, POI search, and routing data
- Logistics, travel, and site-selection workflows that need offline geometry operations (area, buffers, union/intersect/difference)
- Users on clients with MCP Apps support (Claude Desktop, VS Code Copilot, Claude Code, Goose) who want visual, interactive map output
| - 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
|
|---|
| Not for | - Users without a Mapbox account who don't want to obtain an access token
- Fully offline geocoding or routing needs, since most location APIs require live Mapbox connectivity (only the Turf.js geometry tools work offline)
- Fleet-scale optimization with time windows, capacity constraints, or multiple vehicles — the V2 Optimization API needs beta access and isn't registered by default
| - 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)
|
|---|
| Required permissions | - Requires a valid Mapbox access token (MAPBOX_ACCESS_TOKEN), supplied as a secret environment variable
- Local stdio deployment needs outbound network access to call Mapbox APIs
- Using the hosted endpoint requires network access to https://mcp.mapbox.com/mcp
| - 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
|
|---|
| Risks and side effects | - A leaked Mapbox access token can be abused, incurring extra API charges or exceeding quota
- Geocoding, search, and directions tools send addresses, coordinates, and routing preferences to Mapbox APIs, subject to Mapbox's privacy policy
- render_map_tool renders an HTML panel via the MCP Apps protocol, which relies on the client's handling of rich content being trustworthy
- The advanced V2 Optimization API ships in the codebase but is unregistered by default, requiring deliberate beta opt-in
| - 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
|
|---|
| Supported clients | Claude Desktop, Claude Code, GitHub Copilot, Goose, Cursor, Smolagents | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 31 | 26 |
|---|