by chrisdoc
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.
# Add to your Claude Code skills
git clone https://github.com/chrisdoc/hevy-mcpA Model Context Protocol (MCP) server implementation that interfaces with the Hevy fitness tracking app and its API. This server enables AI assistants to access and manage workout data, routines, exercise templates, and more through the Hevy API (requires PRO subscription).
Note: HTTP transport and Docker images are deprecated. The server runs via stdio transport (e.g.,
npx hevy-mcp). Legacy GHCR images remain available but are no longer maintained.
Pick the workflow that fits your setup:
| Scenario | Command | Requirements |
| --- | --- | --- |
| One-off stdio run | HEVY_API_KEY=sk_live... npx -y hevy-mcp | Node.js ≥ 20, Hevy API key |
| Local development | pnpm install && pnpm run dev | .env with HEVY_API_KEY, pnpm via Corepack |
.nvmrc to match CI)You can launch the server directly without cloning:
HEVY_API_KEY=your_hevy_api_key_here npx -y hevy-mcp
# Clone the repository
git clone https://github.com/chrisdoc/hevy-mcp.git
cd hevy-mcp
# Install dependencies
corepack use pnpm@10.22.0
pnpm install
# Create .env and add your keys (never commit real keys)
cp .env.sample .env
# Edit .env and add your HEVY_API_KEY.
To use this MCP server with Cursor, add/merge this server entry under
"mcpServers" in ~/.cursor/mcp.json:
{
"hevy-mcp": {
"command": "npx",
"args": ["-y", "hevy-mcp"],
"env": {
"HEVY_API_KEY": "your-api-key-here"
}
}
}
Make sure to replace your-api-key-here with your actual Hevy API key.
If your mcp.json already contains other servers, do not replace the whole
file—merge the "hevy-mcp" entry into your existing "mcpServers" object.
The "hevy-mcp" key name is arbitrary. If you already have an existing config
using a different name (for example "hevy-mcp-server"), you can keep it.
If you already have an existing "mcpServers" object, merge the "hevy-mcp"
entry into it without removing other servers.
{
"mcpServers": {
"hevy-mcp": {
"command": "npx",
"args": ["-y", "hevy-mcp"],
"env": {
"HEVY_API_...