Health Auto Export Now Ships an "Integrated MCP Server": What the Listing Claims vs a Zero-Dependency Local Server
The export incumbent just added an MCP Server to its App Store listing, so the agent path is now bundled into the paid app. It is a real server, and a different architecture from a local one. Here is what the listing describes and how to compare the two before you pick.
Quick answer. Health Auto Export's listing now advertises "the integrated MCP Server." Per the vendor's own help pages, that server runs on the iPhone and lets AI clients on your local network query health data over an endpoint like http://{LAN_IP}:9000/mcp with a bearer token, and the app must stay in the foreground while clients are connected. A zero-dependency local server is the other architecture: a small Node program on your computer that reads a synced JSON snapshot and makes zero network calls. Both keep data off a vendor cloud. They differ in where the server runs and what has to stay awake.
"It has MCP" now appears on half the category's feature lists, and it hides the thing that decides whether your agent can reach your data at 2am. Here is what the incumbent shipped, then the same test on our app.
What the listing claims, and what the help page describes
Credit where it is due: the claim is accurate. Health Auto Export (App Store, roughly 410 ratings at 4.3) is a mature export app, and 150+ metrics plus MQTT and Home Assistant integrations is a deep feature set. The architecture is the part the listing line leaves out, and the vendor documents it in its help center:
- The server runs on the iPhone. "The MCP Server on iOS lets AI clients and scripts on your local network query your health data."
- It is a network transport. "HTTP (Streamable MCP) is the recommended transport," at a LAN address,
http://{LAN_IP}:9000/mcp, with a bearer token. It also supports TCP "for Node-bridge setups." - The phone has to be awake and showing the app. "Health Auto Export on iPhone (app must stay in the foreground while clients are connected)."
So it is a phone-served LAN endpoint. Nothing leaves your network. But the agent can only reach it while the app is open and the phone is on the same network, and every query is a live call to a device that a locked screen puts to sleep.
The other architecture: a local stdio server
Our MCP server is the opposite shape: a zero-dependency Node program, MIT licensed and open source, that the agent launches over stdio. No socket, no port, no bearer token on your Wi-Fi. The iOS app writes a small JSON snapshot to a destination you choose, and the server reads that folder. Pick iCloud Drive and the OS syncs it to your Mac:
{
"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"
}
}
}
}The server exposes 16 read-only tools, including get_mcp_status, get_health_metrics, get_trends, compare_periods, resolve_metric, and get_freshness. The trade is explicit: a snapshot is a snapshot, so get_freshness flags the export as stale after 26 hours by default and the agent can say "this is a day old" rather than quietly answering from yesterday. The full tool list lives on the MCP docs page.
Side by side
| Question | Integrated MCP in the app (Health Auto Export) | Local stdio server (MetricBridge) |
|---|---|---|
| Where does the server run? | On the iPhone, inside the app | On your computer, launched by the agent |
| How does the agent reach it? | LAN endpoint, HTTP or TCP, bearer token | stdio, no network calls |
| Phone requirement | App must stay in the foreground, phone reachable on the same network | None once the snapshot has synced |
| Staleness signalling | Live connection: nothing to signal | get_freshness, stale after 26h by default |
| Metrics | 150+ | 190 |
| Cost | IAP ladder: a Basic tier, Premium Annually, and a Premium Lifetime tier at $24.99 | One $24.99 one-time unlock, everything included |
Read the cost row: the incumbent's Premium Lifetime is also $24.99, so a one-time price is now the category norm. The difference is what the unlock covers. Ours is one purchase for the whole product: export, local MCP setup, on-device Ask and Pro Chat, and the Weekly Brief. Nothing is metered, and there is no recurring option to fall into.
One correctness difference worth knowing
The incumbent also has an open data-quality hazard, documented in its public issue #56: an app that backfills historical samples stamps them with a recent HealthKit write time, so a snapshot built on "changes since last sync" never recomputes those past days, leaving quiet gaps in older summaries. Our 1.10 release ("Past days stay correct") recomputes the day a backfilled sample belongs to.
How to check any app's MCP claim in five minutes
Three questions, no marketing required:
- Where does the server run? On the phone inside the app, or as a separate program on your computer?
- How does the agent reach it? A network endpoint you dial, or a local process the agent launches?
- What happens when the phone is locked or backgrounded? If the answer is "it has to be open," that is your real-world failure mode.
What we are not claiming
This compares architectures, not fitness: for a live dashboard on the same Wi-Fi, a phone-served endpoint is a perfectly good answer. And the product describes and computes from your own data. It does not diagnose, detect, treat, or monitor any condition, and where a number moves away from your recent range the language is deviation from your personal baseline. Wellness, not medical advice.
A local MCP server, and on-device answers
Ask your Apple Health data anything on the iPhone and see the numbers behind every answer, then export 190 metrics as local JSON to a zero-dependency MCP server. One purchase covers it all: $24.99 one-time, no subscription.
Frequently asked questions
What does "integrated MCP Server" mean in an app listing?
It means the MCP server runs inside the phone app rather than on your computer. Clients connect to an endpoint the app opens, usually over HTTP with a bearer token, and the app has to be running and reachable to answer.
Does Health Auto Export's MCP server send my data to the cloud?
By its own documentation the server runs on the iOS device and serves clients on your local network, so traffic stays on your LAN. The limits are that the phone must stay foregrounded and access is a network endpoint, not a local file.
What is the difference between a LAN HTTP MCP server and a local stdio server?
A LAN server opens a socket in the app and the agent dials it over Wi-Fi, so the phone must be on. A local stdio server is a program on your computer the agent launches over standard input and output, with no network calls, reading a snapshot that already synced.
Can the MCP server keep working when my iPhone is locked?
A phone-served endpoint depends on the app staying foregrounded, so a locked phone is the failure case. A local stdio server reads a snapshot that already synced, so it works whether or not the phone is awake, and reports the snapshot's age.
Is MetricBridge's MCP server free?
Yes. The health-export-mcp server is open source and MIT licensed. MetricBridge is one $24.99 one-time unlock covering the whole app: export, MCP setup, on-device Ask and Pro Chat, and the Weekly Brief. No subscription, nothing metered.
How do I check any app's MCP claim in five minutes?
Ask three questions: does the server run on the phone or your computer, does the agent reach it over a network endpoint or a local file, and what happens when the phone is locked? The answers tell you the architecture faster than any feature list.