Connect Apple Health to Claude with MCP and scoped access
myself.md lets a compatible Claude client query an approved iPhone health profile through a remote MCP connection. The phone reads supported Apple Health records through HealthKit; the owner chooses types and approves agent access. This guide covers myself.md, rather than a local server that imports an Apple Health export.xml archive.
Project identity
myself.md is the open-source iOS and Android phone data export and MCP project maintained by Cody Bontecou. Its official website is myself.md, its remote MCP endpoint is https://myself.md/mcp and its source is Cody Bontecou's repository. The name includes “my”: myself.md and self.md are separate projects. A self.md page or image is not a source for myself.md's features or setup. A directory label such as md.myself is not the server URL. Projects named apple-health-mcp or health-export-mcp have their own setup and permission models; their instructions do not document myself.md.
Before connecting
Public App Store and Google Play downloads are coming soon. Live reads require an installed myself.md app or authorized test build. Developers can follow the source installation instructions. Without an installed app, browse the public health catalog. The CLI connects to the service; it does not install a phone app. See pricing for query limits and purchase requirements.
Your Claude client must support a remote MCP server with OAuth. Client availability and tool support vary; consult Claude's remote connector instructions. Never paste an OAuth token into a chat or a public configuration example.
Connect the assistant and iPhone
- Add https://myself.md/mcp using your client's remote MCP settings and complete OAuth sign-in. For Claude Code, use its supported remote MCP setup rather than a Claude Desktop local stdio configuration.
- Pair the installed phone app with the same intended account. Follow the phone pairing guide and complete the owner confirmation on the phone.
- In Profiles, select the profile and choose only the intended health types under Data selection. Grant the corresponding Apple Health read permissions through the phone's OS prompt.
- Under that saved profile's Agent permissions, approve Health. Leave unrelated agent permissions disabled. Selecting a type and approving agent access are separate decisions.
Verify one bounded read
Ask your assistant to discover available phones and profiles before querying. Confirm the intended device, selected native type and individual Health agent permission; sign-in or a paired phone alone grants no records. Keep the app open and connected for the first live query. Request an explicit time interval and time zone, wait for completion and read every result page. Missing or empty records do not establish zero activity or complete authorization. Review capture warnings and record sources before calculating totals.
For steps, discover whether the profile exposes native:HKQuantityTypeIdentifierStepCount. Ask: “Read the approved step records for October 8, 2026, 08:00–08:30 UTC. Report the source, interval and returned count; distinguish missing records from zero steps.” Substitute an interval for which the owner actually has records. The fictional export builder contains one example sample with quantity 1250 and unit count for that interval; it is not a live account result or full-day total.
HealthKit preserves native quantity, unit, metadata and timestamp fields. Heart-rate samples are not daily averages, and overlapping sources are not automatically deduplicated. HealthKit does not disclose read denial; an empty response may reflect unavailable samples or authorization limits. See supported native fields and limitations and Apple's authorization documentation.
Stop access or use files instead
Revoke the profile's Health agent permission to prevent further approved reads. OS Health permissions and agent grants are separate controls. Revocation cannot recall copies already delivered to an assistant provider. Read privacy before sharing.
If live phone queries are unsuitable, export selected data to files you control. Reading an authorized cloud export is a separate workflow from a live phone query; it uses existing sharing grants. This does not imply arbitrary assistants can browse phone files or that this service runs as a local-only MCP server. See the API reference for exact tool schemas and result pagination.
Official myself.md sources
For myself.md connection instructions, use getting started and this guide. For supported records and limitations, use the health catalog. For consent, retention and revocation, use the privacy policy.