Apple Health MCP: options compared
Which approach fits my destination and runtime?
Apple Health lives on your iPhone. MCP lets an AI client call tools, but does not itself move data off the phone. Start with these four transfer approaches, then compare the named projects below. Implementations vary; check the one you choose.
| Approach | Data destination | Setup | Ongoing delivery | Runtime | Write permissions | Limitations |
|---|---|---|---|---|---|---|
| File/XML export | Files you copy to a computer or service | Export from Health, then parse or import | Repeat exports yourself unless a separate tool automates them | A parser; an MCP wrapper if your client needs one | An export alone grants no write access | Snapshots become stale; file formats need parsing |
| Vendor-hosted/cloud MCP | The provider's infrastructure and whichever model receives tool output | Provider account, phone permissions and connector setup as required | Depends on the provider's phone app and service | The provider runs the server; you need a compatible client | Depends on the implementation and your Health permissions | Check retention, model sharing, supported types and availability with the provider |
| LAN/local services | A machine on your own network | A phone app or bridge plus a local receiver; optionally an MCP wrapper | Requires the phone to reach the service; background work depends on iOS | Your receiver and, if used, MCP server must run | Depends on the bridge and permissions you allow | LAN reachability, phone restrictions and local service uptime still apply |
| Syncky local agent | Your computer or server; client health-data envelopes pass through a sealed relay queue | Install the agent, pair the iPhone and select types | Agent polls Relay; iPhone syncs when iOS permits | Node.js 22.15 or newer, a receiver and your MCP client | Only supported types the owner allowed for writing in the app, with Health write permission; applied at the next sync; source is marked | Hosted Syncky Relay is part of this route; delivery is not real time and queued envelopes expire |
Which named projects offer these routes?
Checked on 7 November 2026. US prices, checked 2026-11-07. These are documented capabilities, not device tests or a ranking. Links lead to project documentation or US App Store listings. Hosting, AI-client plans and any separate export app can cost extra. A dash means the fact was not confirmed.
Prices and availability may differ by region.
| Project | Architecture | Writes to Apple Health | Price (US) | Checked |
|---|---|---|---|---|
| Marrow: on-iPhone MCP | LAN server on the iPhone; answers only while Marrow is open in front | Yes, with Allow AI write; see supported entries below | Free (3 connections at a time) | 2026-11-07 |
| Marrow: self-hosted mirror | Self-hosted, MIT server; background pushes; plain HTTP, with a tunnel or HTTPS proxy for remote access | Yes, with Allow AI write; phone applies queued entries | Free (3 connections at a time) | 2026-11-07 |
| Marrow: Cloud MCP | Vendor cloud; a copy on Marrow's US server that Marrow says it could technically read but says it does not read it | Yes, with Allow AI write; phone applies queued entries | Pro: $4.99/mo, $34.99/yr or $59.99 lifetime; 7-day trial on monthly/yearly | 2026-11-07 |
| HealthKite | LAN; on-iPhone server while the app is open; Bonjour and TLS-PSK | No; read-only | Free | 2026-11-07 |
| health4ai | Export/sync to your Google Sheet or your Supabase project; local MCP for the database route | — | Free app and MIT server; database hosting separate | 2026-11-07 |
| vpetersson/apple-health-mcp-server | Export; imports Apple's XML into local DuckDB, serves MCP | No; read-only tools | Free MIT software | 2026-11-07 |
| PhilipAD/health-export-mcp | Export; local MCP reads MetricBridge files | No; event tools edit a separate file | Free MIT server; MetricBridge app separate | 2026-11-07 |
| Vaultbeat | E2E relay; ongoing encrypted sync to your computer/server; iOS 26+ | Documented Health write: State of Mind, when enabled; other write tools save to Vaultbeat's account | Pro: $9.99/mo, $29.99/yr or $74.99 lifetime; 3 free days of agent access after pairing | 2026-11-07 |
| athletedata | Vendor cloud; background sync through its iPhone app, currently in beta per its integration page | — | $9/mo or $69/yr; 7-day trial | 2026-11-07 |
| Health Auto Export MCP | LAN; local MCP queries the phone on the same Wi-Fi, with app open and phone unlocked | No Health write tools documented | Premium: $1.99/mo, $6.99/yr or $24.99 lifetime | 2026-11-07 |
| MetricBridge | Export; app updates files in iCloud Drive, a folder or your network; local MCP reads them | No | $24.99 once after a 7-day trial | 2026-11-07 |
| neiltron/apple-health-mcp | Export; reads Simple Health Export CSV files locally, not Apple's XML | No Health write tools documented | Free MIT server; exporter separate | 2026-11-07 |
| the-momentum/apple-health-mcp-server | XML export repository; imports Apple's XML into a database you run; README says it evolved into Open Wearables | No Health write tools documented | Free MIT software | 2026-11-07 |
| Syncky Health | E2E relay to your own agent, without a public URL; direct server route also available | Supported types on the app's device-wide per-type write allow-list; connection write settings and iOS Health permission; applies at sync | Free during launch; plans coming later | 2026-11-07 |
Marrow documents writes for meals, water, weight, workouts, sleep and mood, marked with the AI's name and removable with undo. Its Cloud MCP explanation says Marrow “could technically read” the US copy while it exists but says it does not read it. Local and self-hosted Marrow use different data destinations. Its Pro page defines the trial terms.
Vaultbeat also documents an encrypted relay route. Syncky's combination is end-to-end encryption to your own agent without a public URL, a device-wide per-type write allow-list, and an open protocol with test vectors. Write-back is available in other projects too. MetricBridge is the iPhone app that supplies files to PhilipAD/health-export-mcp; the table separates that app purchase from the free MCP server. The Health Auto Export row describes its LAN MCP path, not all its export options.
How do I use Syncky's local MCP server?
After pairing your iPhone, use npx -y @syncky/agent mcp. A compatible client can alternatively import syncky-health.mcpb from a matching release after checksum verification. See the guides for Claude Code, ChatGPT desktop (Mac and Windows), Codex CLI/IDE, Cursor installation, Claude Desktop, VS Code Copilot in agent mode, Windsurf Cascade, OpenClaw-style agents and all agent options for configuration files, startup and scope checks, permission limits and troubleshooting. ChatGPT desktop and Codex follow the shared read-only setup, with syncky_send and syncky_ack disabled in the client.
For servers, Home Assistant sensor setup, n8n authentication, tests and permitted replies, the Node-RED flow guide and InfluxDB 2 and Grafana guide use direct webhooks without MCP or agent pairing. Use the server contract for generic receiver formats, authentication and the canonical Node-RED and InfluxDB recipes.
Who receives plaintext and who sees metadata?
Syncky Relay sees delivery metadata (device ids, IP address, timing and size) and emits plaintext hub notices, but sees no health values. Client health-data envelopes are sealed end to end and queued until acknowledgment or retention expiry, at most 7 days. The local agent and direct server receive plaintext. A chosen model sees what the agent supplies. Encryption of the relay route does not hide that data from your chosen client or model.
The protocol and reference agent are open source. The iPhone app and Syncky's hosted service are separate; this is not a wholly self-hosted service. Read the Privacy Policy and your chosen model provider's terms before sharing.
Can I write back, and is delivery immediate?
Writes apply at the next sync for the types the owner allowed for writing in the app, with iOS Health permission. Only supported writable types can be used. HealthKit sync metadata identifies the requesting agent or server and command; Syncky Health is the writing app. iOS chooses background opportunities; Health reads require an unlocked iPhone. Samples can be hours old and writes wait for a sync. No route here removes the phone's scheduling restrictions.
See writing to Apple Health for formats, results and refusal reasons, or Apple Health API options for exports, Shortcuts and direct server delivery.
Syncky Health is free during launch; plans are coming later. Canonical pricing · FAQ. It is a transfer tool and gives no medical advice.