Apple Health MCP servers compared
Getting your Apple Health record in front of an AI agent comes down to two questions: are you willing to run a server, and are you willing for a copy of your data to leave your own devices? The options below answer those differently, and one of them is probably right for you.
The short version
If you want nothing uploaded and you are comfortable running a program on your own machine, use one of the local open-source servers. They are free, they are MIT-licensed, and your record never leaves your computer. That is a real answer rather than a consolation prize, and for a good number of people reading this it is the right one.
If you want it working from your phone with nothing to run and no export to remember, you are looking at the phone-based apps or at Pomme — and you pay for that convenience twice: in money, and in a copy of your record sitting somewhere other than your own hardware.
We make Pomme, which is the last row of the table. The other six are described the way their own documentation describes them, and every claim here has a source at the foot of the page.
The comparison
| What it is | How the data gets there | What you run | Where your record sits | Cost |
|---|---|---|---|---|
| neiltron/apple-health-mcp | CSV files written by the Simple Health Export CSV app | A Node 22 server your MCP client starts | Your own machine | Free, MIT |
| vpetersson/apple-health-mcp-server | Apple's own export: the XML, the ECG recordings and the workout routes | A Rust binary — import once, then serve | Your own machine | Free, MIT |
| the-momentum/apple-health-mcp-server | An Apple Health XML export you upload | Python, or the Docker images in the repository | Your own machine | Free, MIT |
| the-momentum/open-wearables | Continuous sync, plus Garmin, Whoop and other providers — but the Apple Health half is a Swift SDK, not an app | The platform (FastAPI, Postgres and Redis, by Docker Compose) and an iPhone app you build around the SDK yourself | A server you host | Free, MIT, before 1.0 |
| Health Auto Export | Nothing moves — the iPhone answers the queries itself | Nothing, but your agent must be on the same Wi-Fi | Your iPhone | Premium subscription |
| HealthExport | Background sync, encrypted between your phone and your browser | A command-line tool and a Claude Desktop extension, on a Mac | Their sync, decrypted on your Mac | Remote subscription |
| Pomme | Background sync from the iPhone — no file, no computer | Nothing | Our London database, encrypted at rest | Free to sync; £19.99 a year to query |
That is not every project. New ones appear most months and the MCP registries carry more. These are the ones whose documentation was complete enough to check line by line.
The local servers: nothing leaves your machine
All three read an export file into DuckDB, which is a sensible thing to do with a few hundred thousand rows of health samples: the agent gets to write SQL, and SQL is what a decade of your own measurements deserves. They differ in what they read and in what you need installed.
neiltron/apple-health-mcp
Describes itself as a local-first Apple Health MCP server. It reads CSV written by a separate iPhone app, Simple Health Export CSV, and its README is explicit that Apple's own XML export is not supported. Node 22 or newer, launched by your MCP client over stdio; the data is held in memory and rebuilt each time the server starts. Three tools: schema discovery, a read-only SQL query, and a weekly or monthly report. MIT.
vpetersson/apple-health-mcp-server
Works straight from the export the Health app writes — the XML, plus the ECG recordings and the GPX workout routes in the same folder — importing it into a DuckDB file with one command and serving it with another. Written in Rust, and it speaks both stdio and streamable HTTP, the HTTP endpoint being on your own loopback address by default. MIT.
the-momentum/apple-health-mcp-server
Python and FastMCP over DuckDB, with Elasticsearch and ClickHouse also supported and Dockerfiles in the repository. It takes an Apple Health XML export. Its README now points readers at Open Wearables as where the project went, so treat it as the older of Momentum's two. MIT.
The trade you are making with all three is the export. Apple's Health app writes you a zip when you ask it to, and nothing about that is automatic: a month later your agent is answering from a month-old file unless you remember to do it again. That is the honest cost of keeping everything local, and plenty of people are right to pay it.
The apps that keep it on your phone
Health Auto Export
Exports more than 150 metrics as CSV, JSON, Markdown or GPX and automates that to iCloud Drive, Dropbox, a REST endpoint, MQTT or Home Assistant. With a Premium subscription it also runs an MCP server on the iPhone itself: streamable HTTP is the recommended transport, requests carry a bearer token, and HTTPS uses a certificate authority the app generates on the device. Two things to know before you plan around it — the client has to be on the same Wi-Fi or LAN as the phone, and the documentation says the server stops when the app is backgrounded. In September 2026 the listing showed a free tier, a $2.99 one-off Basic purchase, and Premium at $1.99 a month, $6.99 a year or $24.99 once.
HealthExport
An iPhone app that syncs the Health types you pick in the background, end-to-end encrypted between your phone and your browser, and a command-line tool on a Mac that decrypts it there. Its MCP is a packaged Claude Desktop extension using the same local authentication as that tool, and it answers from what has been synced rather than from the watch directly. It needs a Mac and a Remote subscription; the pages we read say a subscription is required without naming the price.
Simple Health Export CSV
Not an MCP server at all — a free App Store app, with in-app purchases between $0.99 and $5.99 in September 2026, that turns your Health data into CSV on the device and hands the files wherever you point them. It is in this list because it is what neiltron's server reads.
Open Wearables: the whole platform, self-hosted
Momentum's newer project is a different scale of thing: a self-hosted platform that normalises Apple Health alongside Garmin, Whoop and other providers behind one API. FastAPI, Postgres, Redis and Celery, brought up with Docker Compose, MIT-licensed.
The Apple Health half is worth reading carefully, because it is the part that decides whether this is a weekend or a quarter. The README lists an iOS SDK in Swift, under Mobile Sync SDKs — a library, not an app. There is nothing to install on the phone. To get continuous HealthKit sync out of it you build an iPhone app around that SDK, sign it, and get it through App Review, which for an app that reads Health data is its own project with its own uncertainty. If you are a company already shipping an iOS app, that is a reasonable amount of work for a lot of capability. If you are one person who wanted your sleep in an agent, it is not the shortcut it looks like.
If you want continuous sync and you want to own the server it syncs to, this is the only thing here that gives you both. Two caveats from its own documentation: it says its APIs may change before 1.0, and while the repository carries an MCP component, the documentation we read did not describe its transport or its state — so check that yourself before you build on it.
Where Pomme fits, and what it costs you
Pomme is an iPhone app and a hosted MCP server. The app reads the categories you tick, backfills your history and keeps syncing in the background; the server answers your agent over HTTPS with a key you make in the app and can revoke. Nothing to install on a computer, no export to remember, and any MCP client that lets you set an Authorization header can reach it — from wherever you happen to be, not only from your own network.
The price of that is the part to be clear about: a copy of your record lives on our servers rather than only on your devices. It is stored in a London database, encrypted at rest, read only by agents you have issued a key to, and deleting your account erases it. But it has left your phone. If that is a line you would rather not cross, one of the local servers above is a better product for you than ours is, and we would rather say so here than have you find out after paying.
It serves ten daily categories, not raw samples
Sleep, steps, active energy, exercise minutes, resting heart rate, HRV, VO₂max, workouts, weight and body fat, as a value a day. The DuckDB servers query the export itself, so they can reach things Pomme does not carry at all — ECG waveforms and workout routes among them.
One query covers up to 1,000 days
Longer histories are answered across more than one call, which agents handle by themselves but which is worth knowing if you are planning a decade-wide question.
There is no download of your record from Pomme
Not today. If having the file matters to you, an exporter app is the thing that gives you one.
It needs an iPhone
Sync comes from the app. There is no Android app and no way to load a record in from a file.
What it costs: syncing is free, and stays free. Answers are open for your first seven days, starting at your first query. After that they are £19.99 a year in the UK, bought in the app — the App Store charges each storefront in its own currency, so the number you are shown is Apple's.
How to choose
You want nothing uploaded, anywhere
One of the three local servers. If you are happy installing a Rust toolchain, vpetersson's reads Apple's own export with no second app in the way. If you would rather not, neiltron's is Node and reads CSV from a free exporter.
You want it continuous, and you want to own the server
Open Wearables, with the caveats above. It is the most work here and the most yours.
You work at one desk, on one network
Health Auto Export. The phone is the server, nothing is uploaded, and the constraints — same network, app in the foreground — are ones you may simply never notice.
You want it to work from anywhere, with nothing to run
HealthExport if you are on a Mac and want the decryption happening there; Pomme if you would rather run nothing at all and have any MCP client be able to reach it.
You are not sure yet
Start with a free local server. It costs you an afternoon and an export file, and within a week you will know whether asking an agent about your own data is a thing you actually do. If it is, and the export chore is what stops you doing it, the hosted options are here.
Which Apple Health MCP server keeps my data on my own machine?
neiltron/apple-health-mcp, vpetersson/apple-health-mcp-server and the-momentum/apple-health-mcp-server all run locally and read an export file, so nothing is uploaded. Health Auto Export goes one further: the data stays on the iPhone and the phone answers the queries over your own network.
Do any of them work without exporting a file by hand?
Yes. Health Auto Export and HealthExport sync from the phone, Open Wearables syncs through an iOS SDK to a server you host, and Pomme syncs in the background to ours. The three DuckDB servers all read an export you make yourself.
Which ones can an agent reach from outside my home network?
HealthExport, through its Mac tool, and Pomme, over HTTPS. Health Auto Export's MCP server needs the client on the same Wi-Fi or LAN as the phone, and a local server is reachable only from the machine running it.
What does Pomme cost?
Syncing and storage are free for good. Answers are open for your first seven days, starting at your first query, then £19.99 a year in the UK, bought in the app through the App Store.
Every claim above about somebody else's software was read off their own documentation or listing on the date below. Software moves; if you are reading this much later, check before you rely on it.
- neiltron/apple-health-mcp — README: CSV from the Simple Health Export CSV app, Node 22 or newer, DuckDB in memory, three tools, MIT, and that Apple's XML export is not supported.
- vpetersson/apple-health-mcp-server — README: Rust, imports Apple's XML export with the ECG recordings and GPX routes into DuckDB, stdio and streamable HTTP on the loopback address, MIT.
- the-momentum/apple-health-mcp-server — README: Python and FastMCP over DuckDB with Elasticsearch and ClickHouse options, XML upload, Docker, MIT, and the note that the project has evolved into Open Wearables.
- the-momentum/open-wearables — README: self-hosted FastAPI platform with a Swift iOS SDK for HealthKit, Postgres, Redis and Celery by Docker Compose, MIT, APIs may change before 1.0.
- Health Auto Export — App Store listing: formats, the automation destinations, the built-in MCP server, and the prices shown in September 2026.
- Health Auto Export — server connection — Documentation: streamable HTTP and TCP, bearer token, the locally generated certificate authority, the same-network requirement, Premium, and that the server stops when the app is backgrounded.
- HealthExport — Background sync of the Health types you choose, end-to-end encrypted between phone and browser, and that remote export requires a subscription.
- HealthExport — Apple Health MCP — The Mac command-line tool, the packaged Claude Desktop extension and its local authentication, and that it queries what has been synced rather than the watch.
- Simple Health Export CSV — App Store listing: free with in-app purchases from $0.99 to $5.99 in September 2026, processing done on the device, no data collected by the developer.
Sources checked 10 September 2026
Go on then — point an agent at it
Free to download and free to sync. Answers are open for your first 7 days.