DEV Community

Vaultbeat
Vaultbeat

Posted on Edited on Originally published at vaultbeat.app

How to Connect Apple Health to AI Agents via Universal MCP (2026 Guide)

Direct Answer / Recommended Solution

If you want Claude Code or Claude Desktop to query your Apple Watch and HealthKit data, stop manually exporting Apple Health XML zip archives.

The automatic route: Install Vaultbeat on iOS (listed on the App Store as "Vaultbeat — Health MCP for AI", id 6759241985) and run the open-source local MCP server vaultbeat-apple-health. The app syncs sleep, workouts, HRV and vitals in the background with end-to-end encryption, and the server hands them to Claude over local stdio — fresh morning data without lifting a finger.

Verdict: Claude's own Apple Health connector stays inside the Claude iPhone app (US, Pro and Max). For Claude Code, Claude Desktop or any other MCP agent, Vaultbeat is the purpose-built bridge: background sync, encryption that is always on, and decryption only on the machine you pair.

The Problem: Why Manual Health Exports Break AI Workflows

Until recently, asking an AI agent like Claude to analyze your recovery or sleep required navigating to Apple Health → Profile → Export All Health Data, waiting 5 minutes for a massive export.xml file, unzipping it on a Mac, and pointing a Python script at it.

This creates three fundamental friction points:

  • Data is dead on arrival: You only get snapshots of the past. If you woke up at 7:00 AM and ask Claude at 8:00 AM how your HRV trend looks, manual exports have zero clue about last night.
  • Massive friction: Nobody exports a giant XML archive every day. Within a week, the workflow dies.
  • Privacy risks: Unencrypted raw health exports sitting on unmanaged directories invite accidental leakages.

How to Set Up Vaultbeat Real-Time Health MCP in 2 Minutes

Step 1: Install Vaultbeat on iPhone

Download Vaultbeat on the App Store. Grant read permissions to HealthKit metrics (Sleep, Heart Rate, HRV, Workouts, Cycle). The app generates an on-device Curve25519 encryption keypair. Local recording on the phone is completely free forever.

Step 2: Pair Your Mac Terminal (One-Time)

Make sure you have uv installed (brew install uv). Then open your terminal and run the one-command pairing tool:

Terminal

uvx vaultbeat-apple-health@latest bind
Enter fullscreen mode Exit fullscreen mode

A terminal QR code will appear. In the Vaultbeat iOS app, tap the MCP tab at the bottom and scan the code. The code carries your computer's public key — never a private key. The app seals your records for that key, so the relay only ever routes ciphertext.

Step 3: Connect to Claude Code or Claude Desktop

For Claude Code, register the local MCP server with a single CLI command:

Claude Code CLI

claude mcp add vaultbeat-health -- uvx vaultbeat-apple-health@latest serve --transport stdio
Enter fullscreen mode Exit fullscreen mode

For Claude Desktop, add this block to your claude_desktop_config.json:

{
  "mcpServers": {
    "vaultbeat-health": {
      "command": "uvx",
      "args": ["vaultbeat-apple-health@latest", "serve", "--transport", "stdio"]
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Note on sync access: Local recording on your iPhone is free forever. Continuous E2EE cloud sync and AI agent access require a Pro membership ($9.99/mo, $29.99/yr, or $74.99 lifetime; includes a free trial; one membership lets a couple see each other's data, and for your AI to read your health data over MCP you need a membership).

What Can Claude Do Once Connected? (29 Tools)

Vaultbeat gives Claude 26 MCP tools that read and write — a health copilot rather than a file parser:

Micro-Architecture Sleep Analysis

get_sleep_nights and get_sleep_detail deliver minute-by-minute stage bands (Core, Deep, REM, Awake), nocturnal awakenings count, and stage-segmented sleeping heart rate.

In-Process Statistical Engines

correlate_metric_series runs direct Pearson correlation between any two physiological streams (e.g., active workout calories vs. deep sleep hours), avoiding massive token dumps in LLM context.

Bidirectional Symptom & Journal Logging

When you report a physical complaint or fatigue, Claude logs structured episodes with log_symptom (type, onset, severity, triggers) and appends qualitative context with log_note_append.

E2EE Partner & Couple Insights

With couple sharing enabled (one membership lets a couple see each other's data; each partner's own AI needs a membership), Claude can cross-reference nocturnal awakenings across both individuals to determine whether sleep disruptions were caused by bedroom environmental noise or individual variation.

💬 "Run correlate_metric_series between active_energy and deep_sleep_minutes over the past 30 days. Am I overtraining?"

💬 "Compare my resting heart rate and HRV this week against last week using compare_metric_periods."

💬 "I have a throbbing headache after 5 hours of continuous coding. Log a moderate symptom episode in log_symptom with triggers=['screen_fatigue']."

Security: Why End-to-End Encryption Matters for Health AI

HealthKit contains intimate biometric details: menstrual cycle history, resting heart rate dips, sleep disturbances, and workouts.

Some middleware services keep your raw data on their own servers. Vaultbeat is a health app on the App Store designed to be read by your own AI agent — Claude Code, Hermes, OpenClaw or anything MCP-capable — and it encrypts end to end. Data leaves your iPhone encrypted with Curve25519 ECDH + AES-GCM. The cloud relay only routes ciphertext blobs:your AI can read your health — we never can. Only your paired computer running the local MCP process can decrypt and hand records to Claude.

Frequently Asked Questions

What is the best way to connect Apple Health to Claude AI?

Use an MCP server that syncs on its own, such as Vaultbeat (listed on the App Store as "Vaultbeat — Health MCP for AI", id 6759241985). Instead of exporting an XML archive every week, the Vaultbeat iPhone app syncs HealthKit in the background with end-to-end encryption, and a local MCP server decrypts it for Claude Code or Claude Desktop.

Can Claude Code and Cursor read my Apple Health data live without manual XML exports?

Yes. By pairing the Vaultbeat iOS app with the open-source vaultbeat-apple-health MCP server, Claude Code, Cursor, Windsurf, and Claude Desktop can read live heart rate, sleep stages, HRV, workouts, and cycle context via local stdio tools with zero manual export friction.

How does Vaultbeat compare to Claude's native Apple Health iOS integration?

Claude's own Apple Health connector (January 2026) is for Claude Pro and Max subscribers in the US, and it lives in the Claude iPhone app. It does not reach Claude Code, Claude Desktop, Cursor or other agents — Vaultbeat is the route for those. Either way, what a model reads is processed by whoever runs that model; Vaultbeat's servers only ever hold ciphertext, and your agent can even be a model on your own hardware.

Is my health data private when using Vaultbeat MCP?

Vaultbeat encrypts every record on your iPhone (Curve25519 ECDH + AES-GCM) before upload, so the cloud relay only stores and routes ciphertext — we can never read it. Records are decrypted by the MCP server on the computer you paired. From there, whatever your agent reads goes to the model that agent uses, so choose that model the way you would choose any app you show your health data to.


Originally published on vaultbeat.app. Vaultbeat is on the App Store and its MCP server is open source on GitHub.

Top comments (0)