← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionHevy MCP ServerManage workouts, routines, and exercise data through the Hevy APIHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS66 / 100 · C77 / 100 · B
Reliability9 / 2012 / 20
Security and permissions14 / 2016 / 20
Maintenance12 / 2016 / 20
Documentation17 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Hevy PRO users
  • Fitness enthusiasts who want AI-assisted training analysis and planning
  • Developers who want to integrate Hevy data into MCP clients like Claude Desktop, Codex, Cursor
  • 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 Hevy PRO subscription
  • Users who need deletion capabilities (Hevy API does not expose delete endpoints)
  • Users looking for official support (this is community-maintained, not affiliated with Hevy)
  • 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 Hevy API key (`HEVY_API_KEY`)
  • Can read and write Hevy data (workouts, routines, exercise templates, body measurements, etc.)
  • Hosted endpoint validates the API key with Hevy on each request and forwards it as `api-key` header
  • 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
  • API key leakage risk: never put key in source control, URLs, logs, or screenshots.
  • Mutation risk: create operations may produce duplicates on retry; update operations replace existing records.
  • Privacy: local package enables telemetry by default (can be disabled), sending errors and metrics to external services.
  • Dependency on third-party service: hosted endpoint relies on Cloudflare Worker, availability may vary.
  • Tool confirmation: mutation tools may require client confirmation, but support varies by client.
  • 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, Codex, Cursor, AntigravityClaude Desktop, Cursor, Codex, Antigravity
Tools2626