health-export-mcp — Apple Health MCP server for AI agents

Query your Apple Health data from Claude, ChatGPT, Cursor, OpenClaw, Hermes — and any other AI agent.

health-export-mcp is an open-source, zero-dependency Model Context Protocol (MCP) server that lets any MCP-compatible AI agent query your Apple Health / HealthKit data — 190 metrics as clean JSON — in plain language. Local-first, read-only, no accounts, and no developer server in the path. It's the open-source server for the Health Export AI iOS app.

Ask your agent: "Compare my HRV this week vs last week and tell me if I'm recovering." — it calls the tools and answers from your actual numbers.

What is health-export-mcp?

It's an MCP server that turns your Apple Health export into a tool your AI agent can query in natural language — HRV, sleep, resting heart rate, steps, workouts, VO₂ max, and 180+ more.

• Who it's for: anyone who wants their AI to reason over their real health data instead of a stale CSV.
• What it isn't: a cloud service. There's no developer server in the path — your data goes only where you point it.
• Setup: point the server at your exported data and add it to your AI client.

Try it with no iPhone needed: git clone https://github.com/PhilipAD/health-export-mcp.git && cd health-export-mcp && npm test writes a 14-day sample cache and exercises every tool.

Connect Apple Health to your AI agent — Quickstart

1. Get your Apple Health data flowing

The companion iOS app Health Export AI exports your Apple Health data — read-only, automatic, private. For this MCP server, export to a destination it can read:

Using a non-MCP tool (ChatGPT, n8n, Home Assistant)? The app can also POST to a webhook those tools read directly — see Works with.

2. Add the server to your agent

Fastest — auto-configure:

git clone https://github.com/PhilipAD/health-export-mcp.git
cd health-export-mcp
node apply-mcp-config.mjs     # detects installed clients and writes the config for you

Manual — Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "health-export": {
      "command": "node",
      "args": ["REPLACE_WITH_ABSOLUTE_PATH/server.mjs"],
      "env": { "HEALTH_DATA_DIR": "~/Library/Mobile Documents/iCloud~ai~healthexport~app/Documents" }
    }
  }
}

Get the absolute path to paste above: node -e "console.log(process.cwd()+'/server.mjs')" (run inside the repo). Or skip JSON entirely — drag health-export.mcpb into Claude Desktop → Settings → Extensions.

Cursor / VS Code: node gen-deeplinks.mjs prints one-click install links. opencode / OpenClaw / Hermes: see AGENTS.md for the exact block — same shape, one per client.

3. Ask your agent

Restart the client and try:

"Use health-export: what's my average HRV this week vs last week?"

Works with Claude, Cursor, ChatGPT, OpenClaw, Hermes

_{*MCP clients query this server directly over stdio. ChatGPT / Gemini / Grok / n8n / Home Assistant don't speak MCP — they consume the same Apple Health data via the iOS app's token-authenticated webhook export.}

The 7 MCP tools

Coverage: 190 Apple Health metrics across activity, heart, HRV, mobility, respiratory, body, sleep, hearing, and nutrition — plus workouts.

Example AI queries

"What has my resting heart rate done over the last 30 days?"
"Compare my deep sleep this week vs last week."
"Is my VO₂ max trending up or down this quarter?"
"Give me a clean JSON export of HRV, RHR and sleep for the last 14 days."
"Correlate my step count with my sleep duration this month."

Use cases

• AI health coach — let an agent reason over your real HRV, resting heart rate, and sleep to suggest when to push and when to recover, grounded in your actual numbers instead of generic advice.
• Training-load analysis — pull workouts, VO₂ max, and heart-rate trends so your agent can flag overreaching, plot fitness progression, and pace a training block.
• Sleep correlations — have your agent correlate deep-sleep duration against steps, caffeine, late workouts, or screen time to find what actually moves your sleep quality.
• Quantified-self dashboards — feed clean JSON for any metric set and date range straight into a notebook, spreadsheet, or LLM-built dashboard for your own self-tracking.
• Personal research & experiments — run n-of-1 experiments (supplement, routine, or protocol changes) and let an agent compare before/after periods across 190 metrics to see what changed.

The app that feeds it

Privacy & security

• Read-only. The server only reads your exported data — it never touches HealthKit and never writes back.
• Local-first. It runs on your machine over stdio. There is no developer server in the path.
• Optional pairing. Set PAIRING_SECRET to the code the iOS app shows (Settings → Agent pairing) to gate access.
• Auditable. Zero dependencies and a few hundred lines of readable JavaScript — read every line.
• Signed releases. Hosted artifacts are minisign-signed and checksummed — see Verifying releases.

Verifying releases

The server artifacts hosted at healthexport.dev/mcp/ (used by the setup skill) are minisign-signed, and every download is SHA-256 checksummed. The signing public key is published in this repo (minisign.pub) and in SKILL.md — pin it from here, not only from the website, so a compromise of the website alone cannot swap both an artifact and its key.

PUBKEY='RWS6TxVWSKUblYkx7Db6ZpmvHALwHpznZpjaED/FlZj+PpxSlel0MxHZ'   # = minisign.pub in this repo
curl -fsSL https://healthexport.dev/mcp/SHA256SUMS         -o SHA256SUMS
curl -fsSL https://healthexport.dev/mcp/SHA256SUMS.minisig -o SHA256SUMS.minisig
minisign -Vm SHA256SUMS -P "$PUBKEY" || { echo "signature INVALID — do not run"; exit 1; }   # fail closed
curl -fsSL https://healthexport.dev/mcp/server.mjs -o server.mjs
shasum -a 256 --ignore-missing -c SHA256SUMS || { echo "checksum mismatch — do not run"; exit 1; }

The pinned, checksum-verified download above is the locked-down path. npx health-export-mcp instead resolves the latest version published to npm at run time (npm provides its own package integrity). Full security overview: https://healthexport.dev/security. Report vulnerabilities to security@healthexport.dev.

Requirements

• Node.js ≥ 18 (node -v).
• A folder containing a .health-cache.json exported by Health Export AI — or run npm test to generate a sample one.
• An MCP-compatible client (Claude Desktop, Cursor, opencode, OpenClaw, Hermes, VS Code) — or any tool that can read the webhook export.

FAQ

How do I get my Apple Health data into Claude / ChatGPT / my AI agent? Install health-export-mcp, export your Apple Health data with the Health Export AI iOS app (to iCloud, a folder, or your LAN), then add the MCP server to your AI client. Your agent can then query your Apple Health metrics in natural language. (Non-MCP tools like ChatGPT read the app's webhook export instead.)

Is my health data sent to a server? Not to us. The MCP server runs locally and reads only the export files or endpoints you configure — there's no developer server in the path. Where your iOS export is delivered (iCloud, your LAN, a webhook) is entirely your choice.

Which agents are supported? Any MCP client — Claude Desktop, Cursor, opencode, OpenClaw, Hermes, VS Code — natively. ChatGPT, Gemini, Grok, n8n, and Home Assistant consume the same data via webhook.

Do I need the iOS app? The app is the easiest way to get Apple Health data off your iPhone in the format this server reads. You can also point HEALTH_DATA_DIR at any folder containing a compatible .health-cache.json.

Troubleshooting

• "No metrics found" — confirm HEALTH_DATA_DIR points at the folder containing .health-cache.json, and that the app has exported at least once. Run get_mcp_status to see the resolved source and latest date.
• Server not visible in the client — use an absolute path to server.mjs, ensure Node ≥18, and fully restart the client.
• Locked data error — the export file is protected until first unlock after reboot; unlock your device once.

Run it locally

# Node ≥18, no install needed
HEALTH_DATA_DIR=~/Library/Mobile\ Documents/iCloud~ai~healthexport~app/Documents node server.mjs

# integration test — writes a 14-day sample cache and exercises every tool
npm test

stdio transport (newline-delimited JSON-RPC 2.0) — the universal MCP transport. Optionally set HEALTH_LISTEN=1 to also accept LAN pushes from the iOS app in the same process (see receiver.mjs).

How it works

The iOS app reads Apple Health (read-only) and writes a compact .health-cache.json to the destination you choose. This server reads that file and exposes the 7 tools above over MCP. No bridge, no Docker, no database — just a file and stdio.

Apple Health → Health Export AI (iOS) → .health-cache.json → health-export-mcp → MCP client → you

Related projects

Other Apple Health MCP servers in the ecosystem — worth a look depending on your setup:

• neiltron/apple-health-mcp — an MCP server that runs SQL-style queries over an Apple Health export.
• the-momentum/apple-health-mcp-server — an MCP server for analyzing Apple Health data exported from the Health app.
• HealthyApps/health-auto-export-mcp-server — an MCP server for the Health Auto Export app's data.

How health-export-mcp differs: zero dependencies, clean structured JSON, 190 Apple Health metrics, and the widest agent support (Claude, Cursor, opencode, OpenClaw, Hermes, VS Code natively — plus ChatGPT/Gemini/Grok/n8n/Home Assistant via webhook).

Related

• Companion iOS app: Health Export AI — exports 190 Apple Health metrics to your agent, automatically.
• Model Context Protocol: modelcontextprotocol.io
• Per-agent setup: AGENTS.md

If this helps your setup, a ⭐ makes it easier for others to find.

License

MIT — see LICENSE. Contributions welcome.

_{Apple Health MCP server · export Apple Health to AI · HealthKit MCP server · query Apple Health with Claude / ChatGPT / Cursor · Model Context Protocol health server · Apple Health to LLM · HRV, sleep & heart rate for AI agents.}