Claude Now Connects to Apple Health Natively: Cloud Sync vs On-Device MCP
Anthropic shipped native Apple Health support for Claude in January 2026, the first big AI platform to pull HealthKit data straight into a cloud model. It's convenient. It also means your health data leaves your phone. Here's what actually happens, and the on-device path that keeps it local.
Quick answer. Claude's Apple Health connector syncs your HealthKit history to Anthropic's servers so Claude can reason over it. That's a cloud round-trip every time you ask a question. The alternative is an on-device health AI that answers on your phone with no upload, plus a zero-dependency MCP server that lets any agent you run read the same data from a folder you control.
What Claude actually shipped
In late January 2026, Anthropic announced Apple Health and Android Health Connect integrations rolling out in beta through the Claude iOS and Android apps, alongside new HealthEx and Function connectors for healthcare. MacRumors covered the Apple Health rollout on 22 January 2026. The short version: you toggle a connection in the Claude app, pick which categories to share (steps, sleep, or everything), and Claude starts referencing your HealthKit data in replies.
That is genuinely useful. For the first time, a major assistant reads your steps, sleep, and heart data without you exporting a file. The trade-off is the part most write-ups skip.
What happens to your data
Claude's connector is cloud sync. Your HealthKit data moves from your iPhone through Apple's sync infrastructure and lands on Anthropic's servers, where the model reads it. Every follow-up question is another round-trip over the network. You are also handing a second company, on top of Apple, a running copy of your most personal measurements.
For a lot of people that's an acceptable trade for the convenience. The point is that it's a trade, and it's one you should be able to decline without giving up the ability to ask an AI about your health data. That's where the on-device path comes in.
The on-device alternative
On-device health AI runs the model on your phone. You ask a question in plain English, the answer is computed locally, and it shows you the numbers it used (a provenance card), so you can check the work instead of taking a smooth paragraph on faith. Nothing is uploaded, so there's no cloud account and no sync to a third party. MetricBridge's Ask and Pro chat work this way, and the Weekly Brief summarizes your week from the same local data.
Then there's the agent side. Instead of locking your data to one assistant, you export once to a folder you pick (iCloud Drive, a synced folder, your LAN, or a webhook you run) and point a zero-dependency MCP server at it. Any MCP client (Claude, Cursor, ChatGPT, opencode, and more) can then query the same 190 metrics through 14 read-only tools. Your data never transits the server author's infrastructure, and you keep the model you already use.
Cloud sync vs on-device MCP, side by side
| Claude native connector | On-device + MCP | |
|---|---|---|
| Where the model runs | Anthropic's cloud | Your phone (chat), your machine (MCP) |
| Where your data goes | Apple servers, then Anthropic servers | Stays local |
| Which agents can use it | Claude only | Any MCP client |
| Cost | Free with an Anthropic account | One-time $24.99 for the app; MCP server is open source |
| Read-only tools | None (built-in connector) | 14 (get_trends, compare_periods, correlate_metrics, and more) |
The developer angle is the quiet one. Claude's native connector is a single vendor, single assistant path. If tomorrow you want Cursor to write a script over your sleep data, or opencode to diff two months of HRV, the native connector does nothing for you. An MCP server is the opposite: write the config once, and every MCP-aware client reads the same local file. You're not re-exporting or re-authorizing anything.
Which one should you use?
If you want the absolute fastest setup and you're comfortable with your health data living in Anthropic's cloud, Claude's native connector does exactly what it says. If you'd rather keep your health history on hardware you control, and still want to ask an AI about it, the on-device plus MCP route is the better fit. The two aren't mutually exclusive, but they make opposite bets about where your data belongs.
For most privacy-conscious users, the deciding question is one sentence: do you want a second company holding a running copy of your heart rate and sleep history, or not. If the answer is not, the on-device route is the one that exists today.
Building the local path yourself? MetricBridge is the on-device health AI whose MCP server is open source and zero-dependency. A one-time $24.99 purchase covers export, MCP, and on-device chat. No subscription, nothing synced to us.
{
"mcpServers": {
"health-export": {
"command": "npx",
"args": ["-y", "health-export-mcp"],
"env": { "HEALTH_DATA_DIR": "~/Library/Mobile Documents/iCloud~ai~healthexport~app/Documents" }
}
}
}Ask your Apple Health data anything, without the cloud
On-device answers with provenance, plus an open-source MCP server for every agent you run. Local-first, read-only, no accounts.
Frequently asked questions
Does Claude's Apple Health connector keep my data on my phone?
No. Claude's native Apple Health integration syncs your HealthKit data to Anthropic's cloud so Claude can reason over it. The on-device alternative runs the model on your phone and keeps your data local.
Can I use Claude's Apple Health connection with Cursor or another agent?
No. Claude's native connector is specific to Claude. An MCP server is the portable path: export once, and Claude, Cursor, ChatGPT, opencode, and any other MCP client can query the same local data.
What is the on-device alternative to syncing Apple Health to the cloud?
An on-device health AI answers questions on your phone with no upload, and a zero-dependency MCP server lets your own agents read the same data from a local file. Neither sends your health history to a third-party cloud.
When did Claude add Apple Health support?
Anthropic announced Apple Health and Android Health Connect integrations rolling out in beta in late January 2026 via the Claude iOS and Android apps, as part of a broader healthcare push. MacRumors covered the Apple Health rollout on 22 January 2026.