Hevy Mcp Remote
by rwestergrencommunityv0.1.6
An MCP server for the Hevy fitness app that exposes tools for managing workouts, routines, exercise templates, folders, and webhook subscriptions. This fork is packaged for gateway deployment as a streamable-HTTP OCI image, while the underlying server can also run locally over stdio.
From the registry: Hosted/gateway-ready Hevy fitness MCP: workouts, routines, templates.
Install & configure
Prerequisites
- requiredInstall Node.jsNode.js v24 or higher is required for the recommended npx-based stdio run.
- requiredInstall npmnpm v10 or higher is required to run the package with npx.
- requiredGet a Hevy API keyA Hevy API key is required for all operations. The README notes this is available with Hevy PRO.
Install in your client
Paste into the AI you're chatting with — it will figure out the rest
Please install the `hevy-mcp-remote` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Node.js** — Node.js v24 or higher is required for the recommended npx-based stdio run.
- **Install npm** — npm v10 or higher is required to run the package with npx.
- **Get a Hevy API key** — A Hevy API key is required for all operations. The README notes this is available with Hevy PRO.
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","hevy-mcp"]
- required environment variables:
- `HEVY_API_KEY`: Hevy API key used by the server to authenticate all requests to the Hevy API. (example: `<your-hevy-api-key>`)
Note: This repository documents both a hosted HTTP container variant and the upstream stdio npm package. For end-user MCP client configuration, the README explicitly says to use the stdio/npx flow above. The server also supports supplying the API key via CLI argument (--hevy-api-key), but the documented portable MCP config uses the HEVY_API_KEY environment variable.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Note: This repository documents both a hosted HTTP container variant and the upstream stdio npm package. For end-user MCP client configuration, the README explicitly says to use the stdio/npx flow above. The server also supports supplying the API key via CLI argument (--hevy-api-key), but the documented portable MCP config uses the HEVY_API_KEY environment variable.
Tools (19)
get-workouts
Fetch workouts
get-workout
Fetch a single workout
create-workout
Create a workout
update-workout
Update a workout
get-workout-count
Get the number of workouts
get-workout-events
Fetch workout events
get-routines
Fetch routines
get-routine-by-id
Fetch a routine by ID
create-routine
Create a routine
update-routine
Update a routine
get-exercise-templates
Fetch exercise templates
get-exercise-template
Fetch an exercise template
search-exercise-templates
Search exercise templates
get-routine-folders
Fetch routine folders
get-routine-folder
Fetch a routine folder
Environment variables
HEVY_API_KEYrequiredAPI key used to authenticate with the Hevy APIPackages
ghcr.io/rwestergren/hevy-mcp:0.1.6
ocitransport: streamable-http
Details
- Language
- TypeScript
- License
- MIT
- Released
- May 5, 2026
- Last commit
- May 5, 2026
- Registry name
- io.github.rwestergren/hevy-mcp-remote