Apple Watch MCP · Apple Health MCP
Ask AI about your Apple Health data
Connect your uploaded Apple Watch and Apple Health records to Claude, the Codex app, or another compatible AI client with HealthExport MCP. Add the server URL, sign in with Apple, and approve read-only access. No Terminal setup required.
Works with compatible MCP clients
Remote required for uploads
Read-only access
URL + Apple sign-in
fetch_aggregated_health_data
Illustrative prompt · No customer data shown
Apple Watch data, through Apple Health
What an Apple Watch MCP actually connects to
Your Apple Watch writes health and fitness measurements into Apple Health on your iPhone. HealthExport reads the types you authorize and makes your latest synced records available to your AI assistant through the Model Context Protocol (MCP).
Apple Watch
Records measurements
Apple Health
Stores authorized data
Remote sync
Uploads encrypted records
Hosted MCP
Reads with your consent
AI assistant
Answers your question
The MCP does not connect directly to your watch or stream live sensor data. It queries the latest data HealthExport has synced from Apple Health.
Ask better questions
Explore your own health and fitness history
Instead of uploading another large export, ask for the metric and time range you need.
“Show my uploaded step totals by day for the last three days.”
“Which health data types can HealthExport read?”
“Show my uploaded workout records from yesterday.”
“Show my uploaded sleep records from last night.”
“Summarize my uploaded activity for the last week, and tell me if data is missing.”
“Which available activity types support daily totals?”
Each query supports up to 7 days, 4 health types and 2,000 input records. Larger requests must be narrowed. Totals are available only for eligible numeric types. HealthExport provides data access, not diagnosis or treatment.
More than workouts
Query the Apple Health types you choose to share
Explore the supported activity, heart, sleep, body measurement, nutrition and workout types you have uploaded. The catalog lists supported types; it does not mean every type has records in your account.
See supported health typesActivitySteps, distances, exercise and energy
HeartHeart rate, resting rate and HRV
SleepSleep duration and stages
WorkoutsSessions, duration and workout metrics
BodyWeight, BMI and body measurements
VitalsBlood pressure, oxygen and more
Built for repeat questions
Why use an Apple Health MCP instead of another XML export?
| Workflow | Apple’s XML export | HealthExport MCP |
|---|---|---|
| Getting fresh data | Repeat a manual full export | Use regularly synced Remote data |
| Choosing scope | One large archive | Request specific types and dates |
| Using it again | Upload and explain the file again | Ask another bounded question |
| Decryption | Not applicable | Runs in server memory with consent |
Choose your connection
Two ways to use your health data with AI
Connect an AI assistant with MCP, or use the CLI for agents and scripts. Both require HealthExport Remote for iPhone-to-cloud uploads. Your AI provider’s account requirements also apply.
MCP: connect your AI assistantA server URL and Apple sign-in. No Terminal setup.
- 1
Upload your records with Remote
In HealthExport on your iPhone, enable Remote, sign in with Apple and finish the initial upload. Grant Apple Health access for the types you want to use.
Get HealthExport - 2
Add the server URL in your AI client
Codex app: Open Settings → MCP servers, add a remote server with the URL above, and follow the authentication steps.
Claude: Open Customize → Connectors → + → Add custom connector and paste the URL. Organization accounts may need an owner to add it first.
Other MCP clients: Add a remote MCP server using the URL above. Your client needs Streamable HTTP and browser-based OAuth sign-in support.
- 3
Sign in with Apple and approve access
Use the same Apple account you use for HealthExport. Review the client and read-only permission, then choose Allow. You do not need to install the CLI or paste your account key.
- 4
Ask about your uploaded records
Enable the connection in your AI client and ask about your uploaded records. If records are missing, check your permissions and use Remote → Manual data upload on your iPhone.
MCP reads previously uploaded records. It cannot trigger an iPhone sync, and background upload timing depends on iOS. Client support and connector availability can vary.
CLI: work with agents and scriptsStructured JSON or CSV for terminal and automation workflows.
Use the open-source he CLI with coding agents such as Codex and Claude Code, or your own scripts. It fetches encrypted Remote records and decrypts them on your computer.
- Install the CLI using the instructions linked below.
- Run
he auth loginand enter your HealthExport account key when prompted. - Follow the CLI guide to fetch the records you need as JSON or CSV.
When used with an AI assistant, requested results still go to that client. Treat your account key like a password; unlike a hosted MCP grant, a shared account key cannot currently be revoked or rotated.
CLI installation and usage
Know what you share
Read-only access, with your consent
HealthExport Remote stores encrypted records. When you connect an AI assistant, the hosted MCP service decrypts requested records in server memory and sends the results to your AI client and its provider.
You approve the connection. Sign in with Apple and review the named client before allowing access.
Customer decryption keys are not stored in the MCP database. Decryption material is present in server memory during use.
All four tools are read-only. They cannot change your health records or trigger an iPhone sync.
Your AI service receives requested results. Review its privacy settings before connecting sensitive health data.
The browser and local CLI still decrypt on your own device. Hosted MCP uses the separate, consented server-processing flow described above. Read the Remote privacy terms.
DeveloperTomáš Pařízek
ReviewedSeptember 21, 2026
SourceOpen-source CLI
Supporthello@healthexport.app
Common questions
Apple Watch and Apple Health MCP FAQ
Does HealthExport connect directly to my Apple Watch?
No. Apple Watch measurements are stored in Apple Health on your iPhone. HealthExport reads the Apple Health types you authorize and makes the latest synced records available through its hosted MCP server.
Is the Apple Watch data live?
No. HealthExport syncs regularly in the background, but the exact timing is managed by iOS and can vary. The MCP queries the latest data that has successfully synced.
What do I need to use hosted MCP?
You need HealthExport on your iPhone, Remote for uploads, uploaded records, and a compatible AI client. Add the server URL and sign in with Apple; no CLI installation is needed.
Which AI clients can I use?
Use hosted MCP with Claude, the Codex app, or another compatible remote MCP client. Claude Desktop has been tested with HealthExport; other clients have not yet been verified end to end. Availability depends on your client’s remote MCP and OAuth support. For coding agents and scripts, the CLI provides a separate JSON or CSV workflow.
How is this different from direct Apple Health access in an AI app?
HealthExport MCP reads records already uploaded to Remote, after Apple sign-in and consent. It does not access HealthKit directly or contact your watch. You can also use Remote dashboards, CSV export and local CLI automation.
Can the MCP change my Apple Health data?
No. health_export_status, list_health_types, fetch_health_data and fetch_aggregated_health_data are all read-only. The status tool does not verify data freshness.
What about Garmin, Oura, or other wearables?
If another wearable or app writes a measurement into Apple Health, HealthExport can access that Apple Health record when you authorize the corresponding type. It is not a direct Garmin, Oura, or Strava connector.
Your data, your questions
Start with HealthExport on your iPhone
Install the app, enable Remote, and connect your uploaded Apple Health data to your AI assistant with a URL and Apple sign-in.
HealthExport is an independent product and is not affiliated with or endorsed by Apple Inc. Apple Watch, Apple Health, and HealthKit are trademarks of Apple Inc.