# telo Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## telo

Ask about your sleep, HRV and workouts from Apple Health, and pin charts to your telo home.

- Record: https://musedirectory.ai/connector/telo
- Category: Health
- Developer: telo (https://telo.health/apple-health-mcp)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 185ms, checked 2026-11-07T02:15:54Z
- Endpoint: https://telo.health/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-05T13:01:11Z)
- Source: Found in the official MCP Registry (health.telo/telo) https://registry.modelcontextprotocol.io/v0/servers?search=health.telo%2Ftelo

Connects to your Apple Health history through the telo iPhone app. Muse can review sleep, HRV, workouts and daily metrics, plan workouts for your Apple Watch, and pin charts, countdowns and date notes to your telo home screen.

Example request: "How has my sleep and HRV been this month, and can you pin a chart of it to my home screen?"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use telo to help me. It is a free service with an MCP server at https://telo.health/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- create_workout_plan: Create one structured workout requested by the user, scheduled within the next 7 days. Stores a pending plan; does NOT immediately deliver to or start Apple Watch. The first delivery is manual: open telo on iPhone > Planned workouts and tap Schedule on Watch to grant permission. 
- workout_plans: Read the latest 50 planned workouts, or one by id, including the original prescription, delivery state and first exactly linked HealthKit workout. pending awaits iPhone processing (manual review, or automatic scheduling if enabled on that iPhone); scheduled means the iPhone sched
- cancel_workout_plan: Request cancellation of the user's identified workout plan. The iPhone must process removal, either during an automatic refresh or by opening telo > Planned workouts. Does not delete any recorded HealthKit result. Idempotent; cancel_requested is NOT confirmation of removal from A
- data_status: Inspect before health reviews or investigating missing data. Returns the last received upload batch, collection date ranges/counts and per-metric coverage. Not a sync command. history_import is the iPhone's own report of its history import (complete, still arriving, or unknown fo
- list_metrics: Lists the available health metrics, the unit of each one, and how far back the data goes. Call this before query_daily if you do not know the exact metric names.
- query_daily: Daily records or week/month aggregates. aggregation identifies sum or unweighted average of stored daily values; daily_min/max are extrema of daily values, not raw samples. days_present counts stored dates; days_expected counts calendar dates in period_start/end clipped to the re
- workout_detail: Detail for a workout UUID from sessions. Includes source/device, indoor flag, pool length, elevation gain, laps, classified segments, paired pause intervals, a swimming summary and reduced series when accessible in HealthKit. Summaries, events and zones are permanent; only raw se
- sessions: Sleep nights or workouts within an inclusive date range. Workout activity accepts run/bike/swim (or running/cycling/swimming). granularity=week groups workouts by Monday date and modality, summing duration, distance and estimated HR-zone seconds. Boundary weeks cover only the req
- derived_metrics: Duration-based training workload (minutes), excluding walking unless include_walking=true: rolling ATL 7 days, CTL 42 days, same-day TSB=CTL-ATL and acute/chronic ratio. Not intensity-weighted TSS. Every training row includes trimp_load, trimp_atl, trimp_ctl and trimp_tsb: simple
- home: Read the cards on the user's telo iPhone home screen, the dated marks they asked you to keep (e.g. 'Sick', 'Intervals start'), and recent changes. Marks are context the user gave about their life; use them when interpreting their data. Call before editing the home.
- pin_card: Put a live chart on the user's telo iPhone home. Only when the user asks to pin, save, show or keep something on telo. The card keeps updating with each sync. Styles: trend (line), stat (number and change), bars. Optional: compare_with draws a second metric on the same window; ba
- pin_countdown: Add a countdown to a date the user named (a race, a trip, a test) to their telo home. telo counts days; it never judges them.
- edit_card: Change one card: title, window, style, comparison, usual range, color, size, change_from, or a goal the user stated. null removes an option. Call home first for ids.
- arrange_home: Reorder cards, remove cards or remove marks, when the user asks to set up or tidy their home (e.g. 'set my home up for race week'). The reason is shown to the user in the change history, and every change can be undone on the phone.
- mark_date: Keep a short note the user told you about a date or span (illness, travel, new training, new shoes). It appears on every telo chart covering that date and is returned by home to any assistant later. Only for facts the user stated, never your inference.
- report_gap: Call when the user asked for something telo cannot do with the tools here: a chart or layout on the telo home, a metric telo does not have, data that is missing, a question no tool answers. Pass their request in their words, what you tried instead, and what is missing. Then tell 

Screening checks:
- MCP handshake: pass (Answered in 185ms)
- Domain against threat feeds (Cloudflare security DNS): pass (telo.health not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: warn (workout_detail: Unusually long tool description)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 50 days ago)
- AI review of purpose and tool behavior: pass (No concerns)