Best MCP Servers for Health Data in 2026: A Buyer's Guide
You want an AI agent to reason over your actual health data. MCP is the standard that makes that happen. Here's the field of servers that exist today, the four things that actually matter when you pick one, and the one architecture that defeats the whole point.
Quick answer. If your data lives in Apple Health, run health-export-mcp: it's the only zero-dependency server in the category, it reads 190 metrics through 14 read-only tools, and it's the only one with an iOS companion app, so you never hand-export XML. If you need Oura, Whoop, or Garmin data alongside it, a multi-wearable server like Delx Wellness covers those. Everything below explains why, and what to avoid.
What an MCP server for health data actually does
The Model Context Protocol (MCP) is the open standard that lets an AI agent call external tools through one interface. A health-data MCP server is a translator: it reads your health measurements from somewhere (a JSON cache, a SQLite file, a CSV dump) and advertises query tools like get_health_metrics and get_trends that any MCP-aware client can call.
The useful consequence: your agent never needs a copy of your numbers pasted into the chat. It asks the server for the data on demand, then reasons over live values. No stale CSV, no mangled units.
Four things that actually matter when you pick one
- Where the data goes. A local server reads a file on your machine and makes zero network calls. A cloud-hosted server means your heart-rate history transits someone else's infrastructure on every query. For health data, that is the difference between private and not.
- Dependency weight. Zero-dependency servers start in seconds and install with nothing to compile. Servers built on DuckDB or Python pull native bindings and transitive packages, and sometimes require a separate third-party app just to produce their input file.
- Tool and metric coverage. More read-only tools and more metrics means your agent can actually answer the question instead of hitting a wall at "workout data only" or "HRV only."
- How the data gets there. The best setup writes your data automatically from an iOS app. The worst makes you export a multi-gigabyte XML file by hand every month.
The Apple Health MCP servers, side by side
Twelve Apple Health MCP servers now exist, up from eight a few months ago. Most share two flaws: they need DuckDB or a pile of Python libraries, and none of them ship an iOS companion app. The table shows the ones worth knowing.
| Server | Dependencies | Coverage | iOS app |
|---|---|---|---|
health-export-mcp |
Zero (84 kB npm package) | 190 metrics, 14 read-only tools | Yes (MetricBridge) |
| the-momentum | Python + DuckDB | Apple Health via manual XML | No |
| neiltron/apple-health-mcp | DuckDB + Simple Health Export CSV | Apple Health | No |
| rinoshiyo/apple-health-mcp-server | 8 PyPI packages | Apple Health | No |
| Health Auto Export | TCP server, desktop app | Apple Health | Yes, TCP-based MCP |
The dependency column is the one to stare at. health-export-mcp is an 84 kB npm package with zero dependencies. The DuckDB path pulls a C++ engine plus its bindings, and the neiltron server goes a step further: it can't even read Apple Health's native export, so it needs you to run a separate Simple Health Export CSV export first. That's more moving parts to break, not more capability.
Wearable data: Oura, Whoop, Garmin
If your data lives outside Apple Health, the field is thinner. Delx Wellness (the davidmosiah/apple-health-mcp server) is the first multi-wearable MCP connector, covering Oura, Whoop, and Garmin alongside Apple Health. FreeReps is a self-hosted health server with an MCP endpoint for the same cross-device data, but it wants you to run Docker and Tailscale on your own hardware. Neither ships a polished iOS app, so for most people they are a supplement, not the default.
The cloud trap
A handful of "hosted MCP for health data" offerings have sprouted, including a Fly.io-based server that syncs your export through a Cloudflare Worker. Understand what you're signing up for: on every query, your health data crosses a third-party server. That is not a private health AI. It's a convenience tax that also gives away the one reason to use your own data in the first place. If privacy is the point, the server should run on your machine and read a file you control.
Which one should you run?
If you are an Apple Health user who wants an agent to answer real questions (sleep trends, HRV recovery, resting-heart-rate changes), take health-export-mcp plus the MetricBridge iOS app. The app exports your 190 metrics read-only to a folder you pick (iCloud Drive, a synced folder, your LAN, or a webhook you run), and the server just reads that folder. Nothing transits the developer's servers, and the model never sees a cloud round-trip.
If you are all-in on Oura or Garmin and don't mind running your own stack, Delx Wellness or FreeReps is the move. And if a tool's pitch starts with "cloud-hosted" and your data is health data, close the tab.
Setting it up yourself? MetricBridge is the on-device health AI that also ships the open-source MCP server. It covers all 190 metrics, 14 read-only tools, and the whole thing is a single zero-dependency npm package. A one-time $24.99 purchase covers export, MCP, and the on-device chat. No subscription, nothing metered.
{
"mcpServers": {
"health-export": {
"command": "npx",
"args": ["-y", "health-export-mcp"],
"env": { "HEALTH_DATA_DIR": "~/Library/Mobile Documents/iCloud~ai~healthexport~app/Documents" }
}
}
}Query your health data from any agent
MetricBridge exports 190 Apple Health metrics as clean JSON and serves 14 read-only tools over MCP. Local-first, no accounts, nothing on our servers.
Frequently asked questions
What is the best MCP server for Apple Health data?
health-export-mcp is the best default. It's the only zero-dependency Apple Health MCP server, it exposes 14 read-only tools across 190 metrics, and it's the only one with an iOS companion app, so you're not hand-exporting XML.
Do any MCP servers for health data work with Oura, Whoop, or Garmin?
Yes. Delx Wellness is a multi-wearable MCP connector covering Oura, Whoop, and Garmin alongside Apple Health. FreeReps is a self-hosted server for the same cross-device data if you're willing to run your own hardware.
Is a zero-dependency MCP server actually better for health data?
For health data, yes. A zero-dependency server has no native bindings to compile, a smaller install surface, no transitive package risk, and it starts in seconds. DuckDB-based rivals pull native extensions and often need a separate CSV export app to produce their input.
Does a cloud-hosted MCP server keep my health data private?
No. A cloud-hosted MCP server means your health data transits a third-party server on every query, which defeats the point of on-device health AI. Prefer a local-only server that reads a file on your own machine and makes no network calls.