| FMRS | 37 / 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 | 13 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 9 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 5 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - Geospatial analysts wanting a unified desktop GIS + AI workflow
- Developers who want to run local LLMs and connect custom MCP tools
- Open-source users comfortable building from source under GPL-3.0
| - 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 looking for an MCP server entry to configure in clients like Claude Desktop (Arion is not an MCP server and ships no server manifest)
- Users who need official turn-key installers (binary releases are not yet published)
- Non-technical users unwilling to build an Electron app and compile native modules
| - 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 | - Local file system read/write for app data (SQLite) and the knowledge base (PGlite)
- Network access to call cloud LLM provider APIs
- Access to a local Ollama instance if local models are configured
- Execution of system GDAL binaries for raster processing
- Connections to user-defined MCP servers and execution of their tools
| - 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 project is early-stage (v0.0.14); several features (plugin system, Python agent runtimes, SpatiaLite integration) are planned only
- Building from source is required; native modules (better-sqlite3, keytar) can fail to compile
- Connecting custom MCP servers executes external code whose safety you must evaluate yourself
- With cloud LLMs, query content is sent to third-party APIs
| - 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, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 0 | 26 | 11 |
|---|