← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionArionThe first agentic AI desktop app for geospatial analysisHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS37 / 100 · D77 / 100 · B
Reliability3 / 2012 / 20
Security and permissions7 / 2016 / 20
Maintenance13 / 2016 / 20
Documentation9 / 2018 / 20
Setup experience5 / 2015 / 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
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)
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
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
Supported clientsClaude Desktop, Cursor, Codex, Antigravity
Tools026