How do I connect Claude to Apple Health?

Can Claude read and write Apple Health data?

Checked on 7 November 2026.

Claude has a built-in Apple Health connection in its iOS app. Anthropic's help page describes it as a beta currently limited to users in the US, for Pro, Max and Ultra plans. It can read data with your permission, but cannot write or modify Apple Health entries.

Syncky Health connects Apple Health to your own agent or server, with no Syncky account. On the agent route, client health-data envelopes are encrypted end to end through Relay. Relay sees delivery metadata and no health values; its own hub notices are plaintext. It queues sealed envelopes until acknowledgment or expiry, at most 7 days. Your agent receives plaintext, and a chosen model sees what the agent supplies.

Syncky writes only to supported types in the app's device-wide write allowance, within the connection's write scope and with iOS Health permission. Each entry records its source; see write permissions and source metadata.

Which Claude clients work with Syncky today?

Claude Desktop and Claude Code can use the paired local agent through npx -y @syncky/agent mcp. Claude Desktop also supports .mcpb bundles; the Claude Desktop guide covers this route, checksum limits and client compatibility caveats. Both routes need Node.js 22.15 or newer.

claude.ai and the Claude mobile apps are not supported by Syncky's local MCP route. Those clients need a remote MCP URL and cannot reach a local agent. The built-in iOS connection described above is a separate option.

iOS decides background opportunities. Syncky reads and applies writes when the app runs and the iPhone is unlocked; a queued write is not an applied write.

Where should I start?

Follow the Claude Desktop guide or Claude Code guide, then use agent setup for pairing, receiving and permissions. For a direct server or other approaches, see Apple Health API options, writing to Apple Health and the Apple Health MCP comparison.