What you need
An iPhone with Apple Health records, the telo app from the App Store, and Muse Code installed and signed in. In telo, sign in and send your history; the first sync must finish before Muse Code can read anything.
This guide is about Muse Code from Meta, not the Muse meditation headband, which writes its own sessions into Apple Health. The setup follows the Muse Code MCP documentation; it is not a claim that every version has been tested with telo.
Turn off Contributor mode first
On a Muse Code subscription, Contributor mode is on by default, and Meta may use prompts, files and context to train future models. Tool results from telo become part of that context. Turn it off before connecting health records: open /settings and change the Contributor mode row, or start Muse Code with --contributor-mode off, or set MUSE_CONTRIBUTOR_MODE=0.
Check the current Meta terms for your account type. Pay-as-you-go and Zero Data Retention accounts do not have the setting.
Add the Apple Health MCP server in settings.json
Muse Code has no command to add a server. Put the block above in ~/.config/muse/settings.json, merged with what is already there. The schema_version key is required.
Do not add an Authorization header. telo uses OAuth, and Muse Code stores and refreshes the token itself.
{
"schema_version": 1,
"mcp_servers": {
"telo": {
"transport": "streamable_http",
"url": "https://telo.health/mcp"
}
}
}Sign in with OAuth
The command opens a telo page in your browser. Enter your email, type the 6-digit code and approve access. If a session starts before you log in, Muse Code reports the 401 and prints this same command.
muse mcp login teloCheck that Muse Code can read Apple Health
- Start muse and run /mcp. telo should be connected, with tools named mcp__telo__ followed by the tool name.
- Ask Muse Code to use telo to list 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. If you ask Muse Code to save the analysis, mind where the file lands: a repository commit can publish your health records.
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
If Muse Code stops at startup, the server is in the default required mode and failed to connect. Run muse mcp login telo again, or set "mode": "optional" on the telo entry so the run continues with a warning.
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. To remove access, run muse mcp logout telo.
Practical questions
Does Muse Code have an Apple Health integration?
No. The Muse Code documentation does not mention Apple Health or HealthKit. To read those records it needs an MCP server, such as telo, which receives the data from the iPhone app.
Can Meta train models on my health data?
On a subscription, Contributor mode is on by default and lets Meta use prompts and context for training, and what telo returns becomes part of that context. Turn it off in /settings, with --contributor-mode off or with MUSE_CONTRIBUTOR_MODE=0 before connecting.
Can I use the telo skills in Muse Code?
Yes. Muse Code reads skills from ~/.claude/skills and ~/.agents/skills, and muse skills install adds a folder with a SKILL.md. The telo skills are instructions only; queries are answered by the MCP server after login.
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.