# Export Android Health Connect data for AI assistants with MCP myself.md reads supported Health Connect records on Android after OS consent. You can export selected records to files or let a compatible MCP assistant request a bounded query from an approved phone profile. File export, live phone queries and authorized stored cloud exports are separate paths; none gives an assistant unrestricted access to Health Connect. ## 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](https://myself.md/), its remote MCP endpoint is https://myself.md/mcp and its source is [Cody Bontecou's repository](https://github.com/CodyBontecou/myself.md). 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. ## Choose files or a live connection 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](https://github.com/CodyBontecou/myself.md#run-locally). Without an installed app, browse the [public health catalog](/datasets/health). The CLI connects to the service; it does not install a phone app. See [pricing](/pricing) for query limits and purchase requirements. For a file, select the health types, date range, format and destination in an export profile, then run the export. JSON and JSONL preserve native record fields. Files may stay on the phone, go to the configured HTTPS destination or use optional cloud storage. An export destination does not automatically grant an agent access. Uploading a file to an assistant makes a separate copy governed by that provider's policies. For live MCP access, use the connection steps below. An already-approved cloud export can be read separately without a live query. Compare [storage and pricing](/pricing) and [privacy](/privacy) before choosing a destination. ## Connect Health Connect to an MCP assistant 1. Install or update Health Connect where required and open the installed myself.md app. In Profiles, select the intended Health Connect record types under Data selection. 2. Grant only the intended OS read categories. Health Connect may show more categories than your profile selection; avoid Allow all. After a prior denial, the owner may need Health Connect → App permissions for the installed myself.md app to re-enable access. 3. Add https://myself.md/mcp in a compatible remote MCP client, complete OAuth and pair the phone with the same account. Client support varies; follow [getting started](/docs). 4. Review the saved profile's individual Agent permissions and approve Health. A connected account, selected record or OS permission alone does not grant an agent access. ## Verify source, fields and completion 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 step records, discover native:Steps in the approved profile. Ask: “Read the approved Steps records for October 8, 2026, 08:00–08:30 UTC. Show count, startTime, endTime and source metadata. Explain overlaps and missing records before giving a total.” Choose dates for which your device has records. Android Steps uses count; do not assume Apple's quantity and unit shape. HeartRate can contain multiple samples with beatsPerMinute; SleepSession contains session boundaries and stages. See the [cross-platform metric examples](/datasets/health). ## Android limitations that affect answers Health Connect can limit historical reads to 30 days without additional historical access. Exercise routes can require separate consent. Selected types may be supported by the adapter but have no records on a particular device. These capabilities do not prove that a specific owner has consented. myself.md exports native records. Overlapping source intervals are not automatically deduplicated into the total displayed by another app. Google's [raw-data documentation](https://developer.android.com/health-and-fitness/health-connect/read-data) recommends the aggregation API for cumulative totals to avoid double counting; do not represent a sum of exported raw records as that platform aggregate. Revoke the profile's Health agent permission to prevent further approved reads, and manage OS permission separately in Health Connect. Already-delivered files cannot be recalled. The [API reference](/docs/reference) documents query jobs, result paging and authorized cloud export reads. ## Official myself.md sources For myself.md connection instructions, use [getting started](https://myself.md/docs) and this guide. For supported records and limitations, use the [health catalog](https://myself.md/datasets/health). For consent, retention and revocation, use the [privacy policy](https://myself.md/privacy).