hevy-coach
MCP server that connects Claude to the Hevy fitness app, enabling AI-driven personalized strength coaching by reading lifting history and programming workouts.
README
claude-hevy-coach
Claude as your personal strength coach, wired into the Hevy app.
Say "coach me" → Claude reads your real lifting history, checks how your last programmed workout actually went, asks how you're feeling, designs your next session, and writes it into Hevy as a routine. At the gym you just open Hevy and tap Start.
What you need
- Hevy Pro — the Hevy API key requires it
- Node.js 20+ — https://nodejs.org
- Claude Code (Claude Desktop works too — see below)
Setup (~3 minutes)
1. Get the code and install:
git clone https://github.com/jmilinovich/claude-hevy-coach.git
cd claude-hevy-coach
npm install
2. Add your Hevy API key:
cp .env.example .env
Get your key at https://hevy.com/settings?developer and paste it into .env
so it reads:
HEVY_API_KEY=your-key-here
3. Check it works:
npm run doctor
You want: ✅ Hevy API key works.
4. Start coaching:
claude
When Claude Code asks to use the hevy-coach MCP server, approve it. Then
just say:
coach me
That's it. The first time, Claude interviews you for a couple of minutes (goals, schedule, equipment, injuries, your working weights) and saves your profile. Every time after: it recaps your last session, programs the next one, shows you the card, and — once you say go — writes it to Hevy. Open the Hevy app and tap Start on the 🤖 routine.
Day to day
Things you can say:
- "coach me" / "program my next workout"
- "push day, 45 minutes, easy on the shoulders"
- "how did my last session go?"
- "how's my bench trending?"
- "I tweaked my knee — work around it" (it'll update your profile too)
Your training philosophy lives in COACH.md — edit it any time,
the coach reads it fresh before every session. Your block position, baseline
loads, and prescription history live in state/ (local only, not committed).
Using Claude Desktop instead
Do your first conversation in Claude Code (the setup interview writes your
profile into COACH.md, which Claude Desktop can't edit). After that, Desktop
works great for day-to-day coaching.
Add this to claude_desktop_config.json (Settings → Developer → Edit Config),
replacing both paths with wherever you cloned the repo:
{
"mcpServers": {
"hevy-coach": {
"command": "/ABSOLUTE/PATH/TO/claude-hevy-coach/node_modules/.bin/tsx",
"args": ["/ABSOLUTE/PATH/TO/claude-hevy-coach/src/mcp/server.ts"]
}
}
}
(That's the repo's own tsx binary — Desktop launches servers from outside the
repo folder, so a bare npx tsx wouldn't find it.) Restart Claude Desktop,
then tell it: "You're my strength coach — start with the
get_programming_brief tool." Claude Desktop doesn't read CLAUDE.md, so that
first nudge points it at the brief, which carries the coaching instructions.
One limitation: profile updates ("my gym has no cables now") need COACH.md
edited — do those in Claude Code, or edit the file yourself.
How it works (60 seconds)
- The Hevy API has no scheduler and no deletes — the only way to hand you a
planned workout is to overwrite a routine. So the coach maintains exactly
one routine, marked
🤖(the default marker), rewritten in place each session. COACH.mdis the doctrine — your goals, split, equipment, injuries, and effort rules, in plain English. It's injected into every programming brief.- The engine derives everything from your history — which day is due,
whether it's a deload, what loads to prescribe. The only stored state is a
tiny block seed, your baseline loads, and an append-only log of what was
prescribed (
state/, gitignored). - The learning loop: Hevy records what you did; the coach records what it prescribed. Before each session it diffs the two — held / heavier / lighter / faded / skipped — and adjusts.
- Workout writes are previewed first.
commit_workoutvalidates against your live exercise catalog, shows you the card, and only writes after you approve (creating a custom exercise also waits for your explicit OK). Everything runs locally; the only network calls are toapi.hevyapp.com.
Troubleshooting
| Symptom | Fix |
|---|---|
npm run doctor says key rejected |
Re-copy the key from https://hevy.com/settings?developer; make sure your Hevy Pro subscription is active |
| Claude says it has no hevy-coach tools | Run /mcp in Claude Code and approve the server; make sure npm install ran; restart Claude Code in this folder |
npx tsx not found |
Run npm install in the repo folder first |
| Coach programs movements your gym doesn't have | Tell it — it updates COACH.md and won't do it again |
| On Windows the server won't connect | Edit .mcp.json to {"command": "cmd", "args": ["/c", "npx", "tsx", "src/mcp/server.ts"]} (native Windows needs the cmd /c wrapper; WSL doesn't) |
| You want a fresh start | Delete the state/ folder contents and run git checkout COACH.md (restores the template) — the coach re-interviews you next time |
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.