chrisdoc/hevy-mcp

Manage your Hevy workouts, routines, folders, and exercise templates. Create and update sessions faster, organize plans, and search exercises to build workouts quickly. Stay synced with changes so your training log is always up to date.

387 ★73 forksTypeScriptUpdated 21h ago

What you need to know

MCP server for the Hevy fitness/workout tracking app — lets AI assistants read, analyze, create, and update workouts, routines, exercise templates, and body measurements through the authenticated Hevy API.

Install

npx -y hevy-mcp (requires Node.js 20+)
bunx hevy-mcp@latest (requires Bun)
docker run -i --rm -e HEVY_API_KEY ghcr.io/chrisdoc/hevy-mcp:latest (linux/amd64 + linux/arm64)
Hosted endpoint (no install): https://mcp.hevy-mcp.dev/mcp with your Hevy API key as a Bearer token
npm install -g @chrisdoc/hevy-cli (separate terminal CLI, standalone Hevy API client)

Usage

  • Create a Hevy API key (available with Hevy PRO), then export HEVY_API_KEY in the environment that starts your MCP client
  • Add to client config: { "mcpServers": { "hevy": { "command": "npx", "args": ["-y", "hevy-mcp"], "env": { "HEVY_API_KEY": "..." } } } }
  • Ask natural-language questions, e.g. "Give me a training summary for the last four weeks" or "Find exercise templates containing squat"
  • Mutation tools (create/update) are exposed with MCP mutation annotations so compatible clients can request confirmation

Key features

  • 26 MCP tools covering training analysis (get-training-summary), workouts, routines, routine folders, exercise templates, exercise history, body measurements, and account info
  • Hosted stateless Streamable HTTP endpoint on a Cloudflare Worker — no Node.js/Docker needed; validates the key each request and does not store it
  • Local stdio mode via npx/bunx/Docker, plus opt-in local Streamable HTTP mode (--transport http)
  • Server-provided MCP prompts: analyze-workout-progress and create-workout-from-routine coordinate multi-step workflows
  • OAuth 2.1 layer (RFC 8414/9728, PKCE) for Claude.ai custom connectors, with access tokens lasting 7 days and refresh tokens 30 days

Best for

Analyzing training progress and logging Hevy workouts from an AI assistant (Claude, Cursor, Codex) for Hevy PRO users.

Caveats

  • Requires a Hevy PRO subscription to obtain a Hevy API key
  • The Hevy API exposes no delete endpoints, so there are no delete tools
  • npx requires Node.js 20 or newer; client must support Streamable HTTP + fixed Authorization header for the hosted endpoint
  • Local Node package enables telemetry by default (opt out with HEVY_MCP_TELEMETRY=0); hosted Worker does not import Node telemetry
  • Create operations can duplicate on retry; update operations replace existing records
Platforms: Windows · macOS · Linux · Web (hosted Cloudflare endpoint)Clients: Claude Desktop · Cursor · Codex CLI / desktop / IDE extension · Google Antigravity · Claude.ai (custom connector via OAuth)
Documentation ↗

Reviewed 2026-08-07

Topics

claudecodexfitnesshevymcpmcp-servermodel-context-protocolworkout-plannerworkout-tracker
View on GitHub ↗
Stars
387★
Forks
73
Language
TypeScript
License
MIT
Created
2025-03-25
Last push
2026-08-06