Skip to main content
Glama

apple-health-mcp

An MCP server for Apple Health data. Reads daily health metrics and workouts exported by the Health Auto Export iOS app.

Features

  • MCP Server: 3 tools for querying Apple Health data from Claude Code or any MCP client

  • No API keys needed: Reads local CSV files exported by Health Auto Export to iCloud Drive

  • Comprehensive: Steps, HR, HRV, SpO2, sleep stages, body composition, workouts

Related MCP server: Apple Health Chat MCP

MCP Tools

Tool

Description

apple_health_daily

Daily summary: steps, energy, HR, HRV, sleep stages, body comp, workouts

apple_health_workouts

Workout sessions for a date (type, duration, HR, calories, distance)

apple_health_trends

Multi-day trends for steps, HR, HRV, sleep, weight

Setup

1. Set up Health Auto Export on iPhone

This MCP server reads CSV files produced by Health Auto Export, a third-party iOS app that automatically exports Apple Health data to iCloud Drive. The app runs in the background and syncs new data throughout the day.

  1. Install Health Auto Export from the App Store

  2. Open the app and grant it access to Apple Health data when prompted

  3. Go to Automations and create two automations:

    • Daily Metrics: Select the health metrics you want (steps, heart rate, sleep, etc.), set format to CSV, frequency to Daily, and destination to iCloud Drive

    • Workouts: Select workout data, set format to CSV, frequency to Daily, and destination to iCloud Drive

  4. The app will export CSV files to iCloud Drive, which syncs automatically to your Mac at:

    ~/Library/Mobile Documents/iCloud~com~ifunography~HealthExport/Documents/
  5. Verify the files are syncing by checking that the directory contains Daily Export/ and Workouts/ folders with dated CSV files

2. Install

git clone https://github.com/daveremy/apple-health-mcp.git
cd apple-health-mcp
npm install
npm run build

3. Use as MCP Server

Add to your Claude Code project's .mcp.json:

{
  "mcpServers": {
    "apple-health": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/apple-health-mcp/dist/mcp.js"]
    }
  }
}

Or register with the Claude CLI:

claude mcp add apple-health --scope project -- node /path/to/apple-health-mcp/dist/mcp.js

Custom Export Directory

If your Health Auto Export saves to a different location, set the environment variable:

{
  "env": {
    "APPLE_HEALTH_EXPORT_DIR": "/path/to/your/export/directory"
  }
}

Data Format

The server expects the CSV file structure produced by Health Auto Export:

Documents/
  Daily Export/
    HealthMetrics-YYYY-MM-DD.csv
  Workouts/
    Workouts-YYYY-MM-DD.csv

Requirements

License

MIT

Available Tools

3 tools
apple_health_dailyDaily SummaryB

Get Apple Health daily summary: steps, energy, HR, HRV, sleep stages, body comp, workouts

Inputs: date.

apple_health_workoutsWorkoutsC

Get workout sessions for a date

Inputs: date.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have distinct primary purposes: daily summary, trends over a range, and workouts. However, apple_health_daily and apple_health_trends overlap significantly in metrics (steps, HR, HRV, sleep), which could cause confusion about when to use each. The descriptions help clarify, but some ambiguity remains.

    Naming Consistency5/5

    All tool names follow a consistent apple_health_* pattern with clear, descriptive suffixes (daily, trends, workouts). This predictable naming makes it easy for agents to understand the tool set and infer purposes without confusion.

    Tool Count3/5

    With only 3 tools, the server feels thin for the Apple Health domain, which typically includes more operations like adding data, querying specific metrics, or managing permissions. While it covers basic retrieval, the scope seems limited compared to the potential complexity of health data.

    Completeness2/5

    The tool set is severely incomplete for an Apple Health server, focusing only on retrieval of daily summaries, trends, and workouts. There are no tools for creating, updating, or deleting health data, nor for accessing detailed metrics or settings, which are common in health APIs. This will likely cause agent failures in broader health management tasks.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables Claude to answer natural language questions about your Apple Health data by analyzing local CSV exports, supporting metrics like steps, heart rate, sleep, and more.
      6
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Open-source MCP server for MetricBridge (formerly Health Export AI). 16 tools and 22 prompts let any MCP agent query 190 Apple Health metrics from files on your own machine. The server is read-only, has zero dependencies and makes zero network calls.
      21
      561 npm
      11
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Read-only MCP server that exposes Apple Health data (steps, workouts, sleep, etc.) from a local SQLite store, allowing AI agents to query health metrics without sending data to hosted services.
      9
      37
      Apache 2.0