Totem

Name: Totem
Author: briangaoo

作者：briangaoo版本 1.4.3i★ –i在你的电脑上运行

注册名称io.github.briangaoo/totem

安装

概览

作者提供的说明（英文原文）

Totem — talk to your wearables with AI. Today: full Whoop access (48 tools).

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：WHOOP_IOS_BEARER_TOKEN, WHOOP_COGNITO_REFRESH_TOKEN, WHOOP_EMAIL

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： WHOOP_IOS_BEARER_TOKEN, WHOOP_COGNITO_REFRESH_TOKEN, WHOOP_EMAIL, WHOOP_USER_ID, WHOOP_TIMEZONE

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "totem": {
      "command": "npx",
      "args": [
        "-y",
        "@briangaoo/totem"
      ],
      "env": {
        "WHOOP_IOS_BEARER_TOKEN": "your-value",
        "WHOOP_COGNITO_REFRESH_TOKEN": "your-value",
        "WHOOP_EMAIL": "your-value",
        "WHOOP_USER_ID": "your-value",
        "WHOOP_TIMEZONE": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add totem --env WHOOP_IOS_BEARER_TOKEN=your-value --env WHOOP_COGNITO_REFRESH_TOKEN=your-value --env WHOOP_EMAIL=your-value --env WHOOP_USER_ID=your-value --env WHOOP_TIMEZONE=your-value -- npx -y @briangaoo/totem

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "totem": {
      "command": "npx",
      "args": [
        "-y",
        "@briangaoo/totem"
      ],
      "env": {
        "WHOOP_IOS_BEARER_TOKEN": "your-value",
        "WHOOP_COGNITO_REFRESH_TOKEN": "your-value",
        "WHOOP_EMAIL": "your-value",
        "WHOOP_USER_ID": "your-value",
        "WHOOP_TIMEZONE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "totem": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@briangaoo/totem"
      ],
      "env": {
        "WHOOP_IOS_BEARER_TOKEN": "your-value",
        "WHOOP_COGNITO_REFRESH_TOKEN": "your-value",
        "WHOOP_EMAIL": "your-value",
        "WHOOP_USER_ID": "your-value",
        "WHOOP_TIMEZONE": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

WHOOP_IOS_BEARER_TOKEN 机密必填 env
Whoop Cognito access token. Obtain via `totem auth` from the repo, which prompts for your Whoop email + password + SMS MFA code, then writes both tokens to a local .env. Auto-refreshes every ~24h.
WHOOP_COGNITO_REFRESH_TOKEN 机密必填 env
Whoop Cognito refresh token (~30 day lifetime). Obtained alongside the bearer token from `totem auth`. When this expires, run `totem auth` to get a fresh pair.
WHOOP_EMAIL 必填 env
Your Whoop account email. Used only by `totem auth` — the running server reads tokens, not credentials.
WHOOP_USER_ID env
Your numeric Whoop user ID. Optional — used by whoop_profile and whoop_leaderboard. Avoids one redundant bootstrap call per session if set.
WHOOP_TIMEZONE env
IANA timezone (e.g., America/Los_Angeles) for response timestamps. Optional — if unset, the server auto-detects from your Whoop profile's timezone_offset field (refreshed hourly).

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 briangaoo 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18584 个服务器的 0%
发布到注册中心的时间比此分类中其他 18584 个服务器的 10% 更新
基础检查结果等于或优于此分类中其他 18584 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Totem 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：WHOOP_IOS_BEARER_TOKEN, WHOOP_COGNITO_REFRESH_TOKEN, WHOOP_EMAIL

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.4.3）于5个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, aamio rendezvous

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者：formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

安装

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者：desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

安装

aamio rendezvous

Meet an agent you have not met, exchange messages that expire, and prove it happened. No account.

作者：aamio.at起步阶段今天更新

在云端运行✓ aamio.at

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.

▶ 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). 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 if you want the full picture before installing.*

Get Started
Why this exists
What it does
Architecture
The 55 tools
Authentication
Write-safety harness
Bundled catalogs
Configuration
Remote hosting

Deploying to Hugging Face Spaces (free hosting)

The totem CLI
Privacy + security
Troubleshooting
Comparison to alternatives
FAQ
Disclaimers
Acknowledgments

Other root-level docs: TOOLS.md (full per-tool reference) · WHOOP.md (full API reference) · CHANGELOG.md · CONTRIBUTING.md · SECURITY.md · LICENSE

Get Started

Prerequisites: Node 24+ and a Whoop account (any membership tier).

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:

Whoop login — email + password, plus the SMS code if your account has MFA. Tokens are saved locally and pushed to the host.
Pick a host — Fly (automated + tested), Railway, Google Cloud Run, or your own server (guided Docker steps).
Secrets — generates MCP_AUTH_TOKEN and asks you to choose a connector password.
Deploy + verify — sets env, deploys, confirms /health and the OAuth endpoints are live.
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.

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.

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:

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, Remote hosting, and Configuration. Stuck? See Troubleshooting.

Why this exists

Whoop ships two APIs:

The public developer API at developer.whoop.com 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.

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:

Authenticates via the cached Cognito access token (auto-refreshes if expired)
Issues HTTP requests to api.prod.whoop.com
Walks the response to extract a flat domain object (the projection step)
Validates the projected object against a zod schema (catches Whoop API drift)
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 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`](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

只显示了开头部分；其余内容请在仓库中阅读