whoop-ai-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@whoop-ai-mcpSummarize my sleep and recovery this week."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
whoop-ai-mcp is a read-only WHOOP MCP server for Claude Desktop, Claude Code, Codex and GitHub Copilot. Ask about your recovery, compare weeks of sleep, or check today against your own baseline, without exporting the data yourself.
npx -y whoop-ai-mcp@latest setup --client=claude-desktopAsk your WHOOP data anything
Ask | You get |
"How am I doing today?" | Recovery, primary sleep, strain and your latest workout, with gaps flagged where data is missing |
"Is my HRV unusual for me?" | Your personal baseline: distribution, percentiles and how many days it's based on |
"How did my sleep change this month?" | Trends, period-to-period comparisons, sleep debt and consistency |
"Give me my weekly health review." | Recovery, sleep and training in one summary |
Statistics describe your recorded history. They aren't medical diagnoses or predictions.
Related MCP server: whoop-ai-mcp
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.
Assistant
Command
Claude Desktop
npx -y whoop-ai-mcp@latest setup --client=claude-desktopClaude Code
npx -y whoop-ai-mcp@latest setup --client=claude-codeCodex
npx -y whoop-ai-mcp@latest setup --client=codexGitHub Copilot
npx -y whoop-ai-mcp@latest setup --client=copilotFor 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-desktopHow 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.
The race log, workout corrections and dashboard are available only when the server runs locally (stdio). Details: race performance tools and local data.
Group | Tools |
Today and baselines |
|
Trends and reviews |
|
Records |
|
Profile |
|
HYROX and triathlon |
|
Local only: race log, corrections, dashboard |
|
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
Guide | What's in it |
Assistants, manual configuration, environment variables and WHOOP authorization | |
Every tool and its parameters, date expressions, resources, prompts and caching | |
Structured results, aggregate mode and what your assistant provider receives | |
Consent, opting out, what's collected and how long it's kept | |
Local diagnostics, common errors and MCP Inspector | |
Docker, cloud hosting and remote connector OAuth | |
Tests, project structure and release workflow | |
Ecosystem research and the video walkthrough |
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.
This server cannot be deployed
Maintenance
Related MCP Connectors
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Your WHOOP data in the assistant, read-only: recovery, sleep, strain, workouts, cycles and body meas
Garmin data in Claude & ChatGPT via the Garmin Health API. OAuth sign-in, no password sharing.
- SomviaOAuthapp.somvia
Apple Health training load, recovery, HRV and workout detail for Claude, ChatGPT and any MCP client.
Related MCP Servers
- FlicenseNot gradedqualityAmaintenanceEnables read-only access to your WHOOP recovery, sleep, HRV, strain, workout and body-measurement data from Claude Desktop, Claude Code, Codex or GitHub Copilot, so you can ask natural-language questions about today's status, personal baselines, trends, period comparisons and sleep debt.7 npm-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to read a user's WHOOP recovery, sleep, HRV, strain, and workout history through a local, read-only server with tools for today's status, personal baselines, sleep debt, trends, and period comparisons. It supports Claude Desktop, Claude Code, Codex, and GitHub Copilot, letting users ask natural-language questions about their health data without exporting it themselves.7 npm-
- FlicenseNot gradedqualityAmaintenanceEnables users to query their own WHOOP recovery, sleep, HRV, strain and workout history in natural language through read-only tools, baselines and period comparisons inside Claude, Codex and GitHub Copilot.7 npm-
- FlicenseNot gradedqualityAmaintenanceProvides read-only access to WHOOP recovery, sleep, HRV, strain, and workout data so assistants like Claude, Codex, and GitHub Copilot can answer questions about personal health trends, baselines, and period comparisons. It runs locally with no hosted relay and never modifies anything in the user's WHOOP account.7 npm-