Create your private account
Your membership, sessions, and authorization stay isolated from every other user.
Private wearable context for your AI
Your body knows. Now your AI can listen.
Wearable Context gives the AI clients you authorize precise, read-only access to your connected wearable data through one private MCP connection.
- Read-only
- Encrypted access
- Disconnect any time
Example contextToday · Aug 22
WHOOP connected82%
RecoveryReady for strainHRV 68 ms · RHR 52 bpm
Recovery82%
Sleep7:42h
Day strain14.3
Built as a gateway, not another health dashboard.
Official provider APIs
Standards-based MCP
No advertising or tracking
One connection, useful context
From wearable data to answers in three clear steps.
Connect a wearable with consent
Choose a supported provider and authorize only the read scopes needed for its data.
Add it to your AI client
Use one remote MCP URL, sign in, and approve access before the client can read anything.
Private by architecture
Your health data is context—not the business model.
Wearable Context is intentionally narrow. It retrieves official provider data only when needed for your request, transforms it in memory, and returns it to the client you authorized.
Read the privacy policyNo permanent health record
Wearable measurements are not stored in the application database.
Read-only by design
No workout, journal, or provider-account mutation tools are exposed.
You hold the off switch
Disconnect a wearable provider or revoke a client from your dashboard whenever you choose.
The useful signal
The context your client can request from WHOOP today.
WHOOP is the first supported provider; connection discovery is provider-agnostic.
01Cycles
02Recovery
03Sleep
04Workouts
05Body measurements
06Deterministic trends
Wear your context
Give your AI a better starting point.
Connect your own wearable account and keep control of who can read it.