Home

whoopmcp

A read-only MCP server for the WHOOP API v2: recovery, sleep, strain, cycles and workouts, plus server-side trends, correlations and period comparisons — from Claude Desktop, Claude Code, Cursor, or any other MCP client.

Terminal demo

Pages

Installation — clone, install, register the WHOOP app, wire up an MCP client, verify with whoopmcp doctor.
Usage Patterns — the four ways people actually run this: live local analysis, the persistent local store, hosted multi-member mode, and the operator command set.

The short version

git clone https://github.com/kurok/whoopmcp && cd whoopmcp
python3.13 -m venv .venv && .venv/bin/pip install -e .
export WHOOP_CLIENT_ID=... WHOOP_CLIENT_SECRET=... WHOOP_REDIRECT_URI=https://...
.venv/bin/whoopmcp doctor     # three honest sentences about your setup
.venv/bin/whoopmcp login      # OAuth in the terminal, token stored locally

Then point your MCP client at .venv/bin/whoopmcp and ask it how your recovery trended last month.

Ground rules

Read-only against WHOOP. No MCP tool can mutate your WHOOP account; the only mutating endpoint WHOOP exposes is reachable solely from the operator-run whoopmcp delete-member CLI, never from a model.
Local-first. In default local mode nothing but your OAuth token touches disk. The persistent store is opt-in (WHOOPMCP_CACHE=true).
Not a medical device. It reports numbers and the sample size behind them, never advice or diagnoses.

Reference docs in the repo: SETUP (from-scratch walkthrough), PRIVACY, SECURITY, THREAT-MODEL.

Navigation Menu