What you need
An iPhone with Apple Health records, the telo app from the App Store, and a Perplexity plan with custom connectors (Pro, Max or Enterprise). In telo, sign in and send your history; the first sync must finish before anything can be read.
On Enterprise, an admin must first allow members to add custom connectors. The steps follow the Perplexity documentation reviewed on the date above; they are not a claim that every version has been tested with telo.
Add the Apple Health MCP connector
- Open Plugins in the sidebar. If it is not there yet, go to Customize, then Connectors.
- Choose Add custom, then Add MCP connector, then Remote.
- Name: telo. MCP server URL: https://telo.health/mcp.
- Under Advanced, set Authentication to OAuth and Transport to Streamable HTTP. Leave Client ID and Secret empty: telo supports dynamic client registration.
- Tick the acknowledgement and choose Add.
Sign in with OAuth
Select the telo card to start the sign-in and turn it on. A telo page opens in your browser. Enter your email, type the 6-digit code and approve access. Never paste a code or token into the chat.
A connection made once applies to your Perplexity account on every surface.
Check that Perplexity can read Apple Health
- Turn telo on under Sources on the home screen.
- Ask, naming the connector: use telo to list my available metrics and the dates they cover.
- Confirm the answer comes from a telo tool call with real dates. If it describes data without calling a tool, it is guessing.
A first prompt
Asking for coverage first keeps gaps visible. A missing day is unavailable, not zero.
Use telo to check which Apple Health metrics are available and how recent they are. Then compare my sleep and resting heart rate over the last 7 days with the 7 days before, and list the dates with missing records.Troubleshooting and removal
If the card shows an error tag, sign in again from the card. If Add custom is missing, the plan does not include custom connectors or the Enterprise admin has not allowed them.
To remove telo, use the ⋮ menu on the connector. If the connection works but records are missing, check the sync in the telo app. A working MCP connection does not prove that HealthKit read permissions were granted on the iPhone.
Practical questions
Does Perplexity read Apple Health on its own?
No. Perplexity reads custom remote MCP connectors, and Apple Health stays on the iPhone. telo receives the data from the iPhone app and answers through its MCP server.
Do I need a paid Perplexity plan?
Custom remote connectors are a paid feature: Pro, Max or Enterprise, with Enterprise admins allowing them first.
Which transport should I pick?
Streamable HTTP, with OAuth for authentication. telo needs no API key and no client secret.
Sources and availability
Plans, regions and interfaces can change. Check the official sources before setting up.
How this guide was prepared
Prepared with AI assistance using the cited official documentation and the telo workflow described in the project. Screens and permissions can vary by account. This review did not include a complete authenticated test in each assistant.