Hevy2whoop

io.github.mselcukozturkPublished by GitHub account mselcukozturkv1.1.0Updated Nov 6, 2026

Copy Hevy strength workouts into WHOOP Strength Trainer sets with reps and weight

VerifiedSTDIODesktop onlyLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

Copies Hevy strength workouts into WHOOP Strength Trainer, with reps and weight, via a preview-then-write sync and an exercise ID catalog.

What you can do
  • Sync Hevy workouts into WHOOP Strength Trainer: preview the latest workout or a date range, then write it when explicitly enabled
  • Report unmapped and skipped exercises, and skip workouts already present in WHOOP
  • List WHOOP Strength Trainer exercise IDs and names, optionally filtered by search text, to build the exercise mapping
When to use it
Use it if you log strength training in Hevy and want those sets to appear in WHOOP Strength Trainer without retyping them in the WHOOP app, either on request through an assistant or from a scheduled job.
Requirements
Runs locally over stdio with Node.js 24 or later. Needs a Hevy Pro account and its API key in HEVY_API_KEY, a WHOOP account, and the separate totem MCP server installed and signed in on the PATH (its WHOOP sign-in expires after about 30 days). Optionally set HEVY2WHOOP_MAPPING to a custom mapping file.
Before you install
Writing to WHOOP goes through totem, which uses WHOOP's private iOS API; the project states WHOOP's terms do not permit this and it can change without notice, so use your own account at your own risk. The sync tool writes to WHOOP only when called with write: true, but an assistant can pass that flag, so review previews first. The Hevy API key is a secret; the project says it and WHOOP tokens go only to Hevy and WHOOP. Bundled exercise mappings are often approximate.

Installation

In SourceWeft

  1. Open Hevy2whoop in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

bash
git clone https://github.com/mselcukozturk/hevy2whoop.gitcd hevy2whoopnpm install -g @thebriangao/totemtotem auth                      # sign in to WHOOP onceexport 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

bash
node hevy2whoop.mjs sync                                      # preview the latest workoutnode hevy2whoop.mjs sync --write                              # write it to WHOOPnode hevy2whoop.mjs sync --from 2026-09-01 --to 2026-09-30    # preview a date rangenode hevy2whoop.mjs sync --from 2026-09-01 --to 2026-09-30 --writenode 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:

ToolArgumentsEffect
hevy2whoop_syncfrom, to (YYYY-MM-DD, optional), write (default false)Same as sync. Returns one result per workout: preview, written, already_in_whoop, nothing_to_write or error, with unmapped and skipped exercises.
hevy2whoop_catalogsearch (optional)Same as catalog.

The sync tool writes to WHOOP only when it is called with write: true.

Claude Code:

bash
claude mcp add hevy2whoop -e HEVY_API_KEY=your-hevy-api-key -- node /path/to/hevy2whoop/hevy2whoop.mjs mcp

After the npm release, no local clone is needed:

bash
claude mcp add hevy2whoop -e HEVY_API_KEY=your-hevy-api-key -- npx -y hevy2whoop mcp

Claude Desktop, Cursor and other clients (claude_desktop_config.json or the client's MCP settings):

json
{  "mcpServers": {    "hevy2whoop": {      "command": "node",      "args": ["/path/to/hevy2whoop/hevy2whoop.mjs", "mcp"],      "env": { "HEVY_API_KEY": "your-hevy-api-key" }    }  }}

totem must be on the PATH the client gives to the server. If the client cannot find it, add "PATH" to env.

Exercise mapping

mapping.json is keyed by the Hevy exercise_template_id:

json
"DE68C825": {  "hevy": "Single Arm Lateral Raise (Cable)",  "whoop": ["LATERALRAISELEFT_PULLEYMACHINE", "LATERALRAISERIGHT_PULLEYMACHINE"],  "approximate": false,  "note": "the catalog has no two-sided cable lateral raise; every set is written to both sides"}
FieldMeaning
hevyHevy exercise title, for readers of the file
whoopWHOOP exercise IDs. Each working set is written to every ID in the list. An empty list means the exercise is never logged.
approximatetrue when the WHOOP catalog has no exact equivalent and the closest exercise was chosen
noteReason for an approximate or unusual choice

The WHOOP catalog has 372 exercises and Hevy has many more, so a number of entries are approximate. Check the notes and change entries you disagree with.

Adding an exercise

  1. Run sync. Unmapped exercises are listed with their template ID.
  2. Find the WHOOP ID with node hevy2whoop.mjs catalog <search>.
  3. Add an entry to your own mapping file (below), or to mapping.json if the exercise is one of Hevy's built-in exercises and you want to contribute it.

Your own mapping file

Set HEVY2WHOOP_MAPPING to the path of a JSON file in the same format. Its entries are added to mapping.json, and an entry with the same template ID replaces the bundled one. Use it for your custom Hevy exercises and for choices that differ from the bundled mapping; updating the repository then never conflicts with your changes.

bash
export HEVY2WHOOP_MAPPING=~/.config/hevy2whoop/mapping.json

Custom Hevy exercises have UUID template IDs (for example 0b7e5c2a-4d1f-...). They exist only in your account, so keep them in your own file and do not submit them.

Contributing

Pull requests that add or correct entries for Hevy's built-in exercises (8-character template IDs) are welcome. Please set approximate and explain the choice in note when the match is not exact.

Limitations

  • WHOOP stores a duration for each set; Hevy does not. The workout duration is divided equally across the working sets.
  • Drop sets and failure sets are written as ordinary sets.
  • Only workouts WHOOP records as Strength Trainer activities count as already logged. A separate activity recorded by the strap during the same session is left untouched.
  • For one-sided exercises, Hevy counts reps per side, while some WHOOP entries may count the total. See the notes in mapping.json.

Testing

bash
node test/e2e.mjs

Runs the command-line tool and the MCP server end to end against a fake Hevy API and a fake totem server, covering the cases in docs/failure-scenarios.md, and writes the result to artifacts/e2e-result.json. No real account is used.

Credits

  • totem by Brian Gao (MIT) does all communication with WHOOP.
  • hevy2garmin does the same job for Garmin Connect and was a reference for this project.

License

MIT

Source: README.md at commit bccf837

Tools

2

hevy2whoop_sync

Copy Hevy strength workouts into WHOOP Strength Trainer. Without from/to, takes the latest Hevy workout. Without write: true, only previews. With write: true, WRITES the workouts to WHOOP; workouts already in WHOOP are not written again. Reports exercises that have no entry in the exercise mapping.

Parameterstofromwrite

hevy2whoop_catalog

List WHOOP Strength Trainer exercise IDs and names, optionally filtered by a search text. Use it to find IDs for the exercise mapping.

Parameterssearch

Version history

1
  1. v1.1.0LatestNov 5, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts