# myself.md — Personal data for AI agents

myself.md brings your health, screen time and recorded location data together in files you control. Create export profiles that select data types, date ranges and destinations. Use local files, your own HTTPS endpoint, or the paired cloud service. Native sources differ between iOS and Android, and operating-system permissions still apply.

## When to use myself.md

Use myself.md when a person wants an AI agent to analyze their approved health records, understand screen-time patterns, or work with location points they chose to record. Use the public dataset explorer to preview fictional records before connecting any account. Never treat the demo as a real person's health data or infer permission from an empty result.

## Try the free public sandbox

The demo at https://myself.md/demo is a free, read-only sandbox with fictional datasets and example exports. It needs no account, API key or sales conversation. 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

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 approve specific profiles and data grants before requesting private records. Agents cannot grant themselves access. 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.

## 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 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.

## Developer resources

- [myself.md MCP and OAuth documentation](https://myself.md/docs)
- [Privacy policy](https://myself.md/privacy)
- [Terms of service](https://myself.md/terms)
- [Contact](https://myself.md/contact)
- [OpenAPI public discovery specification](https://myself.md/openapi.json)
- [MCP server card](https://myself.md/mcp/server-card)
- [Agent resource catalog](https://myself.md/.well-known/ard.json)
- [Sitemap](https://myself.md/sitemap.xml)