Apple Watch MCP · Apple Health MCP

Use your Apple Watch health data with Claude through MCP

Q: Can the MCP change my Apple Health data?

No. HealthExport's MCP tools are read-only.

HealthExport regularly syncs the Apple Health data you choose. On your Mac, a local, read-only MCP extension fetches the encrypted records and decrypts them locally for Claude.

See MCP setup

4.5 on the App Store Remote subscription required Local decryption Open source

How have my steps and resting heart rate changed this month?

fetch_health_data

I found your latest synced Apple Health records. I can compare the daily totals and show the trend.

Read-only connection ready

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 Claude through the Model Context Protocol (MCP).

Apple Watch Records measurements

Apple Health Stores authorized data

Remote sync Uploads encrypted records

Local MCP Decrypts on your Mac

Claude 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.

“Compare my average daily steps this month with last month.”

“Show the trend in my resting heart rate over the last eight weeks.”

“List my recent workouts and summarize duration and energy burned.”

“How much deep and REM sleep did Apple Health record last week?”

“Create a weekly CSV of my active energy for the past six months.”

“Which Apple Health measurements can I query through HealthExport?”

HealthExport provides access to your data; it is not a medical device and does not provide diagnosis or treatment.

More than workouts

Query the Apple Health types you choose to share

HealthExport covers activity, heart, sleep, body measurements, nutrition, workouts, and many other Apple Health categories.

See supported health types

ActivitySteps, 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?

Comparison of Apple’s XML export and HealthExport MCP workflows
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 locally on your Mac

Claude Desktop and Cowork on macOS

Set up HealthExport MCP

The packaged extension uses the same local authentication as the HealthExport command-line tool.

1

Get HealthExport and enable Remote

Install HealthExport on your iPhone, choose the Apple Health types you want to share, and activate a Remote subscription.
Open the App Store
2

Install and authenticate the CLI

Install he on your Mac, run he auth login, and paste the account key from HealthExport Remote.
3

Install the MCP extension

Download the matching Apple Silicon or Intel .mcpb release and install it from Claude Desktop’s extension settings.
Download the latest release
4

Check the connection

Ask Claude to run health_export_status, then list the available health types and query a short date range.

Read the complete setup guide Learn about the Remote subscription

Private by design

Remote availability, local decryption

HealthExport Remote stores encrypted records. The local MCP server fetches those records and decrypts them on your Mac using your account key.

HealthExport cannot read the stored records. The Remote service receives encrypted health packages.

Your account key stays local. The CLI and MCP use it on your machine for decryption.

The MCP tools are read-only. They do not write to or modify Apple Health.

The API uses a one-way hashed identifier. Health packages returned by the service remain encrypted.

Your AI client receives the requested result. Review that client’s privacy settings before querying sensitive health data.

Treat your account key like a password. If you share it with another person, it cannot currently be rotated or revoked. Read the Remote security white paper and privacy policy.

Choose the right connection

MCP for Claude, CLI for flexible automation

Claude Desktop and Cowork

Use the packaged macOS MCP extension for a guided installation and three read-only HealthExport tools.

Packaged MCP extension

Codex, Claude Code and scripts

Use the open-source he CLI for structured JSON or CSV output in terminal and automation workflows.

Cross-platform CLI

ChatGPT and other chat tools

Export a focused CSV and attach it to the conversation. HealthExport does not currently document a direct ChatGPT MCP connector.

CSV file workflow

The underlying local server speaks standard MCP over stdio. The packaged and documented extension installation currently targets Claude Desktop and Cowork on macOS.

DeveloperTomáš Pařízek

ReviewedSeptember 3, 2026

SourceOpen-source CLI & MCP

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 local 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 the MCP extension?

You need the HealthExport iPhone app, an active HealthExport Remote subscription, a Mac, the authenticated HealthExport CLI, and Claude Desktop or Claude Cowork.

Can I use HealthExport with Codex or Claude Code?

Yes. The HealthExport CLI works with Codex, Claude Code, terminal scripts, and other tools that can consume structured JSON or CSV. The packaged MCP installation currently targets Claude Desktop and Cowork.

How is this different from direct Apple Health access in an AI app?

Some AI apps can request Apple Health access directly on iPhone. HealthExport is designed for a desktop Claude workflow, encrypted Remote availability, repeat queries, CSV export, and CLI automation on your own computer.

Can the MCP change my Apple Health data?

No. health_export_status, list_health_types, and fetch_health_data are read-only tools.

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 latest synced Apple Health data to Claude on your Mac.

View source on GitHub

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.