Your Clients' Own Apple Health Data, Privately

You want your clients' real numbers so you can coach them well. Your clients want useful answers without handing their most personal data to yet another platform. For fitness, running and wellness coaches, here is what MetricBridge does today, what is still in development, and how to hear when the coach workflow is ready.

By MetricBridge · Updated 17 October 2026 · ~6 min read

AI-assisted, human reviewed. How we use AI

Fitness, running and wellness coaches all hit the same wall. The data that would help you coach better (sleep, heart rate, steps, workouts) sits inside your clients' Apple Health, and many tools that read it ask the client to create an account and sync years of personal measurements to a vendor's server.

Clients push back, and they are right to. Health data is some of the most personal data there is. When the price of better coaching is "upload your whole health history to our cloud," you can lose the client who would benefit most.

The objection that decides it

"Where does my data go?" is not a checkbox. It is the whole decision. A client who trusts you with their training may still hesitate to upload their health history to a platform neither of you controls, especially one with a recurring fee they did not ask for.

The honest answer MetricBridge can give today: the export goes to the client's own iCloud Drive or a folder they choose, the MCP server runs on the client's own computer, and MetricBridge has no server in the data path. The client decides which AI agent reads it and what, if anything, they share with you.

What works today, for each client

1. The client installs the app once. The MetricBridge iOS app (a one-time $24.99 purchase, no account, no subscription) reads Apple Health read-only and exports 190 metrics as local JSON to iCloud Drive, a folder, a device on the local network, or a webhook the client sets up. No MetricBridge account, no upload to us.
2. The client's own AI agent reads it. The free, open-source health-export-mcp server runs on the client's computer, reads that local file, and gives their agent 16 read-only tools such as get_trends, compare_periods, get_sleep_sessions and get_workouts. The server itself makes zero network calls.
3. The client chooses what to share with you. Every answer shows the metric and date range it came from, so if a client sends you a summary, you can both see what it was computed from.

The privacy line, for you and your clients

• Read-only. The app reads Apple Health and does not write back. The MCP server's tools are read-only too.
• No MetricBridge server in the path. The MCP server makes zero network calls, and a client's health data never passes through any server we operate.
• The client holds the data. The full dataset stays with the client. Today there is no coach dashboard and no way for you to pull a client's data; you see only what they choose to share.
• Wellness, not medicine. MetricBridge is a wellness tool, not a medical device. Everything is framed as deviation from the client's personal baseline. Nothing is a diagnosis, a treatment, or a substitute for professional medical advice.

Our privacy commitments are scoped to the client's health data and to the MCP server. They are stated plainly in the privacy policy, and the server's behavior is open on GitHub.

What is coming next for coaches

We are developing a workflow for coaches who work with several clients, built on the same export and the same read-only server. We are also planning a small coaching pilot. Neither is available yet, there is no beta running, and we cannot promise dates or places.

The goal: you could ask a client's agent "show me the last two weeks of sleep against training load" and get an answer computed from their real data, with the numbers shown, instead of a hopeful self-report. Upcoming agent skills will be included in the existing purchase at no extra charge. If you coach and want to hear when this is ready, join the early-access list.