ToolyHealthToolyHealth
Back to Open Source Reviews
Totem
Wearables / Developer Tool / MCPTypeScriptMIT

Totem Review

A TypeScript MCP server that gives Claude and other MCP clients read/write access to Whoop wearable data.

Deployability
3/5
Value
3/5
Privacy
2/5
View source

Each review covers deployability, value versus commercial alternatives, and privacy model. Tools that can run locally were started and exercised; mobile or backend-dependent tools were assessed from published builds, source code, and deploy guides. Ratings reflect what we were able to verify.

Totem — MCP Server for Wearable Data

A TypeScript Model Context Protocol (MCP) server that gives Claude and other MCP clients read/write access to Whoop wearable data through a reverse-engineered iOS API adapter. Last updated: 2026-06-21.

One-sentence verdict: A powerful developer tool for bridging Whoop data into AI clients — not a consumer app, and its use of Whoop's private API carries clear terms-of-service risk.

What the System Is

Totem is an MCP server for wearable data. The repository shows:

  • TypeScript 6 / Node.js 24+ MCP server using the official @modelcontextprotocol/sdk.
  • Transport: stdio (default) or HTTP.
  • Whoop adapter: 48 tools, 47 microservices, 311 endpoints covering recovery, sleep, strain, HRV, Strength Trainer, journal, Whoop Coach, and smart alarm.
  • Auto-refreshing Cognito auth and bearer-token/OAuth security gates.
  • Write-safety harness to protect destructive operations.
  • Bundled catalogs: 372 exercises, 308 behaviors, 203 sports.
  • Extensible architecture: Fitbit, Apple Watch, and Garmin adapters are listed as in progress.

The deploy guide states the CLI compiled successfully and the help screen was displayed; full Whoop functionality requires a Whoop account and authorization.

Key data
Category Wearables / Developer Tool / MCP
Language TypeScript
License MIT
Self-hosted Yes (CLI, Docker, Fly, Railway, Hugging Face Spaces)
AI Exposes wearable data to MCP clients (Claude, ChatGPT, Cursor, etc.)
Database None persistent by default
Deployment npm-linked CLI or cloud host

How to Install and Deploy

cd /data2/docker/going-global/repos/totem
npm install
npx tsc
npm link

After linking, the totem CLI is available on PATH:

totem --help
totem auth        # Whoop login and authorization
totem start       # local stdio MCP service
totem start --http
totem dev
totem test

Copy .env.example to .env and fill in Whoop / AWS Cognito credentials for full functionality.

How to Test

The documented test flow is:

  1. Run totem --help and verify the CLI responds.
  2. Run totem auth to complete Whoop login via SMS/Cognito.
  3. Start the MCP server with totem start (stdio) or totem start --http.
  4. Connect the server to an MCP client such as Claude Code, Claude Desktop, or Cursor.
  5. Query Whoop metrics through natural language and verify structured zod-validated responses.
  6. Test write operations carefully; the write-safety harness should prompt for confirmation.

Because full Whoop authorization was not configured, only the CLI help screen was verified in the current environment.

Privacy & Compliance

Totem is a developer tool, not a consumer health app, and is not HIPAA compliant. Data flows through Whoop's private iOS API and your chosen MCP client. The README explicitly notes this use is contrary to Whoop's Terms of Use (reverse engineering and data extraction prohibitions). It is not illegal, but it may result in account action by Whoop. Do not use it for PHI or in regulated environments.

Totem vs Commercial Wearable Integrations

Dimension Totem Official Whoop Integration / Wellness Platform
Cost Free / open source Subscription or paid platform
Open source Yes (MIT) No
Data access depth Private iOS API surface (311 endpoints) Public OAuth API only
AI client support Any MCP 1.x client Limited or none
Setup effort High: CLI, Whoop auth, MCP client config Low: connect account
Terms-of-service risk Yes — uses private API No
Write support Yes, with safety harness Read-only or limited

Who Should Use It

  • Developers and power users who want deep Whoop data inside Claude or other MCP clients.
  • Researchers building wearable-data workflows who accept the terms-of-service risk.
  • Contributors interested in adding Fitbit, Apple Watch, or Garmin adapters.

Who Shouldn't Use It

  • Casual users who want a simple dashboard.
  • Anyone unwilling to accept Whoop's terms-of-service risk.
  • Regulated environments or anyone handling PHI.

FAQ

Is Totem officially supported by Whoop?

No. Totem uses Whoop's private iOS API, not the official public API. The README states this is contrary to Whoop's Terms of Use.

Can Totem write data back to Whoop?

Yes. The Whoop adapter includes write operations, gated by a write-safety harness to prevent accidental changes.

Which MCP clients work with Totem?

Any MCP 1.x client, including Claude Code, Claude Desktop, ChatGPT Desktop, Codex, Gemini CLI, and Cursor.

Verdict

Totem is a powerful, well-documented MCP bridge for wearable data. It gives AI clients deep, structured access to Whoop metrics with a strong write-safety harness. The clear downside is its reliance on Whoop's private API, which violates Whoop's Terms of Use. It is best suited to developers and power users who understand and accept that risk.

Ratings: Deployability 3/5 · Value vs Commercial 3/5 · Privacy Compliance 2/5