Apple Health plus Oura and Whoop: What Works Today and What Is Coming

Your ring tracks your sleep. Your band tracks your training. Your watch tracks your heart. Here is what MetricBridge can already give your AI from all three, and the per-source reconciliation we are building next.

By MetricBridge · Updated 17 October 2026 · ~7 min read

AI-assisted, human reviewed. How we use AI

Ask an Apple Watch, an Oura ring and a Whoop band how well you slept last night and you can get three different answers. That is not a bug in your devices. Each one measures a slightly different thing, on its own schedule, and keeps its own scores in its own app.

You end up with a fragmented picture. Your recovery lives in one app, your readiness in another, your workout history in a third. No single view sees all of it, and the AI you already use cannot easily answer a question that spans them.

What works today

Apple Health is already the on-device store many wearables write into. MetricBridge reads it read-only on your iPhone and exports 190 metrics as local JSON to iCloud Drive, a folder, a device on your local network, or a webhook you set up. The free, open-source MCP server then lets your AI agent query that export with 16 read-only tools.

• Oura can write sleep, heart rate, resting heart rate, respiratory rate, steps, weight and workouts into Apple Health when you enable its Health sharing.
• Whoop, Garmin, Fitbit, Strava and Withings can likewise write activity, workouts, heart rate and more.
• What you get in the export today: one value per metric per day, already merged across sources by Apple Health. You cannot yet see which device a number came from, or where two devices disagree.
• What is not in the export today: vendor-only scores such as Oura Readiness, Whoop Recovery and Strain, and Garmin Body Battery. These stay in their own apps.

How reconciliation will work

This part is in development and testing. It is not available yet, and there is no beta running. The plan has three pieces:

1. Source attribution. Readings will gain a source dimension. When two devices disagree on a metric, a source priority will decide which one is used, and the other copy will be kept rather than discarded, so your agent could say which device it relied on.
2. Vendor-score import. Scores that never reach Apple Health will be importable from each vendor's own export file and stored locally as a labelled file the MCP server can read.
3. Dedup and normalization. The same run can arrive from two apps; a matching rule plus source priority will keep one clean copy.

What this will get you

Once reconciliation ships, you could ask a question that spans devices and have the agent answer from one export, with the numbers and the sources shown. The exchange below is an illustrative example of the upcoming feature. The numbers are made up, and the source-filtered query does not exist today:

Illustrative example (upcoming feature, not available today)

You: This week, did my Oura sleep or my Watch sleep trend better?

Agent: [calls compare_periods, source-filtered]
       Oura deep sleep: 1.9h avg this week, up 12% vs last.
       Watch deep sleep: 1.7h avg this week, up 6% vs last.
       Source priority used: Oura for sleep stages.

Today, the same compare_periods tool already compares two periods of your merged Apple Health data, without the per-source split.

The privacy line does not move

• Read-only. HealthKit access is read-only. MetricBridge reads, it does not write back to your health record.
• No MetricBridge server in the path. The MCP server makes zero network calls. It reads a local JSON file and talks to your agent over a local pipe. Your health data never passes through any server we operate.
• Your choice of agent. If you use a cloud AI agent such as Claude or ChatGPT, the numbers it requests go to that provider under its terms. With a local model, they stay on your machine.
• No account. There is nothing to log in to.

Our privacy commitments are scoped to your health data and to the MCP server. They are stated plainly in the privacy policy, and the server's behavior is open on GitHub.

Reconciliation is coming next

The Apple Health export and MCP server are available today. Per-source reconciliation and vendor-score import are in development, with no date promised. If you want to hear when they are ready, join the early-access list. Joining does not guarantee access.