MCP server for the official Whoop API v2: cycles, recovery, sleep, workouts, and profile data
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Manual Client & Custom JSON ConfigExpand JSON ▾
No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for whoop-mcp-server, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.
Capabilities & Tool Schemas (10)
Inspect callable tools, capabilities, and parameters exposed to AI agents by Whoop MCP Server.
get_profileSingle object: `user_id`, `email`, `first_name`, `last_name
get_body_measurementSingle object: `height_meter`, `weight_kilogram`, `max_heart_rate
get_cyclesArray of cycle records — one per physiological day: `start`/`end`, `score_state`, and `score` with day `strain`, `kilojoule`, `average_heart_rate`, `max_heart_rate
get_latest_cycleSingle cycle record (the current/most recent day)
get_recoveriesArray of recovery records — one per sleep: `cycle_id`, `sleep_id`, and `score` with `recovery_score` (0–100), `resting_heart_rate`, `hrv_rmssd_milli`, `spo2_percentage`, `skin_temp_celsius
get_recovery_for_cycleSingle recovery record for that cycle
Documentation Overview
whoop-mcp-server
MCP server for the official Whoop API v2, written in Go. Exposes cycles, recovery, sleep, workouts, and profile data as MCP tools.
Tools
All tools return JSON. Record shapes are the unmodified Whoop API v2 objects, so every field the API exposes is available to the model.
| Tool | Inputs | Returns |
|---|---|---|
get_profile | — | Single object: user_id, email, first_name, last_name |
get_body_measurement | — | Single object: height_meter, weight_kilogram, max_heart_rate |
get_cycles | start_date, end_date, limit (all optional) | Array of cycle records — one per physiological day: start/end, score_state, and score with day strain, kilojoule, average_heart_rate, max_heart_rate |
get_latest_cycle | — | Single cycle record (the current/most recent day) |
get_recoveries | start_date, end_date, limit (all optional) | Array of recovery records — one per sleep: cycle_id, sleep_id, and score with recovery_score (0–100), resting_heart_rate, hrv_rmssd_milli, spo2_percentage, skin_temp_celsius |
get_recovery_for_cycle | cycle_id (required) | Single recovery record for that cycle |
get_sleep | start_date, end_date, limit (all optional) | Array of sleep records: start/end, nap flag, and score with per-stage durations (light/SWS/REM/awake, in ms), respiratory_rate, sleep_performance_percentage, sleep_efficiency_percentage, sleep-need breakdown |
get_workouts | start_date, end_date, limit (all optional) | Array of workout records: sport_name, start/end, and score with workout strain, heart rates, kilojoule, distance_meter, altitude_gain_meter, time-in-zone durations (zone_durations, ms per HR zone) |
get_average_strain | days (optional, default 7) | Computed aggregate: {days, cycles_counted, average_strain} |
check_auth_status | — | {authenticated: bool} plus the profile on success or an error string on failure |
Notes:
- Dates are
YYYY-MM-DD;end_dateis inclusive (internally mapped to the start of the next day, per the API's exclusiveendsemantics). - Collections are date-descending (most recent first) and paginated transparently — the server follows
next_tokenuntillimitrecords (default 25, max 100) are collected. - Scores are point-in-time per record, not time-series: one strain value per cycle, one recovery per sleep. For trends, fetch a range and let the model aggregate (or use
get_average_strainfor the built-in strain average). - A record's
score_statecan beSCORED,PENDING_SCORE, orUNSCORABLE—scoreis only present whenSCORED.
Setup
1. Create a Whoop developer app
At developer.whoop.com, create an app with:
- Redirect URI:
http://localhost:8719/callback - Scopes:
read:cycles,read:recovery,read:sleep,read:workout,read:profile,read:body_measurement,offline
Note the client ID and client secret.
2. Install
Homebrew:
Or download a prebuilt binary from Releases, or:
Or build from source:
3. Authorize (one time)
Opens a browser for the OAuth flow; the token is saved to
~/Library/Application Support/whoop-mcp/token.json (macOS) and refreshed
automatically thereafter (rotating refresh tokens).
4. Register with Claude Code
Or for Claude Desktop, in claude_desktop_config.json:
Example queries
- "What's my recovery score today?"
- "Show my sleep for the past week"
- "What's my average strain over the last 7 days?"
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
npm downloads
2.1k
Package downloads in the last 30 days.
Last commit
2mo ago
Most recent push to the default branch.
Tools exposed
10
Callable tools this server registers over MCP.
Directory activity
1 views
Config copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Whoop MCP Server
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/whoop-mcp-server)HTML Embed
<a href="https://allmcps.com/mcp/whoop-mcp-server"><img src="https://allmcps.com/api/badge/whoop-mcp-server?style=directory" alt="Whoop MCP Server on AllMCPs" /></a>