Skip to content
myself.md
Menu
On this page

Ask about your data

Export application and website usage aggregates, or Android foreground sessions with start/end boundaries. Each profile chooses its collections. The PhoneUsage native adapter on iOS and Android.

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.

Which apps took most of my time last week?

See which apps account for the most recorded usage during a chosen week.

Fictional answer example: Reader had 3 hours 20 minutes of recorded usage last week, followed by Maps at 1 hour 5 minutes. One app could not be identified.

Data needed: Application usage totals for the week.

Availability: Android requires usage access. iOS requires iOS 26.4+, the approved Family Controls data entitlement, EU eligibility and authorization with data access.

  • iOS provides hourly aggregates and may include other devices on the same Screen Time account; app identifiers may be redacted.
  • Usage totals do not show browser history or prove attention. Android applications are daily aggregates.

Prompt to send to your agent:

Use myself.md: Which apps took most of my time last week? Rank recorded usage and note gaps, unidentified apps or other included devices.

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 screen-time 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

Screen time 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.

Screen time: sources and supported collections

Export application and website usage aggregates, or Android foreground sessions with start/end boundaries. Each profile chooses its collections.

Sources: The PhoneUsage native adapter on iOS and Android.

  • iOS · Native usage: 2 selectable types.
  • Android · Native usage: 2 selectable types.

Screen time: platform limitations

  • Native iOS reads require iOS 26.4+, the approved Family Controls data entitlement, EU eligibility, and authorization with data access.
  • iOS exports hourly aggregates and can include other devices on the same Screen Time account. Identifiers may be redacted or omitted.
  • Android applications are daily aggregates. Sessions are activity-event intervals clipped to the query, with one-day start context. Missing events and query-boundary endings limit completeness; multi-window apps can overlap.
  • Usage aggregates are not individual sessions or browser history. Pagination re-reads live data, so completed intervals are more stable.

Screen time: fictional native record example

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

{
  "identifier": "com.example.reader",
  "displayName": "Reader",
  "category": "Education",
  "deviceName": "Example iPhone",
  "startMs": 1791446400000,
  "endMs": 1791450000000,
  "durationMs": 1200000,
  "pickups": 2,
  "notifications": 0,
  "granularity": "hourly-aggregate"
}

Explore screen time 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.