# totem [Health: Active] **Category:** πŸ’» Developer Tools **Repository:** https://github.com/briangaoo/totem **GitHub Stars:** 114 **Views:** 0 **Installs:** 0 **Upvotes:** 0 **Directory Page:** https://allmcps.com/mcp/totem ## Description Totem β€” talk to your wearables with AI. Today: full Whoop access (48 tools). ## Claude Desktop Quick Installation Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client: ```json "mcpServers": { "totem": { "url": "https://img.shields.io/badge/Claude_Code-a855f7?style=for-the-badge" } } ``` ## Documentation & README

totem β€” 55 tools, 47 microservices, 311 endpoints

Totem gives Claude (or any MCP-compatible AI) full read + write access to your wearable data. Today it speaks Whoop β€” every metric, through Whoop's private iOS API.

Claude Code Claude Desktop ChatGPT Desktop Codex Gemini CLI any MCP 1.x client

tools typescript node mcp deploy

β–Ά 2-min demo β€” the full totem cloud flow: install β†’ Whoop login β†’ Fly deploy β†’ Claude connector β†’ first query.

55 tools, structured zod-validated outputs, bundled catalogs (372 exercises, 308 behaviors, 203 sports, 311 endpoints), write-safety harness, automatic Cognito token refresh, bounded in-memory read cache. TypeScript 6, Node 24, 278 tests. > **Totem is becoming a universal wearables bridge.** Whoop is the first adapter β€” every metric, fully wired. Fitbit, Apple Watch, and Garmin are in progress ([contributors welcome](https://github.com/briangaoo/totem/blob/HEAD/CONTRIBUTING.md)). The MCP + projection layer is device-agnostic; an adapter just maps its source into the same shared schemas, so everything below applies to whatever you wear. > *Note: this works through Whoop's private iOS API rather than the public OAuth API. That isn't what Whoop's terms allow β€” see the [FAQ](#faq) if you want the full picture before installing.* --- ## Table of contents 1. [Get Started](#get-started) 2. [Why this exists](#why-this-exists) 3. [What it does](#what-it-does) 4. [Architecture](#architecture) 5. [The 55 tools](#the-55-tools) 6. [Authentication](#authentication) 7. [Write-safety harness](#write-safety-harness) 8. [Bundled catalogs](#bundled-catalogs) 9. [Configuration](#configuration) 10. [Remote hosting](#remote-hosting) - [Deploying to Hugging Face Spaces (free hosting)](#deploying-to-hugging-face-spaces-free-hosting) 11. [The `totem` CLI](#the-totem-cli) 12. [Privacy + security](#privacy--security) 13. [Troubleshooting](#troubleshooting) 14. [Comparison to alternatives](#comparison-to-alternatives) 15. [FAQ](#faq) 16. [Disclaimers](#disclaimers) 17. [Acknowledgments](#acknowledgments) **Other root-level docs:** [`TOOLS.md`](https://github.com/briangaoo/totem/blob/HEAD/TOOLS.md) (full per-tool reference) Β· [`WHOOP.md`](https://github.com/briangaoo/totem/blob/HEAD/WHOOP.md) (full API reference) Β· [`CHANGELOG.md`](https://github.com/briangaoo/totem/blob/HEAD/CHANGELOG.md) Β· [`CONTRIBUTING.md`](https://github.com/briangaoo/totem/blob/HEAD/CONTRIBUTING.md) Β· [`SECURITY.md`](https://github.com/briangaoo/totem/blob/HEAD/SECURITY.md) Β· [`LICENSE`](https://github.com/briangaoo/totem/blob/HEAD/LICENSE) --- ## Get Started **Prerequisites:** Node 24+ and a Whoop account (any membership tier). ```bash git clone https://github.com/thebriangao/totem.git cd totem && npm install && npx tsc && npm link ``` That puts `totem` on your PATH (the one-time `npx tsc` builds it; after that every workflow is a `totem` command β€” there are no `npm run` scripts). Now run **one guided command** β€” each handles Whoop login (SMS included), setup, and connecting to Claude from end to end. Pick how you want to run it: ### β˜… Recommended β€” `totem cloud` Deploys the server to a host and connects it to Claude on **web, desktop, and mobile**, synced across every device on your account. One command walks through: 1. **Whoop login** β€” email + password, plus the SMS code if your account has MFA. Tokens are saved locally and pushed to the host. 2. **Pick a host** β€” Fly (automated + tested), Railway, Google Cloud Run, or your own server (guided Docker steps). 3. **Secrets** β€” generates `MCP_AUTH_TOKEN` and asks you to choose a connector password. 4. **Deploy + verify** β€” sets env, deploys, confirms `/health` and the OAuth endpoints are live. 5. **Connect** β€” prints ready-to-paste setup for **claude.ai, ChatGPT, Claude Code (remote), and Cursor / Windsurf / any HTTP MCP client** (URL + password for the OAuth connectors, a bearer-token block for the rest), and opens claude.ai's connector page. ```bash totem cloud ``` ### Local only β€” `totem local` Runs the server on this machine over stdio β€” no hosting, this device only. Walks through Whoop login β†’ build β†’ wiring it into the client you pick: **Claude Desktop, Claude Code, Cursor, VS Code (Copilot), Gemini CLI, Codex CLI, or Windsurf** β€” it writes the right config to the right path automatically (or prints a universal block for any other MCP client). Restart the client and you're set. ```bash totem local ``` ### Keeping it alive Whoop's tokens expire roughly every 30 days. When they do, re-run the same command β€” it re-logs you in and (if you deployed) pushes the new tokens to your server: ```bash totem auth ``` Silent if your account has no SMS MFA; prompts for the code if it does. Pushes fresh tokens to your deployment automatically. ### Check it works Ask Claude: *"how am I doing today on whoop?"* β€” you should get structured recovery / sleep / strain back. > Prefer to wire everything up by hand? The guided commands just automate the steps documented in [The `totem` CLI](#the-totem-cli), [Remote hosting](#remote-hosting), and [Configuration](#configuration). Stuck? See [Troubleshooting](#troubleshooting). --- ## Why this exists Whoop ships two APIs: - The **public developer API** at [`developer.whoop.com`](https://developer.whoop.com/api/) is OAuth2, read-only, and exposes **13 endpoints** under 6 scopes. You get recovery score, sleep stage totals, workout strain, body measurements (3 fields), and HRV/RHR per cycle. No journal, no Strength Trainer, no Whoop Coach, no hypnogram, no stress monitor, no trends, no writes, nothing else. Numeric `sport_id` was removed 2025-09-01. - The **private iOS API** is what the actual Whoop app uses β€” `api.prod.whoop.com` behind AWS Cognito. **311 distinct operations across 47 microservices**, including everything missing from above. This MCP wraps the iOS surface. ### What the iOS API has that the public OAuth doesn't | Capability | Tool | |---|---| | HRV / RHR / respiratory / VO2 / weight time-series (25 metrics Γ— up to 4 windows) | `whoop_trend` | | Hypnogram (per-stage sleep timeline) + full stage breakdown (ms + %) + in-sleep HR | `whoop_sleep` | | Strength Trainer β€” every set, every workout, full 372-exercise catalog, PRs | `whoop_lift_*` (8 tools) | | 308-behavior Journal + behavior impact analysis | `whoop_journal*` (5 tools) | | Stress monitor (intraday timeline) | `whoop_stress, whoop_live_stress` | | Whoop Coach AI chat | `whoop_coach_ask` | | Smart Alarm (read + 4 write modes) | `whoop_smart_alarm*` | | HR zones (read + configure max HR / 5 custom zones) | `whoop_hr_zones*` | | Compare-windows, sleep coach, calendar grid, performance assessment | `whoop_compare`, `whoop_sleep_need`, `whoop_calendar`, `whoop_performance_assessment` | | Live HR / activity state / live stress | `whoop_live_*` (3 tools) | | Community leaderboards, hidden metrics, women's health (cycle / symptoms / MCI) | `whoop_leaderboard`, `whoop_hidden_metric`, `whoop_cycle*` | | **15 write tools** β€” log workouts, journal entries, profile edits, smart-alarm config, edit sleep times | various | If recovery + sleep totals + workout list is enough for you, use the public OAuth API. If anything in the table is interesting, you need this. The iOS API was discovered via mitmproxy β€” full methodology in [`WHOOP.md`](https://github.com/briangaoo/totem/blob/HEAD/WHOOP.md). --- ## What it does The MCP runs as a local Node process. It speaks **Model Context Protocol** over stdio (or HTTP for remote deployments), registers 55 tools at startup, and waits for tool calls from a connected MCP client. When a tool is called: 1. Authenticates via the cached Cognito access token (auto-refreshes if expired) 2. Issues HTTP requests to `api.prod.whoop.com` 3. Walks the response to extract a flat domain object (the **projection** step) 4. Validates the projected object against a zod schema (catches Whoop API drift) 5. Returns the structured JSON to the MCP client Writes follow the same path plus a **preview gate**: every write tool defaults `confirm: false`, returning a preview of what would be sent. Claude must explicitly re-call with `confirm: true` to fire. See [The 55 tools](#the-55-tools) for the full per-tool reference. --- ## Architecture ``` Claude Desktop / Code ──stdio──▢ src/server.ts ──▢ 49 tool handlers β”‚ β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β–Ό β–Ό β–Ό schemas (zod) projections (rawβ†’flat) whoop/client β”‚ β–Ό HTTPS api.prod.whoop.com ``` ### Three layers per tool Every tool is a schema + projection + handler: - **`src/schemas/.ts`** β€” zod schema. The contract Claude sees. Used at runtime to validate the projection's output before returning. - **`src/projections/.ts`** β€” pure function turning Whoop's raw BFF response into a flat object. All the "Whoop puts this data over there, not where you'd expect" knowledge lives here. Tested against captured fixtures. - **`src/tools/v2/.ts`** β€” ~25-100 lines. Registers the tool, parses input args, calls the client, runs the projection, validates with zod, returns. Almost no logic in the tool file. That's all in the projection β€” which makes the codebase highly testable (projections are pure transformations, tested against `tests/fixtures/*.json` without hitting the network). ### Shape drift handling When Whoop changes a response shape, the projection emits unexpected data, zod's `.parse()` fails, and the MCP throws `WhoopProjectionError` instead of silently returning malformed data to Claude. Fix: use `whoop_raw` + `whoop_endpoints` to capture the new shape, update the projection, update the fixture, ship. > **Recent example:** in May 2026, Whoop migrated recovery + strain deep-dives from `GRAPHING_CARD` tiles (keyed by `content.title` like `"RECOVERY"`) to `SCORE_GAUGE` + `CONTRIBUTORS_TILE` items with stable `content.id` keys (`RECOVERY_SCORE_GAUGE`, `CONTRIBUTORS_TILE_HRV`). Other deep-dives still use the old card-based shape. The escape-hatch tools made the migration trivial to debug. --- ## The 55 tools Compact summary. **Full per-tool reference (input shape Β· source endpoints Β· output shape Β· notes) β†’ [`TOOLS.md`](https://github.com/briangaoo/totem/blob/HEAD/TOOLS.md).** Tools marked ⚠️ are writes (default `confirm: false`, preview-first). Tools marked ⚑ are compact/aggregate reads that fold several source calls into one lower-token response; `whoop_weekly_plan` is ⚑ **experimental** (its endpoint shape hasn't been verified against a live account yet). | Group | Tools | |---|---| | **Snapshots & profile** (6) | `whoop_today` Β· `whoop_day` Β· `whoop_daily_brief` ⚑ Β· `whoop_weekly_plan` ⚑ Β· `whoop_profile` Β· `whoop_calendar` | | **Deep dives** (3) | `whoop_recovery` Β· `whoop_sleep` Β· `whoop_strain` | | **Trends** (3) | `whoop_trend` Β· `whoop_trend_pack` ⚑ Β· `whoop_compare` | | **Stress + sleep coach** (2) | `whoop_stress` Β· `whoop_sleep_need` | | **Live** (4) | `whoop_live_hr` Β· `whoop_live_state` Β· `whoop_live_stress` Β· `whoop_activity_now` ⚑ | | **Activities** (5) | `whoop_workouts` Β· `whoop_workout` Β· `whoop_sports_catalog` Β· `whoop_activity_create` ⚠️ Β· `whoop_activity_delete` ⚠️ | | **Strength reads** (7) | `whoop_lift_prs` Β· `whoop_lift_exercise` Β· `whoop_lift_progression` Β· `whoop_lift_history` Β· `whoop_lift_overview` ⚑ Β· `whoop_lift_library` Β· `whoop_lift_catalog` | | **Strength writes** (3) | `whoop_lift_log` ⚠️ Β· `whoop_lift_template_save` ⚠️ Β· `whoop_lift_custom_exercise` ⚠️ | | **Journal** (5) | `whoop_journal` Β· `whoop_journal_catalog` Β· `whoop_behavior_impact` Β· `whoop_journal_log` ⚠️ Β· `whoop_journal_autopop` ⚠️ | | **Women's health** (3) | `whoop_cycle` Β· `whoop_cycle_log` ⚠️ Β· `whoop_symptom_log` ⚠️ | | **Coach + performance** (2) | `whoop_coach_ask` ⚠️ Β· `whoop_performance_assessment` | | **Smart alarm** (2) | `whoop_smart_alarm` Β· `whoop_smart_alarm_set` ⚠️ | | **Social** (2) | `whoop_leaderboard` Β· `whoop_communities` | | **Settings** (5) | `whoop_hr_zones` Β· `whoop_preferences` ⚑ Β· `whoop_hr_zones_set` ⚠️ Β· `whoop_profile_update` ⚠️ Β· `whoop_hidden_metric` ⚠️ | | **Escape hatch** (2) | `whoop_raw` Β· `whoop_endpoints` | **Total: 55** (38 reads + 15 writes + 2 escape hatches). For each tool's input args, source endpoint(s), and output shape, see [`TOOLS.md`](https://github.com/briangaoo/totem/blob/HEAD/TOOLS.md). --- ## Authentication Whoop's iOS app uses **AWS Cognito** routed through a Whoop-owned proxy (`/auth-service/v3/whoop/`). The proxy fills in `ClientId` + `SECRET_HASH` server-side β€” no IPA extraction needed. **Bootstrap once** (email + password + SMS MFA code if your account has it on) β†’ tokens written to `.env`. **After that, it's hands-off**: access tokens auto-refresh every 24h via the refresh token; refresh token lives ~30 days. Single-flight refresh gate prevents thundering-herd refreshes when concurrent tool calls all see a stale token at the same time. Auth requests impersonate the iOS AWS Swift SDK (the proxy 403s a Node-style User-Agent), and data requests carry the **WHOOP iOS app's own identity headers** (`user-agent: iOS`, the `x-whoop-*` device set, a per-install identifier) so the traffic blends with the legitimate app rather than standing out β€” see [`WHOOP.md` β†’ Headers for data requests](https://github.com/briangaoo/totem/blob/HEAD/WHOOP.md) for the full set and the reasoning. **Error classes** (`src/whoop/errors.ts`): | Error | When | Behavior | |---|---|---| | `WhoopAuthExpiredError` | 401 from Whoop | TokenManager refreshes on next call | | `WhoopApiError` | 4xx with body | Description surfaced to caller | | `WhoopServerError` | 5xx | Transient β€” retry | | `WhoopProjectionError` | Projection output failed zod parse | Whoop changed shape β€” fix the projection | When refresh-token lifetime expires (~30 days), re-run `totem auth`. It auto-detects local vs deployed and, for a deployment, pushes the new tokens to it. Brand-new SMS code (if your account has MFA), fresh 30-day window. --- ## Write-safety harness Every write tool defaults `confirm: false`. The first call returns a **preview** of what would execute. Claude must explicitly re-call with `confirm: true` to fire the actual request. Without the gate, a hallucinated "log my workout" could create garbage activities on your account. The preview shape (lives in `src/whoop/write_safety.ts`): ```json { "preview": true, "will_execute": { "method": "POST", "path": "/weightlifting-service/v2/weightlifting-workout/activity", "body_summary": { "exercise_count": 3, "set_count": 12, "exercise_list": [{"name": "BENCHPRESS_BARBELL", "set_count": 5}, ...] } }, "set_confirm_true_to_run": true } ``` Claude reads this back to you, you confirm, Claude re-calls with `confirm: true`, the actual POST fires. Every write tool's output schema is a `withPreview(ReceiptSchema)` discriminated union β€” preview or receipt, never both. --- ## Bundled catalogs Four datasets compiled into the MCP at build time (not fetched at runtime): | Catalog | Entries | Catalog tool | Use | |---|---:|---|---| | `behaviors.ts` | 308 | `whoop_journal_catalog` | Journal behavior validation | | `exercises.ts` | 372 | `whoop_lift_catalog` | Strength Trainer exercises | | `sports.ts` | 203 | `whoop_sports_catalog` | `sport_id` ↔ name | | `endpoints.ts` | 311 | `whoop_endpoints` | API path search | **Local lookups, no prompt bloat**: the catalog tools are zero-network local searches, so the full 372-exercise / 308-behavior / 203-sport lists stay out of the system prompt (~14k tokens saved). The ID-taking write tools (`whoop_activity_create`, `whoop_lift_log`, `whoop_journal_log`, …) validate their IDs β€” or an exact catalog name β€” against these bundled datasets before any request fires, rejecting unknown values with an actionable error. (A session-scoped "must call the catalog first" gate existed through 1.4.4; it was removed in favor of this consistent local validation.) --- ## Configuration ### Environment variables | Variable | Required | Description | |---|---|---| | `WHOOP_EMAIL` | yes | Your Whoop login email | | `WHOOP_PASSWORD` | yes (bootstrap only) | Your Whoop login password (used only during bootstrap) | | `WHOOP_IOS_BEARER_TOKEN` | yes | Cognito access token (24h, auto-refreshed) | | `WHOOP_COGNITO_REFRESH_TOKEN` | yes | Cognito refresh token (~30d) | | `WHOOP_USER_ID` | no | Your Whoop user ID β€” used by `whoop_profile`, `whoop_leaderboard`. Avoids one bootstrap call per session. | | `WHOOP_TIMEZONE` | no | IANA timezone (e.g., `America/Los_Angeles`). If unset, auto-detected from your Whoop profile and refreshed hourly. Set explicitly to override. | | `WHOOP_INSTALLATION_ID` | no (auto) | The per-install device identifier sent as `x-whoop-installation-identifier`. Generated once and written to `.env` on first run β€” don't set it by hand. | | `WHOOP_TOKEN_STORE` | no | `envfile` (default β€” persists refreshed tokens back to `.env`) or `memory` (for read-only filesystems; re-bootstrap every ~30 days). | ### Claude Desktop config ```json { "mcpServers": { "whoop": { "command": "/opt/homebrew/bin/node", "args": ["/absolute/path/to/totem/dist/server.js"] } } } ``` The MCP loads `.env` from the repo root (relative to `server.js`). Use absolute paths β€” Claude Desktop doesn't inherit shell `PATH`. --- ## Remote hosting The MCP also speaks HTTP β€” deploy once, use from multiple devices. Same 55 tools, same auto-refresh, behind a bearer-token gate at a URL. ```bash # 1. Local bootstrap (Cognito needs an interactive MFA prompt) totem auth # 2. Build + deploy via the shipped Dockerfile (Fly/Railway/Render/VPS β€” all work) docker build -t totem . # 3. Run with env: WHOOP_EMAIL, WHOOP_IOS_BEARER_TOKEN, WHOOP_COGNITO_REFRESH_TOKEN, # MCP_TRANSPORT=http, MCP_AUTH_TOKEN=$(openssl rand -hex 32) ``` ### Deploying to Hugging Face Spaces (free hosting) [Hugging Face Spaces](https://huggingface.co/spaces) provides **free Docker hosting** β€” a zero-cost alternative to Fly or Railway. Connecting to **claude.ai web and Claude mobile** as a custom connector requires a **Claude Pro plan**, but the server itself runs for free on HuggingFace. > **Note:** HuggingFace Spaces routes all external traffic through port **7860** only, but this repo's Dockerfile defaults to `3000`. The server reads `PORT` from the environment, so just set `PORT=7860` as a Space variable (step 2 below) β€” no Dockerfile edit needed, and it'll listen on the right port. #### Step-by-step **1. Create a new Space** - Go to [huggingface.co/new-space](https://huggingface.co/new-space) - Select **Docker** as the Space SDK - Set the **visibility to Public** β€” HuggingFace Spaces must be public for Claude's connector to reach the `/mcp` endpoint **2. Add your secrets via the Space Settings UI** In your Space β†’ **Settings β†’ Variables and Secrets**, add the following. The token values go in as **Secrets** (hidden, never shown in logs); `PORT` and `PUBLIC_URL` aren't sensitive, so they can be plain **Variables**: | Secret name | Where to find the value | |---|---| | `WHOOP_EMAIL` | Your Whoop account email | | `WHOOP_IOS_BEARER_TOKEN` | From `totem auth` on your local machine (written to `.env`) | | `WHOOP_COGNITO_REFRESH_TOKEN` | From `totem auth` on your local machine (written to `.env`) | | `WHOOP_USER_ID` | From `.env` after running `totem auth` | | `MCP_AUTH_TOKEN` | Generate one with `openssl rand -hex 32` (or reuse the value from `.env.deploy` if you ran a deploy flow) | | `AUTH_PASSWORD` | A password you'll type once when adding the Claude connector | | `PUBLIC_URL` | Your Space's public URL β€” e.g. `https://-.hf.space` | | `PORT` | `7860` β€” HuggingFace's required port. Without this the container listens on 3000 and is unreachable. | > **Tip:** The `WHOOP_*` token values come from your local `.env` after running `totem auth`. `MCP_AUTH_TOKEN` you generate yourself (`openssl rand -hex 32`). **3. Push your code to the Space** Clone this repo and add your HuggingFace Space as a remote, then push: ```bash git clone https://github.com/thebriangao/totem cd totem # Add your HuggingFace Space as a remote git remote add hf https://huggingface.co/spaces// # Push the main branch git push hf main ``` HuggingFace will automatically build and run the Docker container. Watch the **Logs** tab in your Space to confirm it starts up and `/health` returns 200. **4. Connect to Claude** Once the Space is running, go to **claude.ai β†’ Settings β†’ Connectors β†’ Add custom connector**: - **MCP Server URL:** `https://-.hf.space/mcp` - Claude will open an OAuth flow β€” enter the `AUTH_PASSWORD` you set in your Space secrets > `MCP_AUTH_TOKEN` is used internally as the bearer token + JWT signing secret. You do **not** type it into Claude's connector UI β€” that field uses the OAuth `AUTH_PASSWORD` flow instead. **5. Re-authenticate when tokens expire (~30 days)** Whoop's Cognito tokens expire roughly every 30 days. Re-run `totem auth` on your local machine, then update `WHOOP_IOS_BEARER_TOKEN` and `WHOOP_COGNITO_REFRESH_TOKEN` in your Space's Secrets UI. The Space will restart automatically and pick up the new tokens. **Claude Desktop** doesn't natively speak remote MCP β€” bridge through stdio with [`mcp-remote`](https://www.npmjs.com/package/mcp-remote): ```json { "mcpServers": { "whoop": { "command": "npx", "args": ["-y", "mcp-remote", "https://your-app.fly.dev/mcp", "--header", "Authorization:Bearer your-mcp-auth-token"] }}} ``` **Claude Code** speaks remote MCP natively: `claude mcp add whoop --url ... --header ...`. **claude.ai web + Claude mobile app** can't use a bearer token β€” their custom-connector UI only supports OAuth. The server includes an OAuth 2.1 + PKCE authorization server for exactly this. Enable it by setting two extra env vars: ```bash AUTH_PASSWORD= PUBLIC_URL=https://your-app.fly.dev # your server's public origin (the OAuth issuer) ``` Then in Claude: **Settings β†’ Connectors β†’ Add custom connector**, paste `https://your-app.fly.dev/mcp`, and Claude walks the OAuth flow. It pops a small password page (served by your server) β€” enter `AUTH_PASSWORD`, approve, done. The connector then syncs across every device logged into your Claude account (web, desktop, mobile). The password gate means a stranger who finds your URL still can't connect without it. `MCP_AUTH_TOKEN` doubles as the JWT signing secret; leave `AUTH_PASSWORD` unset to disable this path. All of the above is what `totem cloud` automates for you β€” the manual steps here are for reference or hand-rolling. **When Cognito expires (~30 days)**: `totem auth` from your Mac. Silent if your account has no SMS MFA; prompts for the code if it does. Auto-detects your deployment and pushes the new tokens to it (Fly/Railway/Cloud Run/custom), ~10s restart. Requires being at a machine with the repo + the platform CLI. **Security**: bearer-token and OAuth paths both gate `/mcp`. Generate the token random (`openssl rand -hex 32`), HTTPS only, never commit, rotate if leaked. OAuth access/refresh tokens are stateless signed JWTs (survive restarts); auth codes are one-time + 60s-lived; PKCE S256 is enforced. `/health` is the only path without auth. --- ## The `totem` CLI `totem` is the single entry point for everything β€” there are no `npm run` scripts. It works from any directory (it resolves its own install path), so `totem deploy` from `~/Desktop` does the same thing as `cd totem && fly deploy`. ```bash # One-time, after cloning: npm install && npx tsc && npm link # the only npm steps; `npx tsc` does the first build totem # banner + full command list ``` Commands by group: | Group | Commands | |---|---| | **Get started** | `cloud` β˜… (guided server deploy + Claude connect) Β· `local` (guided local setup) | | **Setup** | `auth` (log in + save tokens β€” re-run to re-auth; auto-detects local vs deployed and pushes new tokens to your deployment) | | **Deployed** | `deploy` Β· `update` (interactive version picker + auto-update) Β· `logs` Β· `status` Β· `ping` | | **Local dev** | `start [--http]` Β· `dev` Β· `dev:http` Β· `build` Β· `test` Β· `typecheck` | | **Inspect** | `info` Β· `tools` Β· `config ` | | **Help** | `help` Β· `version` (+ `--help`, `-v` aliases) | Most people only ever need the two **Get started** commands plus `auth` (to re-auth when tokens expire). The rest are for power users β€” `totem ping` ("is my deploy alive"), `totem logs`, `totem start` (drop-in for `node dist/server.js`), etc. **Staying current β€” `totem update`.** An interactive updater. Run it and you get a version picker β€” every release, newest first, with dates and notes pulled from GitHub Releases. The newest is the default; pick anything older and it warns you what you'd be behind on (you can always run it again to go forward). After you choose, it applies the change with a guided, animated build β€” git installs fast-forward `main` (or check out the pinned tag), reinstall deps, and rebuild; npm installs reinstall the chosen version β€” then redeploys to your existing host and health-checks `/health`. A clean working tree is required (it won't clobber local edits), and a failed deploy leaves your live server untouched. After a successful update to the latest it offers **auto-update**. Turn it on and a background job (launchd on macOS, cron on Linux) checks for new releases every 6 hours and applies them the same way β€” pull, build, redeploy, health-check β€” logging to `.totem-autoupdate.log`. There's no push channel to your machine, so it's a scheduled poll, not instant. Toggle it directly anytime: ```bash totem update # interactive: pick a version, then optionally enable auto-update totem update --auto on # turn auto-update on (and pull the newest now) totem update --auto off # turn it off totem update --check # non-interactive: print installed-vs-latest + auto state ``` Versions are sourced from the places that already host them β€” git tags + GitHub Releases for git installs, the npm registry for global installs β€” so there's nothing extra to maintain. Auto-update is opt-in and only ever moves you to **released** versions (every release is CI-gated), never bleeding-edge `main`. --- ## Privacy + security - **Credentials live in `.env` on your machine.** Email, password, access token, refresh token β€” never leave your filesystem. Claude can't read them (it doesn't have filesystem access unless you wire in a filesystem MCP). - **The only outbound traffic is HTTPS to `api.prod.whoop.com`.** No telemetry, no analytics, no third-party servers. The MCP is open source β€” every line that touches your data is auditable. - **Write safety**: every write tool defaults to `confirm: false`. The preview shape includes what would be sent. You see it in chat before any mutation. To go further, remove specific writes from `src/tools/register.ts` or use Claude Desktop's "always require approval" setting. - **Hardened in 1.2.3**: token files are written `0600`, your account password is wiped from `.env` after login, OAuth tokens are audience-bound and signed with a key derived from `MCP_AUTH_TOKEN`, the HTTP server sends anti-clickjacking + CSP headers, the connector-password gate has a global brute-force ceiling, and deploy secrets are pushed over stdin (not argv). Full detail in [`SECURITY.md`](https://github.com/briangaoo/totem/blob/HEAD/SECURITY.md) and [`CHANGELOG.md`](https://github.com/briangaoo/totem/blob/HEAD/CHANGELOG.md). --- ## Troubleshooting **"AUTH FAIL: Cognito InitiateAuth failed (400)"** > Wrong email or password. Double-check `.env`. **"AUTH FAIL: Cognito MFA challenge missing Session token"** > The InitiateAuth response was malformed (unusual). Re-run `totem auth` β€” Cognito occasionally drops sessions. **"MFA verification did not return tokens"** > You entered the wrong SMS code (or it timed out). Codes expire after ~3 minutes. **"WhoopAuthExpiredError" after every call** > Your refresh token has expired (>30 days since last login). Re-run `totem auth` β€” it logs you back in, saves the tokens locally, and (if you deployed) auto-detects your host and pushes the new tokens to it in one step. If your account has MFA you'll get a fresh SMS code on your phone to type in the terminal. **"WhoopServerError: 502" / "503" / "504"** > Whoop's servers are having issues. Retry in 30 seconds. **Claude says it doesn't see any whoop tools** > Check `claude_desktop_config.json` paths are absolute. Restart Claude Desktop fully (quit, then reopen). > Check the MCP server runs without errors: `totem dev` β€” it should start silently and wait on stdin. **"WhoopApiError: 422 on /profile-service/v1/profile"** > Your `whoop_profile_update` body is too partial. Send most fields (gender from {MALE,FEMALE,NON_BINARY} only, birthday as YYYY-MM-DD or ISO datetime, country ISO-2). If `country=US`, also send `state` β€” Whoop returns 400 `"AdminDivision (state) must be set for US"` otherwise. **"Whoop API error 409 on /weightlifting-service/v2/weightlifting-workout/activity"** > Time window conflicts with an existing workout. Use a different range. **"WhoopProjectionError for whoop_X"** > Whoop changed a response shape. Capture the new response (e.g. via `whoop_raw`), inspect, update the projection. **Tests fail after `git pull`** > Pull may have updated captured fixtures. Run `totem test` again to see what changed. If projections need updating, that's the work. **`totem build` (or `npx tsc`) fails with "Top-level await is currently not supported with the 'cjs' output format"** > You're using an old Node. Upgrade to Node 24+. **"Error: ENOENT: no such file or directory, open '.env'"** > Create `.env` at the repo root (or wherever `dist/server.js` is being run from β€” the MCP loads `.env` relative to the entry). **"Cannot find module '@modelcontextprotocol/sdk/server/mcp.js'"** > Run `npm install`. **"AbortError: This operation was aborted"** > A request to Whoop's API took longer than 30s. Either Whoop is slow or your network is slow. Retry. --- ## Comparison to alternatives | Approach | Pros | Cons | |---|---|---| | **This MCP** | Full iOS API surface (55 total: 38 reads + 15 writes + 2 escape hatches), writes supported, structured outputs, auto-refresh, write-safety, bounded read cache | Unsupported by Whoop (see [FAQ](#faq) for what that means); reverse-engineered (Whoop could break it at any time); local install required | | Whoop's public OAuth API | Official, supported, 6 webhook events, scoped permissions | Only 13 endpoints; read-only; no journal/strength/stress/coach/smart-alarm/trends/hypnogram; numeric `sport_id` removed 2025-09-01; 429s exist | | HealthKit-based scraper | Bypass Whoop entirely; uses Apple's data sync | Loses Whoop-specific data (recovery score, journal, coach); requires iOS device involvement | | Direct mitmproxy capture | See everything | Manual, not programmable, doesn't scale | | Whoop iOS app + screenshots β†’ Claude | Works without code | Painful, slow, no writes | This MCP is the only option for **programmatic write access** to your Whoop data right now. --- ## FAQ **Q: Is this supported by Whoop?** A: No. This MCP works through Whoop's private iOS API, which isn't a public surface they intend for third-party tools. Whoop's terms reserve the right to take action against accounts they catch using unsupported integrations β€” realistically that means suspending API access or terminating the membership. The author has used the MCP heavily for weeks without issue, and traffic patterns look similar to normal app usage, but there's no guarantee. If losing your Whoop account would be a problem for you, don't use this. **Q: Why not use Whoop's public OAuth API instead?** A: It's 13 endpoints, all read-only, no journal, no strength, no stress, no coach, no smart alarm, no trends beyond a single recovery score per day. Whoop also pulled numeric `sport_id` past 2025-09-01 (now `sport_name` strings only). If you only need recovery score + sleep stage totals + workout list, the OAuth API is the right answer. **Q: Will this work with the Whoop 4.0 vs 5.0 strap?** A: Yes β€” the API doesn't care which strap you have. It cares about your account. **Q: What about Whoop 6.0?** A: When it launches and the iOS app updates, the api version may bump from 7 to 8. The MCP's `constants.ts` may need an update. Worst case, projections break and you fix them. **Q: Can I run this on a server / cloud / always-on?** A: Sure. The MCP doesn't care where it runs. Just make sure your `.env` survives restarts. **Q: Can I share this MCP with my friends?** A: Each user needs their own `.env` with their own Whoop credentials. Don't share tokens. **Q: Is there an HTTP transport instead of stdio?** A: Yes β€” set `MCP_TRANSPORT=http` to expose the MCP over Streamable HTTP behind a bearer-token + OAuth 2.1 gate (since v1.1.0). See [Remote hosting](#remote-hosting). stdio stays the default for local Claude Desktop / Claude Code. **Q: Does this support Claude's Computer Use API?** A: It's MCP-compatible β€” anything that speaks MCP can talk to it. **Q: Why TypeScript instead of Python?** A: The MCP SDK is most mature in TypeScript. Also Whoop's API responses are heavily nested β€” zod is genuinely the best validation library for that shape work. **Q: Why Node 24 specifically?** A: Uses `import.meta.dirname` (added in 20.11), modern `fetch`, native ESM, `AbortController`. Node 18 might work; 16 won't. **Q: How long did this take?** A: ~3 weeks of evening/weekend work for v1, plus another week to rewrite as v2 with proper projections and the write-safety harness. **Q: Will you maintain this?** A: Best-effort. PRs welcome. --- ## Disclaimers - **Not affiliated with Whoop.** "WHOOP" is a trademark of WHOOP, Inc. Community-built tool that interacts with surfaces Whoop has not published. See the [FAQ](#faq) for the practical implications. - **No warranty, use at your own discretion.** The API surface is reverse-engineered β€” Whoop can change response shapes at any time. The zod schemas surface drift as `WhoopProjectionError` instead of silent corruption. - **Respect rate limits.** Single-digit RPS in normal use. Don't be the person who triggers a backend alert that gets every user of this MCP banned. - **Don't share tokens.** Your `.env` is yours. Don't commit it, don't paste it anywhere. --- ## Acknowledgments - **WHOOP** for building a fitness platform worth reverse-engineering - **Anthropic** for [MCP](https://modelcontextprotocol.io) and [Claude](https://claude.ai) - **mitmproxy** for being the tool that made discovery possible - **The TypeScript + zod community** for making strict validation pleasant - The various API consumers + bloggers who documented bits of Whoop's private API over the years This is open source under the terms in `LICENSE`. Contributions welcome.