hevy2whoop

Copies strength workouts you log in Hevy into WHOOP Strength Trainer: every exercise and every working set, with reps and weight. WHOOP has no Hevy integration, so without this tool the sets have to be entered in the WHOOP app by hand after each session.

hevy2whoop handles the Hevy side and the exercise mapping. Writing to WHOOP is done by totem, an MCP server by Brian Gao.

Read before use. This project is not affiliated with Hevy or WHOOP. WHOOP does not offer a public API for writing Strength Trainer workouts. totem uses WHOOP's private iOS API, which WHOOP's terms do not permit and which can change without notice. Use it at your own risk and with your own account only. hevy2whoop runs on your computer; your Hevy key and WHOOP tokens are sent only to Hevy and WHOOP.

Setting up with an AI agent

Give your agent (Claude Code, Codex, Cursor, ...) this message:

Install hevy2whoop for me by following https://raw.githubusercontent.com/mselcukozturk/hevy2whoop/main/AGENT_INSTALLATION.md

AGENT_INSTALLATION.md takes the agent through each step with a check, maps your unmapped exercises with you, and registers the MCP server in your client. It tells the agent to leave the WHOOP sign-in to you and to write to WHOOP only after you approve a preview.

What it does

1. Reads your latest Hevy workout, or every workout in a date range, from the official Hevy API.
2. Converts each exercise to a WHOOP exercise ID using mapping.json. Warm-up sets are left out. Exercises without a mapping entry are reported and not written.
3. Checks whether WHOOP already has a Strength Trainer activity that starts and ends within 2 minutes of the Hevy workout. If so, the workout is not written again, so repeated runs are safe.
4. Shows a preview. With --write, it logs the workout to WHOOP.

It runs as a command-line tool, or as an MCP server so that Claude or another MCP client can run the sync on request ("copy yesterday's workout to WHOOP").

Requirements

• Node.js 24 or later
• Hevy Pro (the Hevy API key is available only on Pro): hevy.com/settings?developer
• A WHOOP account
• totem, installed and signed in

Installation

git clone https://github.com/mselcukozturk/hevy2whoop.git
cd hevy2whoop
npm install -g @thebriangao/totem
totem auth                      # sign in to WHOOP once
export HEVY_API_KEY=your-hevy-api-key

hevy2whoop has no npm dependencies. It starts totem start from your PATH. totem's WHOOP sign-in lasts about 30 days; when it expires, run totem auth again.

Usage

node hevy2whoop.mjs sync                                      # preview the latest workout
node hevy2whoop.mjs sync --write                              # write it to WHOOP
node hevy2whoop.mjs sync --from 2026-09-01 --to 2026-09-30    # preview a date range
node hevy2whoop.mjs sync --from 2026-09-01 --to 2026-09-30 --write
node hevy2whoop.mjs catalog "lateral raise"                   # find WHOOP exercise IDs

Dates are in your local time zone and both ends are included. Example output:

2026-09-06 13:34–14:27  Upper Body
  unmapped: Wide Grip Row (template 0b7e5c2a-4d1f-4e8a-9c3b-6f2a1d8e7b90)
  skipped by mapping: Warm Up
  preview: would write 10 exercises, 20 sets (run with --write to write)

To sync automatically, run node hevy2whoop.mjs sync --write from cron or a systemd timer some time after your workout ends.

MCP server

node hevy2whoop.mjs mcp runs an MCP server over stdio with two tools:

... View full README on GitHub