rajdeepmondaldotcom/whoop-mcp-server

Your WHOOP shows you charts. It can't answer "should I train hard today" or "what actually hurts my recovery". This server can.
It connects your WHOOP data to Claude, ChatGPT, and any MCP client. You ask in plain English. It computes the answer from your own records and lets the AI explain it.
Runs on your machine. Read-only. The only network peer is api.prod.whoop.com. No telemetry. MIT.
What you need
- A WHOOP account. Any membership works.
- uv or pipx, to install one command line tool.
- An MCP client: Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, or ChatGPT.
One constraint to know before you start. WHOOP has no shared developer app, so during setup you create your own free one. It takes about two minutes of clicking, and it is the reason this is private by design: your tokens belong to your app, on your machine, and your health data never routes through anyone else's server. Including mine.
Set it up
Install the tool:
(pipx install whoop-mcp-server works the same.)
Then run the one command that does everything:
Here is what happens, in order, so nothing surprises you:
1. **Your WHOOP app.** The wizard opens WHOOP's developer dashboard and tells you exactly what to click: create a team, create an app, enable every scope including offline, set the redirect URL to exactly http://localhost:8765/callback. The form requires a privacy policy URL. Use this repo's: https://github.com/rajdeepmondaldotcom/whoop-mcp-server/blob/main/PRIVACY.md. Copy the Client ID and Secret, paste them into the terminal. They're stored locally with 0600 permissions.
2. **Authorize.** Your browser opens WHOOP's consent screen. Approve it. Tokens land in ~/.whoop-mcp and refresh themselves from then on. You never do this again.
3. **Proof.** The wizard makes a live API call and prints your actual latest recovery. If anything is misconfigured, you find out here, in the terminal, not later in a chat window.
4. **Your clients.** It detects Claude Desktop, Cursor, Windsurf, VS Code, and Claude Code, and writes their configs for you. Existing config is backed up before any edit. If Claude Desktop is running, the wizard asks to quit it first, because Desktop silently overwrites config edits made while it's open. Then it launches the configured command once and confirms the server answers. "Done" means verified, not hopeful.
Restart your client. Ask it: "How did I sleep last night?" Then ask the better question: "Give me the full picture of my health this quarter."
Two useful asides. If you want to see the tools work before connecting anything, whoop-mcp-server serve --demo serves 150 days of realistic generated data through the same pipeline. And if anything misbehaves later, whoop-mcp-server doctor names what's wrong and the fix.
What you can ask
24 tools cover every public user-readable endpoint in WHOOP's API, plus the analysis layer that turns records into answers.
| Ask | Tool behind it |
| --- | --- |
| "Give me the full picture of my health" | get_health_overview: status, trends, training load, records, and correlations in one call |
| "How am I doing today?" | get_daily_summary: recovery, sleep, strain, workouts for any day |
| "What actually affects my recovery?" | get_correlations: strain vs next-morning recovery, sleep vs recovery, with plain readings |
| "Am I overtraining?" | get_strain_trends: acute vs chronic load, per-sport breakdown |
| "Is my HRV improving?" | get_recovery_trends: direction, confidence, unusual days |
| "Show my overnight heart rate curve" | get_sleep_stream: minute-level HR and skin temp, lowest point and when; include_raw=true keeps WHOOP's untouched stream |
| "This month vs last month?" | compare_periods: every metric, improved or declined |