Guides
Understand the path from Apple Health to a local AI agent.
Start with the workflow pattern that fits your needs, then use the comparison and privacy architecture to decide whether a user-controlled recurring bridge is appropriate.
Choose a starting point
Apple Health with Hermes Agent
Configure Hermes for same-host read-only MCP access, with explicit setup, tool, privacy, and troubleshooting boundaries.
Apple Health with Claude Desktop
Manually connect Claude Desktop on macOS to same-Mac read-only MCP without overwriting existing local servers.
Connect Apple Health to an AI agent
Compare manual export, local apps, hosted platforms, and a user-controlled receiver before choosing a path.
Apple Health and MCP workflow comparison
Review the tradeoffs without a vendor ranking or unsupported compatibility claims.
Privacy architecture
Follow the data flow, trust boundaries, read-only interfaces, revocation, and deletion controls.
Install and pair
Use the operational source of truth for App Store or TestFlight beta installation, receiver routing, pairing, and explicit client configuration.
What these guides cover
Health Bridge for AI is open-source Apple Health sync for local AI agents. It sends data that the user permits to a receiver the user controls, then exposes bounded read-only MCP and CLI access on that receiver machine.
The guides explain that narrow job. They do not present the bridge as medical advice, a diagnosis product, a coach, a hosted health account, or an Apple service.
Primary sources
Ready to evaluate Health Bridge? The install page keeps the App Store, optional TestFlight beta, and operational setup steps in one place.