Personal analytics
Your history, with the gaps made visible.
Downloads since first publication, through . Stars checked . Refreshed daily.
Downloads may include automated installs.
WHOOP MCP server · Read-only health data
Your recovery, sleep and strain. In your AI assistant.
Open-source software for your existing WHOOP. Not a device.
get_recovery_collection
Recovery scores, HRV and resting heart rate, matched to the right day.
get_sleep_debt
Sleep stages, naps and nightly deficits, kept separate from WHOOP's standing debt.
get_workout_collection
Daily strain and every workout, with weekly summaries and trends.
get_baselines
Personal baselines from your own history. Compared with you, not with a population.
16 tools that read and never write. Nothing is written back to WHOOP.
OAuth with PKCE. Tokens stay on the server host with 0600 permissions.
Works with the assistant you already use, over stdio or Streamable HTTP.2
npx -y whoop-ai-mcp@latest setupNode.js 20+ with npm. No global installation needed.
Client setup16 read-only tools · 9 race tools · 4 resources · 5 prompts in standard mode
Your history, with the gaps made visible.
Share summaries. Hold back the records.
All 16 read-only tools, including raw records and the latest observations.
Tools, resources and prompts. Drop it into Claude Desktop or host your own.
Usage counts, only with your permission.
Setup asks before sending usage counts. Declining does not affect WHOOP access.
Personal analytics
get_baselines
Compares HRV, resting heart rate, sleep and recovery with your own history. Reports insufficient data when history is too short, rather than guessing a normal range.
get_sleep_debt
Separates observed nightly deficits from WHOOP's standing debt. Uses scored asleep stages and accounts for naps.
get_today
Matches recovery with the current cycle and primary sleep. Pending or invalid sleep never borrows an older score. Missing stays distinct from zero.
WHOOP_MCP_PRIVACY_MODE=aggregate
Five summary and analytics tools. No record arrays, identity fields or exact activity timestamps. Aggregates are still sensitive data.1
Aggregates remain sensitive data. Health results reach your assistant provider.
Sixteen read-only tools cover raw records, current health context and personal statistics. Missing data is labeled, never filled in.
Check your configuration offline with whoop-ai-mcp doctor --json. · Changelog
New in 1.0.2 · Local performance dashboard
get_hyrox_session_report
Stitches runs and ergs into one session with transitions, time in zone and rule-based insights. A possible sim stays unconfirmed until you confirm it.
get_race_readiness
Recovery, training form, specificity, sleep debt and taper, each with its value, method, window and records used. No opaque score.
audit_performance_data · verify_claim
Implausible paces, overlaps and indoor distances are flagged, never excluded automatically. verify_claim recomputes a number your assistant told you.
open_performance_dashboard
Today, Session, Training, HYROX, Triathlon, Readiness and Audit on 127.0.0.1. Token-protected, no third-party assets, with locally bundled fonts and a Light/Dark toggle. It stops after 30 idle minutes. Ask your assistant to open your performance dashboard.
Vitals history · Training charts
Five-week recovery, HRV, resting HR and sleep-stage history on one timeline. Training adds recorded zone minutes, workout bubbles and fitness/fatigue/form. Missing data stays missing. Filters survive view changes; presets use completed UTC days. Refresh reports view load time, not WHOOP sync time; reads may use cached data.
annotate_workout · log_race_result
Inspect workout corrections and race results, then edit, cancel or confirm. Failed saves preserve your entries. Local workout corrections apply to race views, not the daily overview.
Node.js local stdio only. Edits stay in local files, never in WHOOP.
The chart-first dashboard is here: recovery and readiness rings, five-week vitals, session charts and a new Training view. Dark by default, with a Light/Dark toggle. Evidence and review-before-save stay built in.
Nine race tools; race results and workout corrections are saved to local files with an audit log, never to WHOOP. Available in the Node.js server's local stdio mode, not aggregate mode. Charts do not infer continuous HR traces or official HYROX station splits. · Race tools · 1.0.2 release notes
Consent-based telemetry
Setup asks before sharing command, tool or template usage. Existing clients are never silently opted in.
Desktop setup stores your choice in its config. Pass --telemetry=off to decline explicitly. No installation ID is created.
Events carry versions, an allowlisted name, its kind and outcome. No arguments, results, chat text or identifiers.
DO_NOT_TRACK=1 and aggregate mode suppress sending even after opt-in. 500 ms deadline, no retry queue.
The collector stores daily counts, not raw events. Users and installations are not measured.
Consent is not an anonymity guarantee: networks can see IP addresses and arrival times. This page loads no telemetry client. · Consent and retention
Setup
Run setup
npx -y whoop-ai-mcp@latest setup --client=claude-desktopMerges the server into Claude Desktop with a backup. Fully quit and reopen Desktop, then authorize WHOOP on first start.
Remote targets: guidance only. Perplexity: macOS. OpenClaw: Gateway host.
Keep generated credentials private. Never disable authentication for remote access.
Choose Node.js or the native Rust binary, then pick your assistant. Local setup uses your WHOOP Developer App credentials. Remote targets print guidance only; credentials stay on your server host.
npm 1.1.0 · Rust 0.2.0 · Optional telemetry defaults to No.
Remote setup does not deploy or verify a connection. ChatGPT and Claude web/mobile need compatible OAuth and account/workspace access. The server supports one static OAuth client with exact callback allowlists, not every client's registration flow. Never disable authentication to work around incompatibilities. Remote deployment guide.
Perplexity local setup requires macOS and its helper; OpenClaw requires native MCP support and runs the server on its Gateway host. Generated configs contain credentials: preserve existing settings, keep files private and out of version control. Printed shell commands use POSIX syntax.
http://localhost:3000/callback