Totem
Let your coding agent read and reason over your Whoop recovery, sleep, strain, and workouts without opening the app.
Overview
Totem is a Build-phase MCP server that exposes 48 Whoop wearable tools so AI coding agents can read your fitness and recovery data over stdio.
What is this MCP server?
- 48 MCP tools for full Whoop access via the private iOS API surface
- stdio npm package @briangaoo/totem (v1.4.3) for agent hosts
- `totem auth` CLI flow: email, password, SMS MFA, tokens written to .env
- Bearer auto-refresh ~24h; Cognito refresh token ~30-day lifetime
- Positioned as multi-wearable Totem stack with Whoop as the first supported device
- 48 MCP tools documented for Whoop access
- Server package version 1.4.3 on npm as @briangaoo/totem
- Bearer token auto-refresh cycle about every 24 hours
Community signal: 66 GitHub stars.
What problem does it solve?
Your agent cannot see Whoop recovery, sleep, or strain unless you manually paste summaries from the mobile app.
Who is it for?
Indie builders who wear Whoop and want recovery-aware planning, journaling, or custom dashboards driven from Claude Code or Cursor.
Skip if: Teams without a Whoop subscription, builders who refuse storing Cognito tokens locally, or anyone needing official public Whoop OAuth apps only.
What do I get? / Deliverables
After `totem auth` and MCP registration, your agent can call Whoop-backed tools directly from the IDE with auto-refreshed tokens.
- Registered stdio MCP server your agent can invoke for Whoop reads
- Refreshed Cognito token pair maintained via totem auth workflow
- Access to 48 Whoop-oriented MCP tools from the Totem package
Recommended MCP Servers
Journey fit
Wearable APIs are wired into the agent stack during product build, not during ideation or launch copy. Totem is an MCP integration that exposes 48 Whoop tools over stdio so Claude Code, Cursor, or Codex can query live fitness telemetry.
How it compares
MCP wearable integration with 48 Whoop tools, not a fitness coaching skill or a hosted analytics SaaS.
Common Questions / FAQ
Who is io.github.briangaoo/totem for?
Solo developers using AI agents who want programmatic access to their own Whoop data through the Model Context Protocol.
When should I use io.github.briangaoo/totem?
When you are building agent workflows—weekly reviews, health-aware scheduling, or logging—that need live Whoop metrics inside your editor.
How do I add io.github.briangaoo/totem to my agent?
Install @briangaoo/totem, run `totem auth` to populate WHOOP_IOS_BEARER_TOKEN and WHOOP_COGNITO_REFRESH_TOKEN, then add the stdio MCP server block in Claude Code, Cursor, or Codex with those env vars.