HealthAPI Answered "Connect Apple Health to Claude" With a $4.99/Month Connector
Someone finally put a recurring meter on the query we've been answering for free. A cloud connector now sells Apple Health access to Claude at $4.99 a month for 100 requests a day. That's a meter on reading your own body's data. Here's the arithmetic, and what a local server does instead.
Quick answer
HealthAPI, a cloud Apple Health connector, now prices access by request quota: $4.99 a month for 100 requests a day or $9.99 a month for 1,000 requests a day, after a 2-day preview and a 7-day trial. It is read-only and server-side, meaning the vendor holds your data and answers your agent from their infrastructure. That is $59.88 a year on the lower tier. MetricBridge is a $24.99 one-time unlock covering the export, the local MCP server, and the on-device Ask and Weekly Brief. Nothing is metered, because there is no server to meter.
What actually changed this week
For two years the "connect Apple Health to Claude" shelf was populated by open-source servers and a handful of apps. Free or one-time. This week that changed: a commercial cloud connector joined the shelf, and it did something nobody else had done. It put a per-request price on your own health data.
That is worth naming plainly, because it reframes the whole purchase. You are not paying for the data. You already own the data, it is on your phone. You are paying rent for the right to have it served back to you 100 times a day.
What we priced. Figures come from the vendor's own pricing and setup pages, read and hashed on 2026-10-18 (evidence ids E1, E2 and E3 in our weekly market pack). Pricing changes. Check the source before you subscribe to anything.
The arithmetic over a year
Recurring plans are small on the day you buy them and large on the day you count them.
| Model | Up front | 12 months | Quota |
|---|---|---|---|
| MetricBridge (one-time unlock) | $24.99 once | $24.99 | Unlimited local reads |
| Cloud connector, lower tier | $4.99/mo | $59.88 | 100 requests/day |
| Cloud connector, higher tier | $9.99/mo | $119.88 | 1,000 requests/day |
The one-time unlock pays for itself against the lower tier in five months, and against the higher tier in two and a half months. Every month after that, the recurring charge is pure margin on data you already owned.
That comparison is not the whole story, and it would be dishonest to pretend it is. A recurring plan funds a hosted service, and running a server that holds health data for many users costs real money. If you want someone else to host it and you want zero setup, that is a fair trade and the price is reasonable for what it is. But you should make that trade knowingly, because it is a trade: you give up the data staying home, and you accept a ceiling on how often you may look at it.
Where the server sits is the real difference
Two setups, same demo, opposite architecture.
| Local server (MetricBridge) | Cloud connector | |
|---|---|---|
| Where your health data lives | Your iPhone and your own disk | The vendor's servers |
| What answers the agent | Your own machine, over stdio | The vendor's infrastructure, over the network |
| Metering | None. Unlimited local reads | 100 or 1,000 requests a day |
| Account required | No account on the data path | Vendor account and plan |
| Works offline | Yes, the export is already local | No |
| Recurring charge | None | Recurring, indefinitely |
None of this is about which model is smarter. Both setups can put your numbers in front of Claude. The difference is whether the server that reads your resting heart rate is a process on your Mac, or a business someone has to keep funded every month.
What a request quota feels like in practice
One hundred requests a day sounds generous until you watch how an agent works. You ask a natural-language question, the model decides which tools to call, and it may call several: one to resolve the metric name, one to pull the range, one to compute the trend. A single good question can be a handful of requests. A morning check-in and an evening review, every day, is a rhythm that runs closer to a ceiling than the question count suggests.
With a local server, that pressure does not exist. There is no counter, because there is nothing counting. The agent reads rows from a file you own, as often as you like.
How to set up the unmetered version
Install the MetricBridge iOS app and turn export on. Install Node.js 18 or newer. Add this block to your desktop agent's MCP config, point the path at your export folder, and restart the agent.
{
"mcpServers": {
"health-export": {
"command": "node",
"args": ["/Users/you/.health-export-mcp/server.mjs"],
"env": {
"HEALTH_DATA_DIR": "/Users/you/Library/Mobile Documents/iCloud~ai~healthexport~app/Documents"
}
}
}
}Ask the agent to call get_mcp_status to confirm it can see your data. Then ask it something real: how did HRV trend this week against last week. It answers from your own numbers, every answer a deviation from your personal baseline, with no request counter ticking in the background. Setup details per client are in the Claude guide and the plan-eligibility matrix.
FAQ
How much does a recurring Apple Health connector cost per year?
One cloud connector we priced on 2026-10-18 charges $4.99 a month for 100 requests a day after a 2-day preview and a 7-day trial, or $9.99 a month for 1,000 requests a day. That is $59.88 a year on the lower tier and $119.88 on the higher one. A one-time unlock pays for itself against the lower tier in five months.
Is 100 requests a day enough for a health agent?
It depends on how the agent is wired. A single natural-language question often triggers several tool calls, so a model that fans out can burn requests faster than the question count suggests. If your health agent lives inside a chat you use daily, a 100-a-day ceiling is a meter you will watch.
Does a local Apple Health MCP server have a request quota?
No. A local server reads a file on your own machine and returns the rows the agent asks for. There is no per-request meter, because nothing is being served from someone else's infrastructure. MetricBridge ships that server as part of a one-time unlock, so there is no recurring charge on the data path.
Does the data leave my iPhone with a cloud health connector?
With a server-side connector, yes: the vendor holds your health data and answers your agent from their servers. With a local server, your HealthKit export stays on your iPhone and your disk, and the agent calls run on your machine. Those are different privacy models, not just different prices.
Doing this yourself? MetricBridge handles the export step: all 190 metrics as local JSON, with the open-source MCP server (GitHub).
Buy it once. Then read your own data as often as you like.
MetricBridge is a $24.99 one-time unlock. It covers the export, the raw MCP server, and the on-device Ask and Weekly Brief. No subscription, no account, nothing on our servers.