MCP.Market

Apple Health AI Bridge MCP server

by roian6·io.github.roian6/health-bridge·v1.2.0·7 stars

Read-only local MCP access to Apple Health data through Apple Health AI Bridge.

B70/100grade B
What users say
No reviews yet
Be the first
Safety scan
B70/100

not scanned yet

Adoption
Growing

7 stars

Reviews

Write one

Nobody has reviewed Apple Health AI Bridge yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Apple Health AI Bridge tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Apple Health AI Bridge compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
70/100
higher than 35% of 48,255 servers
GitHub stars
7
more than 86% of 28,688 servers

Release history: 3 versions in the registry since 2026-07-28, latest 2026-11-01, typically one every 85 days.

Install Apple Health AI Bridge in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Apple Health AI Bridge repository's README, as published. We do not edit it. Read it on GitHub

Your Apple Health data, continuously available to your own AI agent. Download on the App Store · Set up your bridge · Supported health data · Website

Apple Health AI Bridge is the open-source project behind Health Bridge for AI.

The project gives you a direct, self-hosted path from Apple Health to the AI tools you choose—without routing it through a hosted intermediary. The iPhone companion continuously sends the HealthKit data you permit to a receiver you control, where read-only CLI and MCP interfaces make it available to compatible agents.

Your health data stays under your control: the receiver and database run on your infrastructure, AI access is read-only, and no hosted relay or third-party model is required.

Automatic background sync is designed for continuous use. iOS controls background scheduling, so delivery timing is best-effort rather than real-time or guaranteed at a specific moment.

Set up the bridge

You need:

  • an iPhone running iOS 18 or later;
  • a macOS or Linux computer that will run the receiver and store the private database; native Windows is not currently supported;
  • for continuous sync, a stable private HTTPS route that the physical iPhone can reach away from the local network; for an explicit local-only evaluation, a same-LAN route with the limitation below;
  • an MCP client on the receiver machine, or a terminal for direct CLI access;
  • uv for the receiver package.

1. Install the iPhone app

Download Health Bridge for AI from the App Store on your iPhone. TestFlight remains available for beta builds and prerelease testing through the official install page.

2. Prepare the receiver route

The project does not give you a receiver URL. The URL is the private address by which the iPhone reaches your receiver computer, and it must exist before core setup can create pairing material.

  • Already use Tailscale: use the private Tailscale Serve HTTPS path documented in the setup guide. Tailscale is an option for existing users, not a product requirement.
  • Agent-assisted private HTTPS ingress: use the setup guide's agent-assisted path. The setup agent must inspect first, show every proposed DNS, tunnel, proxy, firewall, and service change, and wait for approval before applying it.
  • Local network only: supported as a deliberate local-only fallback, but automatic sync stops when the iPhone leaves that network.

Do not copy a sample hostname, expose receiver port 8765 directly to the public internet, or publish the pairing page. Follow the complete receiver setup guide to produce and verify the real route.

3. Install and run setup

Install the current signed receiver release:

uv tool install "git+https://github.com/roian6/apple-health-ai-bridge.git@receiver-v1.1.1"

The route-specific guide sets HEALTHBRIDGERECEIVER_URL to the exact configured /v1/batches URL. Only then run:

health-bridge setup --receiver-url "$HEALTH_BRIDGE_RECEIVER_URL"

For the deliberate Route C local-network-only fallback, use the same real LAN URL and the required non-loopback bind:

health-bridge setup \
  --receiver-url "$HEALTH_BRIDGE_RECEIVER_URL" \
  --receiver-host 0.0.0.0 \
  --receiver-port 8765

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Apple Health AI Bridge: common questions

Is Apple Health AI Bridge MCP server safe?
Mostly: it is graded B (70/100). Read the Apple Health AI Bridge safety report
Does Apple Health AI Bridge need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Apple Health AI Bridge maintained?
The last commit was 42 days ago (2026-09-23). The latest release is v1.2.0.
How does Apple Health AI Bridge compare with other MCP servers?
safety score 70/100 (higher than 35% of 48,255 servers); github stars 7 (more than 86% of 28,688 servers). Full comparison.