WHOOP has an API, not a connector
WHOOP’s developer platform documents OAuth 2.0, webhooks and six read scopes. What it does not document anywhere is an MCP server, and WHOOP does not appear in the built-in connector directory of either Claude or ChatGPT. There is no WHOOP-built way to point an assistant at your account.
That gap explains why the question is confusing. WHOOP’s API is open to anyone willing to register a developer app, so connectors do exist. They are simply not WHOOP’s. Search for a way to connect the two and you will find a dozen community MCP servers, several of them competently built. Whether you should use one is a separate question, and it depends on what each route actually carries.
ChatGPT reaches WHOOP through Apple Health
This is the route that answers the ChatGPT half of the question, and it does not involve WHOOP building anything. WHOOP writes to Apple Health, ChatGPT's Health feature reads Apple Health, and the data arrives that way.
In the WHOOP app, open More, then App Settings, then Integrations, and select Apple Health. Choose the data you want to share and allow it. Then open Health from the ChatGPT sidebar, choose Connect Health and pick Apple Health.
Two limits decide whether this is any use to you. OpenAI documents Health as available to logged-in Free, Go, Plus and Pro accounts in the United States, aged 18 or over, and connecting Apple Health requires an iPhone. What arrives is also whatever WHOOP writes into Apple Health rather than everything in your WHOOP account: OpenAI notes that some proprietary scores may not transfer, so check whether Recovery and Strain actually appear before planning around them.
Claude has no equivalent of this. For Claude, the route below is still the only official one.
How to connect WHOOP to Claude through Strava
Every hop in this route is documented by the company that owns it, which is the main argument for using it. WHOOP publishes cardio activities to Strava, and Strava runs its own connector for Claude. You need a Strava subscription for the second half to work, and this particular route ends at Claude: Strava does not document a ChatGPT setup.
1. Connect WHOOP to Strava
In the WHOOP app, open More → App Settings → Integrations on iOS, or Account & Settings → Integrations on Android. Select Strava, authorise it, and choose which activity types export. You can also pick how WHOOP data is drawn on the Strava activity: heart-rate graph, strain view or training-state view.
If you get a 404 at this step, it is usually because the account has not finished WHOOP’s initial four-day calibration and unlocked Strain Target. The integration will not authorise before then.
2. Add the Strava connector in Claude
In Claude, go to Customize → Connectors, click + to add one, search for Strava and authorise your account. In Claude Code the equivalent is claude mcp add --transport http strava-mcp https://mcp.strava.com/mcp. The connector is a Strava subscriber feature and has been rolling out since 1 June 2026, so if you subscribe and still cannot see it, Strava’s position is that access is on its way.
3. Test it with something narrow
Ask for one specific thing you can check yourself: last Tuesday’s run, its distance and its average heart rate. A vague opening question makes it hard to tell a working connector apart from an assistant that is guessing.
What arrives, and what stays behind
For each activity it posts, WHOOP sends Strava the activity type, elapsed time, calories, heart rate, activity strain, a recovery score, and GPS if Track Route was switched on. WHOOP excludes WHOOP Age, Pace of Aging, ECG and blood-pressure insights.
The bigger limit is structural rather than a list of exclusions. Only activities post to Strava, and recovery is not an activity type Strava supports, so sleep, the daily recovery score and the HRV trend have no route at all. A rest day produces nothing. That is the awkward part of the official route: sleep and recovery are what most people wear a WHOOP for, and they are the parts that do not travel.
Two smaller details matter in practice. WHOOP will not re-export an activity that reached it from Strava through Apple Health or Google Health Connect, which prevents duplicates if you also wear another watch. Unclassified activities, the ones left as “Activity”, are not posted at all until you give them a type.
None of this is a gap Athmex fills. Athmex holds a different layer: your goals, races, thresholds and injuries. Getting last week’s sessions in front of an assistant is a separate problem from telling it what those sessions were for.
The community servers, and what they ask of you
If you searched for this, you have already seen them: WHOOP MCP servers on GitHub, and a few hosted as products. They reach much more of your account than the Strava route does, because WHOOP’s API exposes recovery, sleep and cycles directly.
The cost is in the setup. To run one you register your own app in WHOOP’s Developer Dashboard, which issues a Client ID and a Client Secret, and then you host the server yourself or run it locally. WHOOP’s own guidance is that the secret should never be logged or shared. The alternative is to authorise somebody else’s hosted app, which gives a third party the same scopes.
Those scopes are not narrow. read:recovery covers heart-rate variability and resting heart rate, read:sleep covers duration by sleep stage, and read:body_measurement covers height, weight and maximum heart rate. That is a detailed health record, and the decision deserves more thought than an OAuth screen usually gets.
Athmex does not recommend a particular project, because their authorisation, data handling and reliability have not been verified. If you do use one, your own registered app is the safer version of the idea, since a shared hosted instance means someone else holds the credentials.
The numbers no route carries
Both working routes share the same blind spot, and it is not about how much data they carry. WHOOP measures what your body did. Neither route tells an assistant what you are trying to do.
Ask Claude whether Thursday’s session should be hard. Even with a perfect WHOOP connection it does not know that your marathon is nine weeks away, that your threshold pace moved in June, that you are managing an Achilles that objects to back-to-back hard days, or that the 3:15 you are chasing is eight minutes faster than your current best. A recovery score of 34% means one thing in a build block and something else during a taper, and nothing in the WHOOP account tells them apart.
That is the layer Athmex holds. You enter your thresholds, personal bests, goals, races, injuries and equipment once, each stored with the date it became true, and connect Athmex to Claude or ChatGPT directly. Athmex stores no activity history. It is not a second copy of your WHOOP or Strava data, and it does not analyse your training. The assistant does the reasoning, using facts you confirmed rather than ones it inferred.
It also covers the case the connectors do not. Whichever route carries your WHOOP numbers, and whether or not the Apple Health route is even open to you, the athlete context layer works with both assistants.
Common questions about connecting WHOOP to AI
Does WHOOP have an official Claude or ChatGPT connector?
No. WHOOP's developer documentation lists an OAuth API and webhooks but no MCP server, and WHOOP is not in either assistant's connector directory. Where WHOOP data does reach ChatGPT, it goes through Apple Health rather than through anything WHOOP built.
Can I connect WHOOP to ChatGPT?
Yes, through Apple Health. WHOOP writes into Apple Health and ChatGPT's Health feature reads it, which OpenAI documents. It needs an iPhone and a United States account. What it does not involve is a WHOOP-built ChatGPT connector, and Strava's connector still supports Claude only.
Do the community WHOOP MCP servers actually work?
Many do, and they read more of your WHOOP account than the Strava route does. The cost is that you register a WHOOP developer app and hold its Client Secret, or trust a third party that already holds one. Athmex has not verified any of them and does not recommend a specific project.
Does sleep, recovery or HRV reach Claude through Strava?
No. A recovery score can ride along on an activity WHOOP posts, but sleep, daily recovery and HRV are not activities, and Strava has no place to put them. Only workouts make the trip.
Does Athmex import WHOOP data?
No. Athmex stores no activity history from WHOOP, Strava or anywhere else. It holds the athlete context you enter yourself, including thresholds, PBs, goals, races, injuries and equipment, and supplies that to Claude or ChatGPT alongside whatever activity connector you are using.
However you get your WHOOP data into Claude or ChatGPT, an Athmex profile is worth having alongside it. It covers your goals, races and injuries, and it is where you would add Strava if you decide to go that route.
For more on what an activity route can and can't tell your assistant, see what the Strava connector doesn't tell Claude.