myself.md — Personal data for AI agents

myself.md is an open-source iOS and Android app that exports selected health, screen time and recorded location data to files you control. Compatible AI assistants can query the data you approve through MCP.

Create export profiles that select data types, date ranges and destinations. Use local files, your own HTTPS endpoint, or the paired cloud service. Operating-system permissions still apply.

When should I use myself.md?

Use myself.md to export your personal records, explore sleep and activity patterns with an AI assistant, understand screen-time habits, or work with location points you chose to record. Choose which data to share and which profiles agents can access.

Supported sources vary by platform. Live phone queries require a reachable installed app and your approval. Public App Store and Google Play downloads are coming soon.

Do not infer permission from an empty result.

Explore supported datasets

Preview supported data at https://myself.md/datasets. Mobile store distribution is coming soon; source and self-hosting instructions are available at https://github.com/CodyBontecou/myself.md.

JavaScript integration

Install the official SDK with npm install myself-md-sdk. Package: https://www.npmjs.com/package/myself-md-sdk. The official CLI is https://www.npmjs.com/package/myself-md-cli; run npx myself-md-cli health for a public service check. The SDK provides public discovery, dataset pagination and authorized asynchronous phone-query methods.

Connect an AI agent

Give your agent this prompt: Set up myself.md using https://myself.md/llms.txt

Start with public discovery: GET https://myself.md/v1/dataset-catalog and GET https://myself.md/v1/docs need no account. Read https://myself.md/docs/reference for exact request schemas and tool availability in your client. For private data, discover connected phones and approved profiles with get_phone_data_catalog, request a bounded query with query_phone_data, then poll get_phone_request until it reaches a terminal state. Phone query states are queued, running, complete and failed; use records only after complete, and stop if the request is expired or missing. Other owner-reviewed operations may require awaiting_user handoffs or report cancelled outcomes; follow returned pagination cursors and capture warnings. Do not retry a mutation blindly after a lost response. Stored cloud exports use list_cloud_exports and read_cloud_export, subject to existing profile and source grants. If a restricted client does not expose an operation, report that limitation and use its documented owner handoff.

Add https://myself.md/mcp as a remote MCP server in a compatible client. OAuth 2.0 signs you in and asks for consent. Pair your phone and select profile data before requesting private records. Paired online phones approve authenticated agent queries; OS permissions still require you. Read the developer guide at https://myself.md/docs and the privacy policy at https://myself.md/privacy.

Find myself.md in the Smithery MCP directory: https://smithery.ai/servers/cody-82px/myself-md.

Recorded walkthroughs

- [Choose your context](https://myself.md/dashboard/showcase/selection.mp4): a silent recording of selecting data types and JSON/JSONL settings in an isolated app QA session. - [Approve agent access](https://myself.md/dashboard/showcase/approval.mp4): a silent recording of phone-owner approval in an isolated QA profile. Agents cannot approve themselves. - [From phone to agent](https://myself.md/dashboard/showcase/overview.mp4): a silent film combining app setup footage with an illustrated replay of an actual MCP run using synthetic phone data. The agent UI is illustrative.

Recordings date from October 2026; app UI may differ from the current release. Browsers provide native playback controls, and agents can retrieve these public media URLs without authentication. Watching a recording does not initiate account setup or change permissions.

Your data, on your terms

Review sharing permissions, revoke future reads, and inspect activity in the phone app or authenticated dashboard. Cloud export content is encrypted at rest and kept until you delete or replace it; the only exception is the 30-day lapse rule when paid cloud storage ends above the included allowance (see Pricing). The service decrypts approved records for authorized reads; providers receiving those records apply their own retention policies. Revocation cannot recall copies already delivered to another service.

Pricing

The dataset catalog is free. The app includes 5 free exports or queries, followed by an optional one-time lifetime unlock. The US price is $19.99; actual checkout uses the localized price returned by Apple or Google. Open the installed app for free at myselfmd:// or open Lifetime checkout at myselfmd://unlock. Open the installed iOS or Android app, review the localized store price, then confirm the one-time Lifetime purchase. Use Restore purchases for a purchase already made with this store account. For included Lifetime storage, sign in to the app with the same account as your dashboard or MCP connection, then check lifetime access. Requires an installed app. Public App Store and Google Play downloads are coming soon. TestFlight sandbox purchases do not unlock production access. Opening the app does not confirm payment or grant access. Eligible existing health.md, iso.me and time.md purchasers can claim lifetime access after purchase verification. Lifetime access removes export/query usage limits and does not include unlimited hosted storage. Optional cloud storage keeps encrypted exports for your account, provides a hosted MCP server for agents and requires an account. Cloud storage plans: 100 MB: Included with Lifetime (No recurring charge); 100 GB: $7.99 / month (or $79.99 / year). myself.md Cloud is a 100 GB auto-renewing App Store or Google Play subscription bought in the installed app at myselfmd://cloud-storage. Cloud includes app access while subscribed, with no Lifetime purchase required. Its capacity replaces any included 100 MB; capacities do not add up. Prices are US prices; checkout shows the localized store price and billing period. A subscription renews automatically unless cancelled at least 24 hours before the current period ends; manage or cancel it in App Store or Google Play subscription settings, and request refunds from Apple or Google. Storage continues during the store's billing grace period. If paid storage ends while usage exceeds the remaining allowance (100 MB with Lifetime, zero otherwise), the files stay for 30 days with push and email reminders; resubscribe or delete files before then, or the oldest exports are deleted until usage fits the remaining allowance. A refunded Lifetime purchase deletes all cloud exports only if no active Cloud subscription remains. The dashboard and agents cannot purchase storage; they hand off to the app. Subscription terms: https://myself.md/terms.

What is myself.md?

myself.md is an open-source app for iOS and Android that exports selected health, screen time and recorded location data to files you control. Its MCP server lets compatible AI assistants query approved phone profiles or read authorized cloud exports. You choose the data types, date ranges and destinations.

Is myself.md the same project as self.md?

No. The name myself.md includes “my”. This phone data export and remote MCP project is maintained by Cody Bontecou at https://github.com/CodyBontecou/myself.md. Its official website is https://myself.md/ and its MCP endpoint is https://myself.md/mcp. self.md is a separate project; its pages and images do not document myself.md.

Which sources document myself.md setup and permissions?

Use https://myself.md/docs for connection and pairing, https://myself.md/datasets/health for supported health records and limitations, and https://myself.md/privacy for consent, retention and revocation. The source is https://github.com/CodyBontecou/myself.md. A listing for another apple-health-mcp or health-export-mcp project is not documentation for myself.md. Public store downloads are coming soon; live phone reads require an installed app or authorized test build.

How can I connect Apple Health to an AI assistant with myself.md?

On iPhone, myself.md reads supported Apple Health data through HealthKit after you grant operating-system permission. Select health types and a date range in an export profile. For agent queries, sign in, pair the phone, select the profile’s data and connect https://myself.md/mcp in a compatible client. The phone must be available to complete a live query; an authorized stored cloud export is a separate read path.

Does myself.md support Android Health Connect?

Yes. The Android app reads supported Health Connect records after you grant permission. Select the records and date range in a profile, then export to files or approve access for a compatible MCP assistant. Historical access may be limited to 30 days without additional permission, and exercise routes can require separate consent. Check the public health dataset catalog for supported types and limitations.

Can Claude or Codex use my health data through myself.md?

Compatible Claude and Codex clients can connect to https://myself.md/mcp using OAuth. Sign-in alone grants no health records: pair your phone and approve specific profiles and data grants. Ask the assistant to discover available data, query an approved profile and wait for completion. Client tool availability varies; the setup guide documents handoffs and limitations. You can revoke future reads, but cannot recall copies already delivered to an AI provider.

Where can I install myself.md, and does the phone need to stay open?

Public App Store and Google Play downloads are coming soon. Live phone queries require an installed app or authorized test build; developers can use the source setup instructions on GitHub. Keep the app open and connected while verifying a live query, with the required operating-system permissions enabled. You can explore the public dataset catalog without installing anything. Reading an already-approved cloud export is a separate path that does not require a live phone query.

Can an agent access my data without approval?

No. OAuth sign-in, a paired phone, selected profile types and OS source permissions are required.

Can I try myself.md without an account?

Yes. The app is free to use without an account, with an optional one-time lifetime purchase for unlimited exports and queries. Optional cloud storage requires an account.

Which data can myself.md export?

Health, screen time and recorded location data supported by the installed phone adapters. Operating-system permissions and platform limitations apply.

How do I revoke an agent’s access?

Review and revoke sharing permissions in the phone app or authenticated dashboard. Revocation prevents future reads but cannot recall copies already delivered.

What happens to my cloud files if a storage subscription ends?

Paid storage continues while your store subscription is active or in the store’s billing grace period. If paid storage ends and your exports exceed your remaining allowance (100 MB with Lifetime, zero otherwise), you have 30 days to resubscribe or delete files. Reminders arrive by push notification and email when this starts, 7 days before and 1 day before. After 30 days, the oldest cloud exports are deleted until usage fits that remaining allowance. Phone files are not affected.