← Back to directory
H

Hevy MCP

Community
Manage your Hevy workout data from AI assistants via MCP.
GitHub source repository ↗
★ 431 Stars Category · Other Very popular Source revision 3045f6edc272
77FMRS · B
Reliability
12/20
Security and permissions
16/20
Maintenance
16/20
Documentation
18/20
Setup experience
15/20

Hevy MCP Server is an unofficial MCP server for the Hevy fitness app. It provides 26 tools for managing workouts, routines, exercise templates, and body measurements, requiring a Hevy API key (requires Hevy PRO). It supports various MCP clients, runs locally via npm or Docker, and can be hosted remotely via a Cloudflare Worker HTTP endpoint.

Read the FMRS scoring method →

Hevy MCP Server is an open-source Model Context Protocol (MCP) server for the Hevy fitness and workout tracking app. It enables AI assistants to read, analyze, create, and update your Hevy workouts, routines, exercise templates, and body measurements through authenticated Hevy API requests. The server runs locally via npm with stdio transport and requires a Hevy API key (requires Hevy PRO). It registers 26 tools, 4 resources, and 2 guided prompts.

Tools

get-training-summary
Summarize 1-12 weeks of workout activity and body-measurement trends in one call.
get-workouts
List workouts from newest to oldest with exercise and timing details.
get-workout
Get complete details for one workout by ID.
get-workout-count
Return the account's total workout count.
get-workout-events
List workout update and delete events since a timestamp.
create-workout
Create a completed workout in Hevy.
update-workout
Patch workout metadata by ID; omitted fields and all exercises remain unchanged.
replace-workout-exercises
Replace all exercises and sets while preserving workout metadata.
search-routines
Search routine titles and return compact metadata for discovery.
get-routines
List custom and default workout routines.
get-routine
Get one routine and its exercise configuration by ID.
create-routine
Create a reusable workout routine.
update-routine
Replace an existing routine's content.
get-routine-folders
List default and custom routine folders.
get-routine-folder
Get one routine folder's metadata by ID.
create-routine-folder
Create a routine folder.
get-exercise-templates
List exercise templates with equipment and muscle metadata.
get-exercise-template
Get complete metadata for one exercise template by ID.
search-exercise-templates
Search the full exercise catalog by title substring.
create-exercise-template
Create a custom exercise template.
get-exercise-history
Get past performed sets for one exercise template.
get-body-measurements
List dated body measurements.
get-body-measurement
Get the body measurement entry for one date.
create-body-measurement
Create a dated body measurement.
update-body-measurement
Update the body measurement for an existing date.
get-user-info
Return the user's ID, display name, and public profile URL.

Setup

  1. Obtain a Hevy API key from the Hevy app (requires Hevy PRO). 2. Configure your MCP client to use 'npx -y hevy-mcp' with the environment variable HEVY_API_KEY. Alternatively, use Docker: 'docker run -i --rm -e HEVY_API_KEY ghcr.io/chrisdoc/hevy-mcp:latest'. 3. Add the provided JSON configuration to your client's mcpServers. 4. Restart or reconnect your MCP client.
claude_desktop_config.json
{
  "mcpServers": {
    "hevy": {
      "command": "npx",
      "args": [
        "-y",
        "hevy-mcp"
      ],
      "env": {
        "HEVY_API_KEY": "your-hevy-api-key"
      }
    }
  }
}

Fit and risk

Best for

  • 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 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 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 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

Troubleshooting

  1. Ensure Node.js 20 or newer is installed
  2. Confirm HEVY_API_KEY is set correctly as an environment variable
  3. Restart or reconnect your MCP client after configuration changes
  4. Check that the API key is valid and belongs to a Hevy PRO account

Use cases

Analyze training progress: summarize 1-12 weeks of workouts and body measurements.
Ask questions in plain language: find recent sessions, frequently trained exercises, consistency gaps, routine details, or exercise history.
Plan and log training: create or update workouts, routines, folders, custom exercises, and body measurements.
Search without huge responses: discover routines and exercise templates with compact, AI-friendly results.

Supported clients

Claude DesktopFull support
CursorFull support
CodexFull support
Google AntigravityFull support

More servers from this repository