All connectors
Apple

apple-health-mcp-unofficial

Apple Health

A local parser for Apple Health exports that lets MCP clients summarize activity, sleep, heart, HRV, workouts and body records.

ActivitySleepHeart RateHRVWorkouts
A private local-first data workspace with wellness context
Local export.zip

Best for users who want Apple Health context in an agent without relying on a live API, cloud sync or background mobile service.

Quick Start

terminal
npx -y apple-health-mcp-unofficial setup --export-path /path/to/export.zip
npx -y apple-health-mcp-unofficial doctor
mcp-client.json
{
  "mcpServers": {
    "apple_health": {
      "command": "npx",
      "args": ["-y", "apple-health-mcp-unofficial"]
    }
  }
}
  1. 01

    Export All Health Data from the iPhone Health app.

  2. 02

    AirDrop or transfer export.zip to the machine running the agent.

  3. 03

    Run setup with --export-path and then doctor.

Data Availability

Available

Activity

Steps, distance, energy and exercise records.

Available

Heart rate

Recorded samples and resting heart rate.

Available

Sleep analysis and stages

When iPhone or Apple Watch logs sleep.

Available

Workouts and sport metadata

All HKWorkout entries in the export.

Available

Body measurements

Weight, BMI and body fat when logged.

Available

HRV and breathing rate

Available when Apple Watch supports and records them.

Conditional

ECG waveform

Metadata is available; raw waveform requires PDF export.

Not exposed

Live HealthKit or iCloud Health sync

Not exposed by export files.

Agent Tools

Start here

  • apple_health_connection_status
  • apple_health_daily_summary
  • apple_health_weekly_summary

Diagnostics

  • apple_health_capabilities
  • apple_health_agent_manifest
  • apple_health_privacy_audit

Records

  • apple_health_list_records
  • apple_health_list_workouts

Prompts and Resources

Prompts

  • apple_health_daily_review
  • apple_health_weekly_review

Resources

  • apple-health://capabilities
  • apple-health://agent-manifest
  • apple-health://summary/daily
  • apple-health://summary/weekly

Privacy Model

No OAuth or cloud token is required.
All parsing happens from a local export path.
The agent sees MCP responses, not the user's entire export by default.
Good fit for private, server-side Hermes deployments when the export file is controlled.