Dev.to AI ๐Ÿค– Ai ๐Ÿ‘ 0 ๐Ÿ“– 7 min read

Claude Apple Health Is US-Only and Pro-Tier: The Connector Route

Claude's Apple Health Access Is US-Only and Pro-Tier: The Connector Route That Works in Any Country Anthropic shipped Apple Health inside the Claude iOS app in January 2026. It is a good feature, it is also beta, US-on

Claude's Apple Health Access Is US-Only and Pro-Tier: The Connector Route That Works in Any Country

Anthropic shipped Apple Health inside the Claude iOS app in January 2026. It is a good feature, it is also beta, US-only and locked to Pro, Max and Ultra. If you are in London, Berlin or Sydney, or on the free plan, the built-in button is not there. The route that is: your own export, and a connector your agent can read.

By MetricBridge ยท Published 4 November 2026 ยท ~8 min read

AI-assisted, human reviewed. How we use AI

Quick answer

Claude's built-in Apple Health sharing is beta, needs a Pro, Max or Ultra plan, and is US-only, per Anthropic's own help centre. Everywhere else, the working route is a connector: export Apple Health from your iPhone to a folder you own, then point a local MCP server at that folder so Claude can query it as tools. That route has no country gate and no plan gate, because the work happens on your own machine and nothing is hosted.

What Anthropic actually shipped

The facts are worth stating precisely, because most of the copy around this feature rounds them off. From Anthropic's help centre: Claude can connect with iOS system apps, including health and fitness data. Health features are currently in beta, require a Pro, Max or Ultra plan, and are available in the US only. The January announcement added Health Connect for Android, plus the HealthEx and Function connectors, all in beta for US Pro and Max users at launch. Anthropic also says the data is opt-in and never used for training.

None of that is a criticism. Beta, region-gated rollout is normal, and health data is exactly the category where you want a company to be slow. But it does mean a very large number of people reading about "Claude plus Apple Health" cannot use the thing being described.

Who is actually locked out

      - Anyone outside the US. The UK, the EU, Canada, Australia, most of the world. No built-in health path today.

      - Anyone on the free plan. The feature sits behind Pro and above, by design.

      - Anyone who wants their agent to compute, not just summarise. The built-in path is Anthropic's reading of your data. If you want your own agent to run its own arithmetic over raw samples, you need the raw samples.

That third group is the interesting one, because it is also the group that never wanted the built-in feature in the first place.

The connector route, in plain terms

A connector is not magic and it is not a workaround. It is two pieces:

      - An export. Your iPhone writes Apple Health data to a folder you choose, as JSON or CSV. That happens on the phone, read-only, and it is your file.

      - A server that reads the export. An MCP server runs on the same machine as your agent, reads that folder, and exposes the data as tools the model can call. Ours is [open source](/mcp/), zero-dependency, and speaks stdio.

Add it to Claude Desktop, Claude Code, Cursor, opencode or any other MCP client with the standard mcpServers block, point HEALTH_DATA_DIR at your export folder, restart the client. The full config per client is on the MCP page. There is no signup step in the middle, because there is no service in the middle.

Why this travels better. A hosted feature has to be switched on country by country, plan by plan, and it stays in beta until it is not. A local server has no country and no plan. If you can install Node and edit a JSON file, you are past every gate Anthropic has.

What the connector gets you that the built-in route cannot

The built-in integration gives Claude a summary of your health data. The connector gives your agent the data itself, plus the tools to query it. In our server that is 22 tools, 20 read-only (the other two log events to their own file, and never write to Apple Health), plus the prompts that wrap the common questions, and all 194 metrics as JSON with units, date ranges and coverage.

The practical difference: with the built-in path you ask Claude a question and get Claude's sentence. With the connector you ask, get the samples back, and your agent does the arithmetic on numbers you can also open in a spreadsheet. That matters when the answer is load-bearing and you want to see the working.

The honest limits of the connector

Two things the built-in route genuinely does better, and you should know them before you choose:

      - Setup. The built-in feature is a switch inside an app. The connector is an export destination and a config file. It is 15 minutes, not 15 seconds.

      - Zero-maintenance. Anthropic maintains their pipe. You maintain yours, which mostly means an export that keeps running. Set it to automatic and you forget about it; set it manual and you will notice.

And one limit that applies to both: neither is a medical device. Both describe your own data. Neither detects, treats or monitors a condition, and neither should be asked to.

What the export half looks like

The connector is only as good as the export under it. MetricBridge reads Apple Health read-only on the iPhone and writes 194 metrics as JSON or CSV to the destination you pick, on whatever schedule you set. From there your agent, and only your agent, reads it over MCP.

Privacy, stated exactly rather than broadly: your health data never reaches us or a cloud AI. The MCP server makes zero network calls, so an export goes only where you point it. Two things worth naming precisely, because "private" is a word people overreach with: the iOS app reports install, trial-start and purchase events to Meta for ad attribution, never health data, and only if you allow tracking when iOS asks; and once you export, the file travels wherever you send it.

Doing this yourself? [MetricBridge](https://dub.sh/WtmrJwr handles the export step in whichever country you live in: all 194 metrics as local JSON, with the open-source MCP server ([GitHub](https://dub.sh/cq0l9Gg

FAQ

Is Claude's built-in Apple Health access available outside the US?

No. Anthropic's own help centre says the health features are in beta, require a Pro, Max or Ultra plan, and are available in the US only. If you are outside the US, or on the free plan, the built-in path is not open to you, and a connector is the route that is.

What is the connector route to Apple Health in Claude?

You export Apple Health from your iPhone to a folder you control, then add a local MCP server that reads that export and exposes it to Claude as tools. Nothing is hosted by the connector, and you supply the data path yourself. It works in any country, on any Claude plan, because it is your machine doing the work.

Does the MCP connector need its own account or API key?

The MetricBridge MCP server needs no account, no API key and makes zero network calls; it reads local files over stdio. The app is a single $24.99 one-time unlock after a 7-day free trial, charged once.

Is this the same as Claude's built-in integration?

No. The built-in integration is Anthropic reading your Health data on your behalf. The connector route is your own agent reading a file you exported, with a server you can inspect and a data folder you can delete. They are different trust shapes, and both are opt-in.

Your health data in the agent you already use, in any country

Export all 194 metrics on the iPhone, then let Claude, Cursor or any MCP client query them locally. No country gate, no plan gate, no account in the middle.

        [Start my 7-day free trial](https://dub.sh/WtmrJwr
        [Install the MCP server](/mcp/)
        [Source on GitHub](https://dub.sh/2HsnrQ0

Where it goes: the app reads Apple Health read-only and writes JSON to a folder you pick. Your health data never reaches us or a cloud AI; the MCP server makes zero network calls. What you get: all 194 metrics, on-device Ask with a provenance card on every answer, the Weekly Brief, and the Mac and Apple Watch apps. Price: $24.99 one time after a 7-day free trial, not a subscription. Wellness, not medical advice.

Related reading

        - โ†’ [Connect Apple Health to Claude via MCP: the exact config](/blog/connect-apple-health-to-claude-mcp)

        - โ†’ [Pass-through vs answer-on-device: who computes your health answer](/blog/pass-through-vs-answer-on-device)

        - โ†’ [The MCP server: 22 tools (20 read-only) and every client config](/mcp/)

        - โ†’ [All 194 metrics the export covers](/metrics/)

        - โ†’ [health-export-mcp: the zero-dependency MCP server on GitHub](https://dub.sh/2HsnrQ0
๐Ÿ“ฐ Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes โ€” full credit and traffic to the original publisher.