MCP server for WHOOP health data — recovery, sleep, workouts, cycles, and trends.
whoop-ai-mcp (MCP server)
This MCP server provides access to WHOOP health data covering recovery, sleep, workouts, cycles, and trends. It is described as an MCP server for WHOOP analytics, exposed under the name “io.github.shashankswe2020-ux/whoop” with the topic set including fitness tracking and integration materials.
🛠️ Key Features
Recovery data support
Sleep data support
Workouts data support
Cycles data support
Trends data support
🚀 Use Cases
Fetch and analyze WHOOP recovery metrics
Review sleep information for reporting or tracking
Summarize workouts and cycle-related data
Track trends across health and training signals
⚡ Developer Benefits
Targets WHOOP health data (recovery, sleep, workouts, cycles, trends)
Packaged as an npm package (“whoop-ai-mcp”)
Uses Node.js with a stated requirement of Node.js >= 20
⚠️ Limitations
Limited to the categories explicitly mentioned: recovery, sleep, workouts, cycles, and trends
whoop-ai-mcp is a read-only WHOOPMCP server for Claude, Gemini CLI, Cursor, VS Code, OpenClaw, Perplexity on macOS, and other MCP clients. Ask about your recovery, compare weeks of sleep, or check today against your own baseline, without exporting the data yourself. ChatGPT, Claude web/mobile, and the Grok xAI API require a remote deployment; see the client setup guide.
For Claude Code, Codex and VS Code/Copilot, run the registration command that setup prints. For Gemini CLI, Cursor and OpenClaw, merge the printed config; for Perplexity, paste the printed launch command into its local connector. Nothing is installed globally, and optional usage telemetry defaults to No.
These targets, including the claude alias for Desktop, require 1.1.0 or later. For a source build, use node dist/index.js setup --client=<target>.
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.
Claude web/mobile and ChatGPT quick setup
Run setup --client=claude-web or setup --client=chatgpt with either implementation
to print remote deployment and connector instructions. These are guidance-only
targets, not one-click hosting: provide a public HTTPS /mcp endpoint, complete
WHOOP authorization on the host, and configure compatible connector OAuth.
Availability depends on the client account/workspace. setup --client=grok prints
an xAI API MCP tool example; consumer Grok chat integration is not verified.
No remote credentials are collected and no client connection is tested.
Prefer a native binary?
The Rust implementation offers the same client targets and limitations without a Node.js runtime for the server. It needs Rust 1.88 or later:
The additional Rust targets require 0.2.0 or later. For a source build,
use cargo run -- setup --client=<target> in the Rust checkout.
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.
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_claim recomputes a number your assistant told you.
Open a chart-first local dashboard (open_performance_dashboard) on 127.0.0.1 with Today, Session, Training, HYROX, Triathlon, Readiness and Audit views. Dark/light themes, local fonts, and review-before-save controls are included.
Screenshots use synthetic sample data.
New in 1.0.2: the chart-first dashboard
Ask your assistant to "Open my performance dashboard" to launch it locally.
The design from the latest main-branch redesign is now part of the working
dashboard, not just a prototype. Dark is the default, with a Light/Dark toggle
that preserves unsaved forms. Session remains the default view.
Today: recovery ring and five weeks of recovery, HRV, resting HR and sleep
stages on one timeline with a shared crosshair. Missing days remain gaps;
historical bands describe your visible data, not medical norms.
Training: WHOOP zone minutes by UTC week, including empty weeks, workout
strain/duration bubbles and fitness/fatigue/form charts. Local corrections apply.
Session and Readiness: recorded-segment and five-component rings, summary
HR charts and evidence. No invented continuous HR traces or HYROX station splits.
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.
Today view with synthetic sample data. WHOOP recovery is not a race-readiness verdict; local workout corrections apply to race views, not this overview.
The race log, workout corrections and dashboard are available only when the server runs locally (stdio). Details: race performance tools and local data.
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.