Hevy (unofficial)

Official registry Other

Create Hevy routines and analyze your training from chat. Unofficial; BYO Hevy PRO API key.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http hevy-unofficial 'https://hevy-coach.ajwallacemusic.workers.dev/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "hevy-unofficial": {
            "type": "http",
            "url": "https://hevy-coach.ajwallacemusic.workers.dev/mcp"
        }
    }
}
NPM package @almostjacked/hevy-mcp
Claude Code
claude mcp add hevy-unofficial -- npx -y @almostjacked/hevy-mcp@0.1.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "hevy-unofficial": {
            "command": "npx",
            "args": [
                "-y",
                "@almostjacked/hevy-mcp@0.1.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. hevy-mcp
  2. Use it
  3. Tools
  4. Privacy Policy

hevy-mcp

Unofficial MCP server for Hevy. Design training programs in chat; your AI creates the routines directly in your Hevy account and analyzes your logged training. Requires a Hevy PRO API key (hevy.com/settings?developer).

Use it

Hosted (easiest — claude.ai web, mobile, desktop)

Add a custom connector in claude.ai → Settings → Connectors:

https://hevy-coach.ajwallacemusic.workers.dev/mcp

You'll be prompted for your Hevy API key; it's stored encrypted in your own OAuth grant and sent only to api.hevyapp.com.

Claude Desktop one-click

Download hevy-mcp.mcpb, double-click, paste your key when prompted.

Local (Claude Code / Cursor / any stdio client)

claude mcp add hevy -e HEVY_API_KEY=<key> -- npx -y @almostjacked/hevy-mcp

Self-host (free, your own infra)

The published package ships the worker — no clone needed:

mkdir hevy-worker && cd hevy-worker && npm init -y
npm install @almostjacked/hevy-mcp wrangler
cat > wrangler.jsonc <<'EOF'
{
  "name": "hevy-mcp",
  "main": "node_modules/@almostjacked/hevy-mcp/dist/worker.js",
  "compatibility_date": "2026-07-01",
  "compatibility_flags": ["nodejs_compat"]
}
EOF
npx wrangler deploy
npx wrangler secret put AUTH_TOKEN     # any long random string — becomes your Bearer token
npx wrangler secret put HEVY_API_KEY   # from hevy.com/settings?developer

Add your worker URL (https://hevy-mcp.<your-subdomain>.workers.dev/mcp) to clients that support custom headers — e.g. Claude Code: claude mcp add --transport http hevy-selfhost <url> --header "Authorization: Bearer <token>". claude.ai custom connectors don't support custom auth headers; for claude.ai use the hosted instance above, or front your worker with Cloudflare Access.

Tools

ToolDescription
search_exercisesSearch the user's Hevy exercise library by name (fuzzy). Returns template id, exact title, type, muscle group and equipment.
list_routine_foldersList the user's routine folders (id + title). Check this before creating a folder — reuse an existing one when the name matches.
create_routine_folderCreate a routine folder, or return the existing folder if one with this exact title already exists (never duplicates).
list_routinesList the user's existing routines (id, title, folder_id, exercise_count). Use to avoid creating duplicates.
create_routinecreate a routine (lb-first: weight_lb snaps to 2.5/5 lb increments; RPE folded into notes; supersets; duration/distance targets supported)
get_workoutsGet the user's most recent logged workouts, newest first, as compact summaries: title, date, duration, and per-exercise set count + top set. Use get_workout for full set-by-set detail of one workout.
get_workoutGet one logged workout with every set (weights in kg). Use the id from get_workouts.
get_workout_countTotal number of workouts the user has ever logged in Hevy.
get_exercise_historypast sets + estimated 1RM in lb for one exercise (full history, optional date range)
get_routineGet one routine in full (all exercises and sets). Always call this before update_routine so you can send back the complete routine.
update_routineReplace an existing routine. WARNING: this overwrites the routine — Hevy replaces its exercises with exactly what you send, so first call get_routine and include every exercise you want to keep. Folder cannot be changed here; duration/distance/custom-metric set targets round-trip safely.
get_training_summaryweekly sessions/volume (lb), sets per muscle group, top-lift 1RM trend

Privacy Policy

Your Hevy API key and training data pass through only to api.hevyapp.com. The stdio/.mcpb versions run entirely on your machine. The hosted instance stores nothing but your encrypted OAuth grant; disconnecting revokes it. Nothing is logged or shared with third parties.

Frequently asked questions

What is Hevy (unofficial)?

Create Hevy routines and analyze your training from chat. Unofficial; BYO Hevy PRO API key.

How do I install Hevy (unofficial)?

It runs as a remote server. In Claude Code: claude mcp add --transport http hevy-unofficial 'https://hevy-coach.ajwallacemusic.workers.dev/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Hevy (unofficial) need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Hevy (unofficial) open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Hevy (unofficial)?

It is published by almostjacked. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.