The problem
You've done this.
- Open Fitness, screenshot the summary.Maybe Strava too. Maybe the heart-rate graph.
- Paste it into ChatGPT.Type the context again: what the session was, how you felt, what last week looked like.
- Get a polite guess.“Based on the image, your pace seems to have improved slightly.”
A screenshot is an average and a blurry graph. Your AI can't see the reps, the heart rate between them, or last month. So it guesses, kindly. And next week, you do it all again.
What your AI actually sees
Am I getting faster? Here are my last runs
Based on these screenshots, it looks like your average pace may have improved slightly over the period, though it's hard to say without more detail…
What changes
Give it the whole workout instead.
Every sample, not a summary
Three legs of a brick, the pause between them, the time zone, every heart-rate reading with its interval. Apple Health keeps it all. Now so does your AI.
Nothing to paste, ever again
Open the app after a run. The session leaves on its own, most recent first. No export, no file, no screenshot.
Read-only, and yours
Sign in with Apple. Each AI gets its own access, approved and revoked from your iPhone. Delete your account, and everything goes with it.
Real answers, real workouts
Ask it what you actually want to know.
How was yesterday's interval session?
healthsync · get_workout 15 legs · 7.72 km · 48:10
Six 400 m reps on 75-second jogs, after an 18-minute warm-up: 2:02, 1:57, 2:00, 1:59, 1:57, 1:58. Heart rate averaged 130 bpm on the reps and peaked at 150 on the fifth; power held between 295 and 308 W. Ground contact time dropped from 266 ms in the warm-up to 224 ms on the reps: you were running tall. A consistent session, and 23 °C with 65 % humidity didn't show in the heart rate.
Is my easy pace getting faster at the same heart rate since August?
healthsync · list_workouts running · 2026-08-01 → 2026-09-15 · 22 workouts
A little. Over 17 runs of 4 km or more, intervals aside, you cover 1.22 m per heartbeat in September against 1.19 in August: 2 % more, which is 8 seconds per kilometre at 130 bpm, 6:18 instead of 6:26. The standout is the 10th: 8.1 km with 181 m of climbing at 6:14/km and 127 bpm, your most efficient run of the two months. Seven September runs is a short sample; ask again in October.
Did my heart rate drift over the second half of my 10 km?
healthsync · get_workout_series heartRate · runningSpeed · distance · 59 rows
Not really. Second half averaged 146 bpm against 135 in the first, but you also went from 6:09/km to 5:42/km. Heart rate rose 8.5 %, speed rose 8 %: that's pacing, not drift. The one stretch that does drift is km 7 to 9, where you held 5:13/km and heart rate crept from 150 to 154. The last 900 m at about 6:40/km brought it back to 139.
Compare Friday's ride with the same loop on August 26.
healthsync · get_workout 2 workouts · 32.8 km each
Ten minutes faster: 1 h 17 against 1 h 27 for the same 32.8 km and the same 68 m of climbing, 25.5 km/h against 22.5. Heart rate averaged 132 against 125, so speed per heartbeat is up 8 %. Two asterisks: it was 22 °C on Friday and 27 °C in August, and the August ride had four stops where Friday had none. Fitter, and also a better day for it.
Was last week lighter than usual?
healthsync · list_workouts 2026-08-10 → 2026-09-13 · 5 weeks
Yes. 5 h 49 against 8 h 28 the week before and 7 h 22 the one before that. Running held at 2 h 54, in line with the previous two weeks. The cut came from the bike, 2 h 24 against 4 h 02, and from the pool, one 31-minute swim against two. If that was planned, fine; if not, Friday's ride was the only long session of the week.
How even were my 50s in Monday's swim?
healthsync · get_workout 16 laps · 800 m · 50 m pool
Sixteen lengths between 61 and 88 seconds, 72 s median, 22 strokes per length. The structure reads as 5 × 50 on about 50 seconds rest (72, 69, 63, 71, 65), a continuous 200 in 5:09 (78, 70, 88, 72), a 150 in 3:50, three minutes off, then 4 × 50 (61, 75, 65, 73). Length 13, the first of that last set, was your fastest of the day. Heart rate averaged 98 bpm and never passed 137: this was a technique session, not conditioning.
Every answer was computed by Claude from real workouts, through HealthSync. Your numbers will be yours.
How it works
Three steps, five minutes.
- On your iPhoneInstall HealthSyncSign in with Apple, allow Apple Health. Every workout syncs on its own, each time you open the app.
- In Claude or ChatGPTConnect your AIAdd HealthSync. A page shows a QR code: scan it with your iPhone, tap Allow. Read-only, revoke any time.
- AnywhereAsk“How was yesterday's interval session?” That's the whole workflow.
The address your AI connects tohttps://api.gethealthsync.ai/mcpMCP over HTTPS
What syncs
Every workout Apple Health holds, in the shape it holds it. A multisport session arrives as its legs, with the transitions between them.
- Running
- Walking
- Cycling
- Swimming
- Hiking
- Rowing
- Elliptical
- Yoga
- HIIT
- Strength training
- Multisport, leg by leg
With each one: heart rate, the GPS route and its altitude, distance per sport, active and basal energy, cadence and power where the watch records them — as samples carrying their own interval, not as an average.
Pricing
Free to sync. Pro to go deep.
Free
€0, always
- Every workout syncs, every sport
- Your AI reads the last 30 days
- Summaries and legs, without the heart-rate series
Pro
€6.99 a month · €59.99 a year
- Your whole history: “since spring”, “this time last year”
- Every heart-rate series, second by second
- Drift, pacing, efficiency per heartbeat
The first 14 days are free, with no card. Billed through the App Store; prices vary by country. What Pro adds
Privacy
GDPR-compliant, secure, and yours.
You sign in with Apple: no password, nothing sold, nothing shared. HealthSync asks Apple Health for workouts, routes and heart rate, and for nothing else.
Read-only, always
An AI can read your workouts. It cannot write to Apple Health, and it never sees anything else.
Each AI has its own key
Approved from your iPhone, revoked from your iPhone, the same second. The server keeps only a hash of it.
Leave with everything
Delete your account from the app. Workouts, keys and the account go with it.
Questions people ask
Does HealthSync work with ChatGPT?
Yes, as a plugin you add in Developer mode. ChatGPT offers that on its paid plan tiers, Plus and up, and Developer mode has to stay on; that is ChatGPT's rule, not ours.
Do I need to export my Apple Health data?
No. The app reads HealthKit on your iPhone and syncs on its own when you open it. There is no XML export, no file to move and nothing to unzip.
Do I have to do anything after each workout?
Open the app. That is it: the session leaves on its own, and your AI can read it a minute later. No screenshot, no paste.
Which workouts sync?
Every workout Apple Health holds: running, walking, cycling, swimming, hiking, rowing, elliptical, yoga, hiit, strength training, multisport, leg by leg. A multisport session arrives as its legs, with the transitions between them.
Does it keep heart rate, GPS and altitude?
Yes, as samples carrying their own interval rather than as averages, along with the GPS route and its altitude. A question about the run is answered from the run.
Where is my data stored?
In the European Union, under GDPR, on HealthSync's servers in Paris, France, under your Apple account. Each AI assistant you connect gets its own access, which you can revoke from the app, and the server keeps only SHA-256 hashes of the tokens.
Does it work with Claude Desktop and Claude Code?
Yes. HealthSync speaks MCP over HTTPS, so any client that speaks MCP can read it: Claude Desktop, Claude Code, ChatGPT, and the rest.