Ask about your data

Export the health samples your phone can read into files. Select individual metrics and keep the original units, metadata, and source fields. HealthKit on iOS, Health Connect on Android, and optional WHOOP on either phone platform.

Copy a question into your agent to get started. This catalog describes capabilities, not a connected person's available records. All answer examples are fictional.

How has my sleep changed this month?

Ask your assistant to compare sleep duration across the nights with available records.

Fictional answer example: Across 12 nights with records, your average sleep was 7 hours 10 minutes. Three nights have no records, so I excluded them from the average.

Data needed: Sleep records covering the dates you want to compare.

Availability: Apple Health on iOS or Health Connect on Android, when sleep records are present and approved.

• Overlapping sources and sleep stages need careful handling; time in bed is not time asleep.
• Missing nights cannot be treated as zero sleep. HealthKit cannot distinguish denied reads from missing samples. Android historical access may limit older records.

Prompt to send to your agent:

Use myself.md: How has my sleep changed this month? Compare nights with records and flag missing nights or overlapping sleep sources.

Use approved records, confirm dates and timezone, and explain missing data. If needed, help me connect https://myself.md/mcp using https://myself.md/docs and wait for my approvals.

Explore health data types and example JSON.

Am I walking more than last month?

Compare daily step counts over equivalent periods, with gaps and sources explained.

Fictional answer example: For the first 14 complete days of each month with records, your daily average rose from 5,800 to 6,400 steps. These figures exclude days with missing coverage.

Data needed: Step records for two comparable date ranges.

Availability: Apple Health on iOS or Health Connect on Android, when step records are present and approved.

• Samples can overlap across sources; adding every sample may double count steps.
• A partial day or missing records can distort a comparison. Android historical access may limit last month’s records.

Prompt to send to your agent:

Use myself.md: Am I walking more than last month? Compare equivalent complete periods and avoid double-counting overlapping step sources.

Use approved records, confirm dates and timezone, and explain missing data. If needed, help me connect https://myself.md/mcp using https://myself.md/docs and wait for my approvals.

Explore health data types and example JSON.

Connect your data when you’re ready

1. Connect a compatible AI assistant at https://myself.md/mcp and complete sign-in.
2. Pair an installed myself.md phone app with the same account. Public store downloads are coming soon.
3. Select the required data in a phone profile, allow the relevant OS permissions and separately approve its Agent permissions.

Viewing this page or copying a prompt does not grant access. Your assistant must check available records and date coverage before answering. Public App Store and Google Play downloads are coming soon.

Connect an AI assistant. Agents can discover these same structured workflows, required types, prerequisites and query steps through get_public_dataset_catalog or the public catalog. Follow nextCursor until hasMore is false.

1. get_phone_data_catalog: Discover connected phones, approved profiles and actual supported types. Catalog support does not prove that records exist.
2. query_phone_data: Use the discovered device/profile IDs and approved native types. Resolve the question to explicit date bounds and a timezone; request only the needed data.
3. get_phone_request: Poll queued or running requests. Use records only after complete; report failed, expired or missing requests. Follow every result cursor with a new bounded query.

Technical explorer

Health exports in myself.md. Select native types in the interactive explorer to update a fictional JSON export. Agent reads require supported phone sources, operating-system permission, selected profile types and separate agent approval.

Health: sources and supported collections

Export the health samples your phone can read into files. Select individual metrics and keep the original units, metadata, and source fields.

Sources: HealthKit on iOS, Health Connect on Android, and optional WHOOP on either phone platform.

• iOS · Quantity samples: 121 selectable types.
• iOS · Category samples: 72 selectable types.
• iOS · Current characteristics: 6 selectable types.
• iOS · Workouts and other samples: 6 selectable types.
• Android · Health Connect: 40 selectable types.
• WHOOP · Connected provider: 5 selectable types.

Common health questions and native fields

These examples come from the supported adapter catalog. Field names and units stay native; availability does not establish OS authorization, profile approval or existing records. A profile selection uses the identifier with a native: prefix.

Reproduce a fictional step question

Question: “How many steps are in the example's October 8, 2026, 08:00–08:30 UTC interval?” Open the health export builder, select only iOS HKQuantityTypeIdentifierStepCount, and inspect the fictional JSON preview. The fixture contains one sample for that interval with quantity: 1250 and unit: "count", so the sample reports 1,250 steps. This is one fictional interval, not a full-day total or a live phone result.

For an approved phone profile, first discover its actual IDs and types. Request step records for 2026-10-08T08:00:00.000Z through 2026-10-08T08:30:00.000Z, wait for completion and follow all result pages. Verify returned source, timestamps and units before aggregating; real records may differ, overlap or be absent. On Android choose Steps and read its count field rather than assuming the iOS shape. See the connection and verification steps.

Health: platform limitations

• HealthKit does not reveal read denial. Empty results can mean no samples or no authorization.
• Characteristics are current snapshots captured at read time, not historical values for the selected day.
• The native iOS adapter excludes clinical FHIR, attachments, audiograms, medications, and vision prescriptions.
• Health Connect can limit historical reads to 30 days without historical access. Exercise routes may require separate consent.
• Optional WHOOP connection requires provider sign-in and consent. WHOOP v2 records preserve scores, RMSSD and millisecond durations separately from OS health records; overlapping events are not deduplicated. Body measurements are current snapshots, not historical measurements. Recovery has no independent measurement timestamp.

Health: fictional native record example

This illustrates native fields for HKQuantityTypeIdentifierStepCount from healthkit, not a complete export envelope or a real person's records. The interactive builder previews selected types in the released export schema.

{
  "startDate": "2026-10-08T08:00:00.000Z",
  "endDate": "2026-10-08T08:30:00.000Z",
  "quantity": 1250,
  "unit": "count"
}

Explore health types and build a fictional export.

Connect an AI assistant

Add https://myself.md/mcp as a remote MCP server in a compatible client and complete OAuth sign-in. Pair your phone with the same account, select a profile and approve its relevant individual Agent permissions. The assistant discovers available types before requesting a bounded query and waits for completion. A stored cloud export is a separate read path; signing in or viewing this catalog grants no private data.

Read getting started, the API reference, pricing and privacy.

For source-specific instructions, read Apple Health with Claude and scoped MCP access or Android Health Connect exports and MCP queries.

Explore other datasets

• Health: HealthKit on iOS, Health Connect on Android, and optional WHOOP on either phone platform.
• Screen time: The PhoneUsage native adapter on iOS and Android.
• Location: Points recorded by myself.md through Expo Location.