npx -y whoop-ai-mcp@latest setup --client=claude-desktop
Ask your WHOOP data anything
Statistics describe your recorded history. They aren't medical diagnoses or predictions.
Quickstart
You need: Node.js 20 or later, an active WHOOP membership, and a WHOOP Developer App with the redirect URL http://localhost:3000/callback.
-
Set up. Run the command for your assistant and enter your developer app's client ID and secret when asked.
For Claude Code, Codex and Copilot, run the registration command that setup prints. Nothing is installed globally, and optional usage telemetry defaults to No.
-
Authorize. Fully quit and reopen your assistant. The first time the server starts, WHOOP opens in your browser so you can approve access.
-
Ask. Try "Summarize my sleep and recovery this week."
Need manual configuration, environment variables or a remote deployment? See the full setup guide.
The Rust implementation supports the same four assistants without a Node.js runtime. It needs Rust 1.88 or later:
cargo install whoop-mcp
whoop-mcp setup --client=claude-desktop
How it works
- Read-only. The server has no tools that create, change or delete anything in your WHOOP account. Race results and workout corrections are saved only to local files, with an audit log.
- Local by default. The server runs on your machine. No hosted relay is involved.
- Your assistant sees the results. Health data reaches the assistant provider you use, the same as anything else you share in that chat.
- Aggregate mode limits the server to five summary tools and hides per-record data. It reduces what's shared, but it isn't anonymization.
- Telemetry is off unless you opt in. It never includes health data or chat text.
Details: data handling and telemetry controls.
What's included
In standard mode, the server provides 16 read-only tools, 4 resources and 5 prompt templates, plus 9 HYROX and triathlon tools. Support for resources, prompts and remote connections depends on your assistant.
HYROX and triathlon tracking
Ask "How did yesterday's HYROX sim go?" or "Am I ready for my triathlon in two weeks?" The race tools:
- Rebuild a HYROX session from WHOOP's back-to-back workouts: segment timeline, transition time, time in zone and rule-based insights.
- Track weekly running and HYROX load, swim/bike/run balance and bricks, plus logged races with station and leg splits and PRs.
- Give a readiness band from recovery, training form, specificity, sleep debt and taper. Every component shows its evidence; there's no opaque score.
- Let you audit the numbers: suspect workouts are flagged, you can relabel or exclude workouts, every change is logged, and
verify_claimrecomputes a number your assistant told you. - Open a local dashboard (
open_performance_dashboard) on127.0.0.1with daily overview, session, HYROX, triathlon, readiness and audit views. Review corrections and race results before confirming a local save.
Ask your assistant to "Open my performance dashboard" to launch it locally. The Today tab shows recovery, HRV, resting heart rate, primary sleep, cycle strain and the latest workout, with evidence and explicit missing-data states. Session remains the default view.
- Review before saving. Inspect workout corrections and race results, then edit, cancel or confirm. Failed saves preserve your entries.
- Keep your context. Filters survive switching views; last-7-day and last-28-day presets use completed UTC days.
- Refresh honestly. Refresh and retry controls report when a view loaded, not when WHOOP synced. Reads may use cached data. The race log, workout corrections and dashboard are available only when the server runs locally (stdio). Details: race performance tools and local data.
Prompt templates: weekly_health_review, sleep_analysis, recovery_trend, workout_recap, health_check
Parameters, date expressions, resources and caching are in the tool reference.
Documentation
What changed recently? See the changelog or the latest release.
Feedback and contributing
Something not working, or a question you wish you could ask? Use the buttons above. Each opens a short form that asks for the details needed to help. Issues are public, so never include credentials or health records; security problems go through the security policy instead.
Want to contribute code? Read the contributing guide. Everyone taking part follows the Code of Conduct.
If whoop-ai-mcp is useful to you, a GitHub star helps other people find it, and you can buy me a coffee to support development.
License
MIT. This is an unofficial project and isn't affiliated with WHOOP. A WHOOP membership and API access are separate from this package.