MetricBridge Apple Health changelog

https://raw.githubusercontent.com/philipad/health-export-mcp/HEAD/AGENTS.md

− ## Hermes− Add the same `health-export` block to your Hermes agent's MCP servers config, then restart the daemon.+ ## Hermes Agent+ Hermes Agent (Nous Research) reads MCP servers from `~/.hermes/config.yaml`. Add the entry under `mcp_servers` (merge it into the existing map if you already have one). Drop the `env` lines on a Mac using iCloud Drive:+ ```yaml+ mcp_servers:+   health-export:+     command: npx+     args: ["-y", "health-export-mcp"]+     env:+       HEALTH_DATA_DIR: /path/to/folder+ ```+ Check it with `hermes mcp test health-export`, then run `/reload-mcp` in Hermes (or start a new `hermes chat`). The tools appear as `mcp_health_export_<tool>`.

description

Ask your agent about your own Apple Health data: 194 metrics, 22 tools, local, 0 deps. → Ask your agent about your own Apple Health data: 194 metrics, 21 tools, local, 0 deps.

version

1.10.2 → 1.11.0

https://www.healthexport.dev/llms.txt

− > Health data (190 metrics) as a small local JSON file, which a zero-dependency− > VS Code, opencode, OpenClaw) can query it with read-only tools. Local-first,− The companion iOS app, which produces the 190 metrics this server reads, is on− - [Prompt library (prompts.mjs)](https://www.healthexport.dev/mcp/prompts.mjs): required module beside server.mjs; the 22 MCP prompts served over prompts/list and prompts/get.− - [Apple Health plus Oura and Whoop: What Works Today and What Is Coming](https://www.healthexport.dev/blog/one-private-health-picture-apple-health-oura-whoop): today the export includes Oura and Whoop data that reaches Apple Health, as one merged value per metric per day with no per-source breakdown; per-source reconciliation and vendor-score import are in development, not available yet.− - [Columnar vs Row JSON: Apple Health Export Size vs Context Window](https://www.healthexport.dev/blog/columnar-vs-row-json-apple-health-context-window): the arithmetic of what a 190-metric export costs an agent's context window as row JSON, and how a columnar shape changes the number.− - [Vaultbeat vs MetricBridge: Write-Back MCP and Encrypted Cloud Sync vs a Zero-Dependency Local Server](https://www.healthexport.dev/blog/vaultbeat-vs-metricbridge): an encrypted relay with agent write-back vs a local JSON snapshot read by a zero-dependency read-only server.− - [The Official MCP Registry Has Garmin, Oura and Whoop. Apple Health Is Missing.](https://www.healthexport.dev/blog/official-mcp-registry-apple-health-gap): what the official MCP Registry's Apple Health gap tells a buyer choosing a health MCP server.− - [Apple pulled its AI Health overhaul from iOS 27.2 beta 4 (2026-10-14)](https://www.healthexport.dev/blog/apple-pulled-ai-health-overhaul-ios-27-2-beta-4): the redesigned Apple Intelligence Health app left the fourth iOS 27.2 beta on 2026-10-13 and was re-timed to later in 2026 (MacRumors, 9to5Mac). What the delay changes for 2026 buyers, and what an on-device health AI can do today: answers computed on the iPhone with a provenance card, plus 190 metrics as local JSON and a zero-dependency MCP− - [Privacy](https://www.healthexport.dev/privacy): read-only, local-first, no health telemetry; the MCP server makes zero network calls, and the iOS app reports install, trial-start and purchase events to Meta for ad attribution (never health data, and only if the user allows tracking when iOS asks).+ > Health data (194 metrics) as a small local JSON file, which a zero-dependency+ > VS Code, opencode, OpenClaw) can query it with 22 MCP tools, 19 of them+ > read-only. Local-first,+ The companion iOS app, which produces the 194 metrics this server reads, is on+ - [Prompt library (prompts.mjs)](https://www.healthexport.dev/mcp/prompts.mjs): required module beside server.mjs; the 23 MCP prompts served over prompts/list and prompts/get.+ - [Export Apple Health to JSON: where your file goes](https://www.healthexport.dev/blog/export-apple-health-to-json-where-your-file-goes): three ways to get Apple Health data as JSON in 2026 (a browser converter, the free built-in route on your Mac, an on-device app) and where each one sends your file.+ - [Apple Health HRV and sleep trends in your AI agent](https://www.healthexport.dev/blog/apple-health-hrv-sleep-trends-ai-agent): the MCP tools that answer a trend question (get_trends, compare_periods, correlate_metrics, get_sleep_sessions), the one-line install, a worked HRV-and-sleep run with real output, and how to export the series to plot locally.+ - [MCP token scoping for a read-only Apple Health grant](https://www.healthexport.dev/blog/mcp-token-scoping-read-only-apple-health): what a read-only token should reach (one destination, read-only tools, daily summaries) and what it never should (the write path, GPS routes, raw samples, the network), with a scope test.+ - [On-device health AI apps with no agent bridge](https://www.healthexport.dev/blog/on-device-health-ai-apps-no-agent-bridge): a dozen-plus iPhone apps now answer Apple Health questions on device; we checked each for an MCP server or agent connection page (as of October 2026).+ - [Apple Health plus Oura and Whoop: What Works Today and What Is Coming](https://www.healthexport.dev/blog/one-private-health-picture-apple-health-oura-whoop): the export includes Oura and Whoop data that reaches Apple Health, and since 1.16 each value names the device it came from; vendor-score import is in development, not available yet.+ - [Columnar vs Row JSON: Apple Health Export Size vs Context Window](https://www.healthexport.dev/blog/columnar-vs-row-json-apple-health-context-window): the arithmetic of what a 194-metric export costs an agent's context window as row JSON, and how a columnar shape changes the number.+ - [MetricBridge compared](https://www.healthexport.dev/compare/): every comparison in one place, grouped into health AI apps, Apple Health MCP servers and connectors, and export formats, each with its date.+ - [Metrya vs MetricBridge: Recovery Scores vs an Apple Health Data Bridge](https://www.healthexport.dev/blog/metrya-vs-metricbridge): a recovery-score app with Watch and Mac apps and optional cloud AI keys, against on-device answers with provenance, full-history JSON export and an MCP server; a dated side-by-side table and where each is the better pick.+ - [Health Auto Export vs MetricBridge: Which Apple Health MCP Server Wins?](https://www.healthexport.dev/blog/health-auto-export-vs-metricbridge): Health Auto Export runs an MCP server on your iPhone over the LAN; MetricBridge runs one on your computer. Where each runs decides which fits your agent.+ - [Vaultbeat vs MetricBridge: Write-Back MCP and Encrypted Cloud Sync vs a Zero-Dependency Local Server](https://www.healthexport.dev/blog/vaultbeat-vs-metricbridge): an encrypted relay with agent write-back vs a local JSON snapshot read by a zero-dependency server that never edits health records.+ - [ghurt Made the Official MCP Registry With Garmin, Oura and Whoop, but Not Apple Health](https://www.healthexport.dev/blog/official-mcp-registry-apple-health-gap): a health MCP server listed on the Official Registry without Apple Health, and what that tells a buyer (health-export-mcp has been listed there since June 2026).+ - [Apple pulled its AI Health overhaul from iOS 27.2 beta 4 (2026-10-14)](https://www.healthexport.dev/blog/apple-pulled-ai-health-overhaul-ios-27-2-beta-4): the redesigned Apple Intelligence Health app left the fourth iOS 27.2 beta on 2026-10-13 and was re-timed to later in 2026 (MacRumors, 9to5Mac). What the delay changes for 2026 buyers, and what an on-device health AI can do today: answers computed on the iPhone with a provenance card, plus 194 metrics as local JSON and a zero-dependency MCP+ - [Sync to a server you own: the self-hosted receiver pattern (2026-11-02)](https://www.healthexport.dev/blog/self-hosted-apple-health-receiver-pattern): the push half of the export surface, in the receiver's own numbers. The real headers (X-MetricBridge-Type, X-MetricBridge-Schema v1, webhook-id, webhook-timestamp, webhook-signature, X-MetricBridge-Replay), a Standard Webhooks v1 HMAC-SHA256 verification snippet, the storage rules (upsert metrics on name plus date, delete-then-insert sleep sess+ - [Claude's Apple Health access is US-only and Pro-tier (2026-11-04)](https://www.healthexport.dev/blog/claude-apple-health-us-only-connector-route): Anthropic's built-in Apple Health sharing is beta, requires a Pro, Max or Ultra plan and is available in the US only (support.claude.com). What that leaves out, and the connector route that works in every country and on any plan: export Apple Health on the iPhone to a folder you own, point a local MCP server (open source, zero dependencies, no acco+ - [A remote MCP server vs a file on your Mac (2026-11-04)](https://www.healthexport.dev/blog/remote-mcp-server-vs-local-file): "your data never leaves your device" is a claim about a data path, not a badge. The two connector shapes (remote over Streamable HTTP, where the health data lives on a machine you do not own, versus local over stdio, which reads a file on your own machine), the one config detail that tells you which you installed (a command means local, a URL plus token means remote), fo+ - [Pass-through vs answer-on-device (2026-11-01)](https://www.healthexport.dev/blog/pass-through-vs-answer-on-device): two 2026 designs for health AI, side by side. A pass-through tool hands your agent raw samples and the model does the reading; an answer-on-device app computes the number on the phone first and shows a provenance card with the samples, date range and computation. Includes a recorded card from our own seeded 30-day series (HRV 7-day average 49.6 ms, up 16.3% vs the prior 14 days,+ - [Privacy](https://www.healthexport.dev/privacy): read-only, local-first, no health telemetry; the MCP server makes no outbound network calls, and the iOS app reports install, trial-start and purchase events to Meta for ad attribution (never health data, and only if the user allows tracking when iOS asks).+ - [Methods: how every number is calculated](https://www.healthexport.dev/methods/): the published method (version 2) behind the readiness estimate, HRV status, sleep shortfall, changes worth a look, fitness age, tag patterns, training load and heart-rate zones, the strength log, sleep regularity, tonight's bedtime and the Lab; every weight, window, threshold and limit, with references.+ - [Readiness: what the Today card shows](https://www.healthexport.dev/readiness/): the morning readiness estimate (50 = your usual) with its sensitivity range, HRV status against your own 60-day range, recent sleep shortfall, changes worth a look and tag patterns, each linked to its method; in the app since version 1.20.+ - [On-device AI: four ways Ask runs](https://www.healthexport.dev/on-device-ai/): Guided mode (no model), Apple's on-device model, a downloaded model, and Your Mac (Ollama on your own Mac over your Wi-Fi, since 1.20); the iPhone computes every number, a model only words the answer, no cloud AI and no API keys.+ - [Apple Watch app](https://www.healthexport.dev/watch/): the watch app and complications that show the Today card, included with the iPhone app since 1.20.+ - [MetricBridge for Mac](https://www.healthexport.dev/mac/): the Mac app (macOS 14 or later) that shows the iPhone's export on a big screen, included with the same purchase.+ - [Sample PDF reports](https://www.healthexport.dev/reports/): every page of the doctor summary and 12-month activity PDFs the app makes on the iPhone, generated by the app's own report code from synthetic data.+ - [Changelog](https://www.healthexport.dev/changelog/): every iOS release as Apple published it in the App Store version history, and every MCP server release.

https://raw.githubusercontent.com/philipad/health-export-mcp/HEAD/AGENTS.md

− `.health-cache.json`, by default the [MetricBridge](https://www.healthexport.dev) iOS app− One command, no clone:− claude mcp add --transport stdio health-export \−   --env "HEALTH_DATA_DIR=$HOME/Library/Mobile Documents/iCloud~ai~healthexport~app/Documents" \−   -- npx -y health-export-mcp− Keep the double quotes (the folder name contains a space). Add `--scope user` to use it in every project. No export yet: `claude mcp add --transport stdio health-export-demo -- npx -y health-export-mcp --demo` serves synthetic data.− `~/Library/Application Support/Claude/claude_desktop_config.json`:−       "command": "node",−       "args": ["/ABSOLUTE/PATH/TO/health-export-mcp/server.mjs"],−       "env": { "HEALTH_DATA_DIR": "~/Library/Mobile Documents/iCloud~ai~healthexport~app/Documents" }− Or drag `health-export.mcpb` into **Claude Desktop → Settings → Extensions** (no JSON).− `opencode.json` (project root) or `~/.config/opencode/opencode.json`:−       "command": ["node", "/ABSOLUTE/PATH/TO/health-export-mcp/server.mjs"],−       "environment": { "HEALTH_DATA_DIR": "~/Library/Mobile Documents/iCloud~ai~healthexport~app/Documents" }− Add the `health-export` block (same shape as Claude Desktop's `mcpServers` entry) to your OpenClaw MCP servers config, then reload.− Add the `health-export` block to your Hermes agent's MCP servers config, then restart the daemon.− These don't speak MCP, so they don't use this server. Instead, the [MetricBridge](https://www.healthexport.dev) app **POSTs your data to a webhook** (or your own endpoint) and your automation/agent reads that JSON. Every delivery is token-authenticated.+ `.health-cache.json` (on a Mac, since 1.7.3, the server finds the app's iCloud folder by itself when it's unset), by default the [MetricBridge](https://www.healthexport.dev) iOS app+ One command, no clone, no environment variable on a Mac (1.7.3 finds the app's iCloud Drive folder itself):+ claude mcp add health-export -- npx -y health-export-mcp+ Windows, Linux, or an export outside iCloud Drive:+ ```bash+ claude mcp add health-export --env "HEALTH_DATA_DIR=/path/to/folder" -- npx -y health-export-mcp+ ```+ Keep the double quotes if the path has a space. Add `--scope user` to use it in every project. No export yet: `claude mcp add health-export-demo -- npx -y health-export-mcp --demo` serves synthetic data. If Agent pairing is on, do not pass `PAIRING_SECRET` on the command line (shell history, `ps`); add it to the entry's `env` in the config file.+ Easiest: download [`health-export.mcpb`](https://github.com/PhilipAD/health-export-mcp/releases/latest/download/health-export.mcpb) and open it, or drag it into **Claude Desktop → Settings → Extensions**. Desktop runs it with its own Node, so there's no JSON and nothing to put on your PATH.+ Or edit `~/Library/Application Support/Claude/claude_desktop_config.json`:+       "command": "npx",+       "args": ["-y", "health-export-mcp"]+ On a Mac the server reads the app's iCloud Drive folder when `HEALTH_DATA_DIR` isn't set (1.7.3+). If Desktop logs `spawn npx ENOENT`, its PATH can't see Node (common with nvm or Homebrew): set `"command"` to the full path from `which npx`, or use the `.mcpb`. To pin a vetted local checkout instead, use `"command": "node", "args": ["/ABSOLUTE/PATH/TO/health-export-mcp/server.mjs"]`.+ `opencode.json` (project root) or `~/.config/opencode/opencode.json`. Drop the `environment` line on a Mac using iCloud Drive; for a pinned checkout use `["node", "/ABSOLUTE/PATH/TO/server.mjs"]`:+       "command": ["npx", "-y", "health-export-mcp"],+       "environment": { "HEALTH_DATA_DIR": "/path/to/folder" }+ Add the `health-export` block (same shape as Claude Desktop's `mcpServers` entry: command `npx`, args `["-y", "health-export-mcp"]`, plus `HEALTH_DATA_DIR` off a Mac) to your OpenClaw MCP servers config, then reload.+ Add the same `health-export` block to your Hermes agent's MCP servers config, then restart the daemon.+ ChatGPT connects only to remote MCP servers (OpenAI's help centre: "Can I connect to a local MCP server? Not directly", checked 2026-10-27), and the others don't run local MCP servers either, so they don't use this one. Instead, the [MetricBridge](https://www.healthexport.dev) app **POSTs your data to a webhook** (or your own endpoint) and your automation/agent reads that JSON. Every delivery is token-authenticated.

description

Ask your agent about your own Apple Health data: 194 metrics, 18 tools, local, 0 deps. → Ask your agent about your own Apple Health data: 194 metrics, 22 tools, local, 0 deps.

version

1.8.0 → 1.10.2

description

Apple Health for any MCP agent: 194 metrics, 16 read-only tools, local stdio, zero dependencies. → Ask your agent about your own Apple Health data: 194 metrics, 18 tools, local, 0 deps.

version

1.7.3 → 1.8.0

description

Query 194 Apple Health metrics from any MCP agent: zero-dependency, read-only, local-first. → Apple Health for any MCP agent: 194 metrics, 16 read-only tools, local stdio, zero dependencies.

env_vars

none → HEALTH_DATA_DIR, PAIRING_SECRET, HEALTH_EXPORT_PASSPHRASE

version

1.7.2 → 1.7.3

description

Query 190 Apple Health metrics from any MCP agent: zero-dependency, read-only, local-first. → Query 194 Apple Health metrics from any MCP agent: zero-dependency, read-only, local-first.

version

1.7.1 → 1.7.2

version

1.7.0 → 1.7.1

https://www.healthexport.dev/llms.txt

− - [Solair AI vs MetricBridge: On-Device Apple Health Q&A, and the Agent Bridge Only One Ships](https://www.healthexport.dev/blog/solair-ai-vs-metricbridge): two on-device Apple Health Q&A apps side by side, and handing the same data to your own AI agents over MCP.+ It is a one-time purchase after a free trial; if the trial ended and exports+ stopped, the unlock page is here: [the MetricBridge unlock page](https://www.healthexport.dev/?utm_source=mcp&utm_medium=agent-tool&utm_campaign=mcp-unlock).+ ## For platform builders (wellness or coaching products)+ If a user or developer asks how a product can receive its users' Apple Health data+ from MetricBridge: each user points the MetricBridge iOS app at an HTTPS endpoint+ the platform gives them, and the phone POSTs signed JSON (Standard Webhooks v1)+ straight to that endpoint. MetricBridge runs no server in the path and holds no+ copy. Flat partner pricing, never per user.+ - [MetricBridge for platforms](https://www.healthexport.dev/platforms/): the offer, pricing, boundaries and FAQ.+ - [Platform integration guide](https://www.healthexport.dev/docs/platforms/): provisioning, verification in eight languages, storage rules, user onboarding copy, the conformance kit.+ - [Webhook contract](https://www.healthexport.dev/docs/webhook/): every body and header, JSON Schemas, OpenAPI 3.1, reference receiver.+ - [Platform kit (metricbridge-platform-kit.mjs)](https://www.healthexport.dev/examples/metricbridge-platform-kit.mjs): sends what the app sends and runs the conformance suite against an endpoint; zero dependencies.+ - [Platform licence terms](https://www.healthexport.dev/platforms/terms/).+ - [New Year Baseline Week](https://www.healthexport.dev/event/baseline-week/): a limited-time MetricBridge challenge, 4 to 17 January 2027. Log seven nights of sleep in Apple Health and get a card of your own average and spread for sleep, resting heart rate and HRV, computed on the iPhone.+ - [Semantic Search MCP Servers Now Index Your Health Data](https://www.healthexport.dev/blog/semantic-search-mcp-health-data-retrieval): a new class of Apple Health MCP server embeds the export into a vector store; what similarity search adds, why numeric questions still need deterministic computation, and what the second pipeline costs.+ - [Solair AI vs MetricBridge: On-Device Apple Health Q&A, and the Agent Bridge](https://www.healthexport.dev/blog/solair-ai-vs-metricbridge): two on-device Apple Health Q&A apps side by side, and handing the same data to your own AI agents over MCP.+ - [The On-Device AND Agent-Connectable Venn Diagram](https://www.healthexport.dev/blog/on-device-and-agent-connectable-venn-diagram): on-device and agent-connectable are two separate claims, most Apple Health AI apps hold only one, and the four quadrants tell you which overlap you are actually buying.+ - [Bevel's Users Filed an MCP Request: 1.0k Votes, Still Under Review](https://www.healthexport.dev/blog/bevel-mcp-feature-request-agent-gap): Bevel's own feedback board carries a Claude connector / MCP request with 1.0k votes, open since February 2026; what that demand says about the agent gap in cloud health coaches.+ - [Apple Health API Pricing in 2026: What the Cloud APIs Charge vs a Flat Fee](https://www.healthexport.dev/blog/apple-health-api-pricing): the published entry tiers of the cloud health-data relays ($299 to $499 a month plus user caps) versus MetricBridge's flat annual fee with no vendor in the data path.

version

1.6.8 → 1.7.0

https://raw.githubusercontent.com/philipad/health-export-mcp/HEAD/AGENTS.md

− ([App Store](https://apps.apple.com/app/apple-store/id6784185201?pt=129083290&ct=githubreadme&mt=8)) writes it to your iCloud Drive container:+ ([App Store](https://apps.apple.com/app/apple-store/id6784185201?pt=129083290&ct=githubreadme&mt=8&ppid=2c28f88a-d94f-48f9-8e6a-74a8d89ce66e)) writes it to your iCloud Drive container:

version

1.6.7 → 1.6.8

https://www.healthexport.dev/llms.txt

− - [App Store](https://apps.apple.com/app/apple-store/id6784185201?pt=129083290&ct=agentfile&mt=8): download the MetricBridge iOS app (the app that exports your Apple Health to the local JSON this MCP server reads).+ The companion iOS app, which produces the 190 metrics this server reads, is on+ the App Store: [MetricBridge on the App Store](https://apps.apple.com/app/apple-store/id6784185201?pt=129083290&ct=agentfile&mt=8&ppid=2c28f88a-d94f-48f9-8e6a-74a8d89ce66e).+ Full plain-text corpus (every page in one file, generated from the live pages):+ [llms-full.txt](https://www.healthexport.dev/llms-full.txt).+ ## Guides (how to get Apple Health data into an agent)+ - [Query Apple Health with ChatGPT and Cursor](https://www.healthexport.dev/blog/query-apple-health-with-chatgpt-cursor): the two ways to use Apple Health data with AI: query it directly from a native MCP client like Cursor, or push it to ChatGPT, Gemini and Grok via webhook export.+ - [Export Apple Health to JSON for AI agents](https://www.healthexport.dev/blog/export-apple-health-to-json-with-ai): clean JSON your AI agent (Claude, Cursor, etc.) can read over MCP; why XML and CSV fail for LLMs, plus 5 example prompts.+ - [Apple Health export.xml to JSON converter guide](https://www.healthexport.dev/blog/apple-health-export-xml-to-json-complete-guide): handle 1.8GB+ export.xml files, streaming vs DOM parsers, Python scripts, browser tools, and the one-click iOS solution.+ - [Apple Health export.xml is too big: what to do](https://www.healthexport.dev/blog/apple-health-export-xml-too-big): why the export is so large, and three ways to get usable data out of it (two of them free).+ - [Connect Apple Health to Claude via MCP](https://www.healthexport.dev/blog/connect-apple-health-to-claude-mcp): the exact Claude Desktop config, the .mcpb one-click install, plus Cursor, opencode, OpenClaw and Hermes.+ - [Fix Apple Health export.xml parse errors (complete guide)](https://www.healthexport.dev/blog/fix-apple-health-export-xml-parse-errors-complete-guide): the iOS 16+ 'ATTLIST: no name for Attribute' error, DTD fixes, 1.7GB+ files, and the Python/R/Go tools that fail.+ - [Best Apple Health MCP servers compared (2026)](https://www.healthexport.dev/blog/best-apple-health-mcp-servers-compared-2026): health-export-mcp (zero-dep), the-momentum (DuckDB), Health Auto Export (TCP), neiltron (npm). Setup time, tools, dependencies, privacy.+ - [Connect Apple Health to Cursor via MCP](https://www.healthexport.dev/blog/connect-apple-health-to-cursor): the exact mcp.json config (global and per-project), the MCP panel, troubleshooting, and real health-data queries.+ - [Automate Apple Health export for AI agents](https://www.healthexport.dev/blog/automate-apple-health-export-for-ai-agents): stop exporting by hand with a background export to clean JSON fed live to your agent over a zero-dependency MCP server.+ - [Connect Apple Health to opencode: Native MCP Setup](https://www.healthexport.dev/blog/connect-apple-health-to-opencode-mcp): the exact opencode.json MCP block: local server config, environment variables, tool-name scoping with globs, and real health queries in the TUI.+ - [Connect Apple Health to ChatGPT via Webhook](https://www.healthexport.dev/blog/connect-apple-health-to-chatgpt-via-webhook): the webhook endpoint setup, the JSON payload your iPhone sends, real prompt examples, and the full ChatGPT conversation.+ - [Query Apple Health with Any AI Agent: Multi-Client MCP Setup Guide (2026)](https://www.healthexport.dev/blog/query-apple-health-with-any-ai-agent): one zero-dependency MCP server for Claude Desktop, Claude Code, Cursor, ChatGPT Desktop, Windsurf, Codex CLI, opencode and any MCP-aware agent, with real config and queries.+ - [Run Apple Health Data with Your Local LLM (Ollama + MCP)](https://www.healthexport.dev/blog/run-apple-health-data-with-local-llm-ollama-mcp): Ollama does not speak MCP, so this points a local model at your Apple Health data through an MCP client: Goose, LM Studio, mcphost and Open WebUI.+ - [Local-First Health Analytics with Claude Code](https://www.healthexport.dev/blog/local-first-health-analytics-with-claude-code): write and run real scripts against your own local Apple Health export, with no upload, no account, and no cloud in the path.+ - [Let Your AI Agent Read Your Apple Health, Privately](https://www.healthexport.dev/blog/let-your-ai-agent-read-your-apple-health-privately): the local bridge that gives Claude, ChatGPT and Cursor your real Apple Health data with one command, no account, no MetricBridge server in the path, plus the early-access list for upcoming features (in development).+ - [Apple Health plus Oura and Whoop: What Works Today and What Is Coming](https://www.healthexport.dev/blog/one-private-health-picture-apple-health-oura-whoop): today the export includes Oura and Whoop data that reaches Apple Health, as one merged value per metric per day with no per-source breakdown; per-source reconciliation and vendor-score import are in development, not available yet.+ - [Your Clients' Own Apple Health Data, Privately: A Guide for Coaches](https://www.healthexport.dev/blog/private-health-ai-for-coaching-clients): for fitness, running and wellness coaches, how a client can let their own AI agent read their Apple Health data today; a multi-client coach workflow and pilot are planned, not available yet.+ ## Explainers+ - [Apple Health for AI: JSON vs CSV vs XML](https://www.healthexport.dev/blog/apple-health-json-vs-csv-xml-for-ai): the three export formats compared on LLM-readability, schema, size, tooling and privacy, and why clean JSON over MCP works best.+ - [Why Your Apple Health Export Has Silent Gaps](https://www.healthexport.dev/blog/apple-health-export-silent-gaps): backfilled samples, deletions and locked-day reads leave holes that date-based cursors miss, plus the MCP calls that show the gaps in your own file.+ - [Best MCP Servers for Health Data in 2026: A Buyer's Guide](https://www.healthexport.dev/blog/best-mcp-servers-for-health-data): which MCP server to run for Apple Health, Oura, Whoop or Garmin data: zero-dep vs DuckDB vs cloud, with selection criteria.+ - [Apple Health Age and Readiness Score Explained: What iOS 27 AI Insights Compute and What They Leave Out](https://www.healthexport.dev/blog/apple-health-age-readiness-score-explained): what the iOS 27 Health Age and 0 to 10 readiness score compute, what Apple has not disclosed, and how MetricBridge shows the numbers behind an answer.+ - [How to Keep Your Apple Health Data Private When Using AI Agents (Local vs Cloud)](https://www.healthexport.dev/blog/apple-health-data-privacy-with-ai-agents): how local-first MCP servers and on-device health AI keep Apple Health data private compared with cloud alternatives.+ - [Apple Health AI Apps That Actually Respect Your Privacy: On-Device vs Cloud Comparison (2026)](https://www.healthexport.dev/blog/apple-health-ai-apps-privacy-on-device-vs-cloud): which health AI apps process Apple Health data locally, which send it to servers, and which also bridge to your AI agents via MCP.+ - [Why On-Device Health AI Apps Need an MCP Bridge: And Which Ones Have One](https://www.healthexport.dev/blog/why-on-device-health-ai-apps-need-an-mcp-bridge): without an MCP bridge, on-device health data is locked away from the AI agents you already use; why MCP matters and which apps ship it.+ - [On-Device Health AI That Actually Answers Questions: No Cloud, No Upload](https://www.healthexport.dev/blog/on-device-health-ai-answers-questions-no-cloud): answers questions about your Apple Health data (HRV, sleep, steps, trends) on the iPhone without sending it to the cloud, and every answer shows its numbers.+ - [Which AI Plans Can Add an Apple Health MCP Server? (2026 Matrix)](https://www.healthexport.dev/blog/apple-health-mcp-server-plan-eligibility): the plan-eligibility matrix across Claude and ChatGPT tiers: which plans let an agent read your Apple Health, and the desktop path that skips the request quota.+ - [Columnar vs Row JSON: Apple Health Export Size vs Context Window](https://www.healthexport.dev/blog/columnar-vs-row-json-apple-health-context-window): the arithmetic of what a 190-metric export costs an agent's context window as row JSON, and how a columnar shape changes the number.+ - [MCP Trust Scanners Now Grade Apple Health Servers](https://www.healthexport.dev/blog/how-mcp-servers-get-trusted-verify-mcp-and-ext-ops-panel): what VerifyMCP and the Ext Ops Panel read when they score a published MCP server, and the checks to run yourself.+ ## Comparisons+ - [ChatGPT Health vs On-Device Health AI: What Actually Leaves Your iPhone](https://www.healthexport.dev/blog/chatgpt-health-vs-on-device-health-ai): cloud processing vs on-device computation, and exactly what leaves the device in each.+ - [Claude Now Connects to Apple Health Natively: Cloud Sync vs On-Device MCP](https://www.healthexport.dev/blog/claude-native-apple-health-vs-on-device-mcp): Claude's native Apple Health connector syncs to the cloud; what leaves your phone, and the on-device MCP alternative that keeps data local.+ - [Health Auto Export's "Integrated MCP Server" vs a Local Server](https://www.healthexport.dev/blog/health-auto-export-integrated-mcp-vs-local-server): what the integrated MCP Server listing describes (a LAN server in the app) versus a zero-dependency local stdio server.+ - [iOS 27 Health App vs MetricBridge: Apple Intelligence Insights vs an On-Device Agent You Can Interrogate](https://www.healthexport.dev/blog/ios-27-health-app-vs-metricbridge): Apple Intelligence summaries, readiness score and Health Age compared with on-device answers that show the exact numbers, plus an MCP bridge.+ - [Marrow vs MetricBridge: On-Phone MCP vs a Zero-Dep Local Server](https://www.healthexport.dev/blog/marrow-vs-metricbridge): read-only Apple Health tools served from the iPhone over your LAN vs a JSON export your agent reads over stdio; two local designs compared.

version

1.6.6 → 1.6.7

https://raw.githubusercontent.com/philipad/health-export-mcp/HEAD/AGENTS.md

− ([App Store](https://apps.apple.com/app/id6784185201)) writes it to your iCloud Drive container:+ ([App Store](https://apps.apple.com/app/apple-store/id6784185201?pt=129083290&ct=githubreadme&mt=8)) writes it to your iCloud Drive container:+ ## Claude Code+ One command, no clone:+ ```bash+ claude mcp add --transport stdio health-export \+   --env "HEALTH_DATA_DIR=$HOME/Library/Mobile Documents/iCloud~ai~healthexport~app/Documents" \+   -- npx -y health-export-mcp+ ```+ Keep the double quotes (the folder name contains a space). Add `--scope user` to use it in every project. No export yet: `claude mcp add --transport stdio health-export-demo -- npx -y health-export-mcp --demo` serves synthetic data.

version

1.6.3 → 1.6.6

version

1.6.2 → 1.6.3

version

1.6.1 → 1.6.2

title

health export mcp → MetricBridge Apple Health

version

1.6.0 → 1.6.1

website_url

— → https://www.healthexport.dev/mcp/

version

1.5.0 → 1.6.0

version

1.4.3 → 1.5.0