
Whoop Mcp
io.github.davidmosiah由 GitHub 账号 davidmosiah 发布v0.5.3更新于 Oct 24, 2026
Privacy-first, unofficial WHOOP MCP server for AI health, sleep, recovery, and performance agents.
概览
非官方本地 MCP 服务器,让 AI 助手通过 WHOOP 官方 OAuth API 读取你的恢复、睡眠、负荷、HRV 和训练数据。
- 可以做什么
- 检查配置与连接状态,列出能力、数据清单、代理清单、隐私审计和缓存状态,并获取 OAuth 链接、交换授权码或撤销授权。无需账号即可生成合成演示数据。生成包含准备度、睡眠、负荷和行动建议的每日与每周摘要。分页列出恢复、睡眠、周期和训练记录,并按 id 获取单条记录。读取个人资料与身体测量数据,并提供每日、每周摘要资源和教练提示词。
- 适用场景
- 适合让助手基于你自己的 WHOOP 数据思考训练、睡眠与恢复,例如生成每日状态简报或每周训练回顾,而不必从应用中手动抄录数字。
- 运行要求
- 通过 npx 在本机运行,需要 Node.js 20 或更高版本。需要一个 WHOOP 开发者应用,重定向地址为 WHOOP_CLIENT_ID、WHOOP_CLIENT_SECRET 和 WHOOP_REDIRECT_URI,或使用交互式 setup 命令。需要恢复、周期、训练、睡眠、资料和身体测量的 OAuth 权限范围。可选 SQLite 缓存与令牌路径设置。
安装
在 SourceWeft 中
- 打开 控制台中的 Whoop Mcp,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
WHOOP MCP
Give your AI agent your WHOOP recovery, sleep, strain and HRV — without copy-pasting from the app.
Local-first MCP server — tokens never leave your machine.
[npm version] [GitHub release] [npm downloads] [License MIT] [Site]
[GitHub stars] [Built for MCP] [Verified release index] [Hermes one-command setup] [WHOOP]
⚡ One-command install with Delx Wellness for Hermes:
npx -y delx-wellness-hermes setup— preconfigures this connector and the full Delx Wellness stack in a dedicated Hermes profile.Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop — see the install section below. Runnable examples live in the Delx Wellness hub.
Public proof: WHOOP MCP is tracked in the Delx Open Source Growth Snapshot alongside downloads, stars and next-action priorities. If it saves you OAuth and MCP setup time, star this repo so other recovery-focused agent builders can find it faster.
First useful prompt:
Use whoop_connection_status, then whoop_daily_summary, then give me a 5-line operating brief for today.
Local-first MCP server that connects AI agents to your WHOOP recovery, sleep, strain and HRV data.
Unofficial project. Not affiliated with, endorsed by or supported by WHOOP, Inc. WHOOP is a trademark of its respective owner. Use this only with your own WHOOP account and in line with WHOOP's Developer Terms.
Built by David Mosiah for people who use Claude, Cursor, Hermes, OpenClaw or other MCP-compatible agents to think about training, sleep and recovery — without copy-pasting numbers from the WHOOP app.
Part of Delx Wellness, a registry of local-first wellness MCP connectors.
Prior work and credits
WHOOP MCP Unofficial builds on prior WHOOP MCP groundwork by
Shashank Mishra, including the
OAuth/WHOOP API direction and the earlier MIT-licensed
whoop-ai-mcp package
(source). This project
extends that foundation with local-first setup, privacy audits, dual transport,
agent manifests, summaries, caching, registry metadata and Delx Wellness hub
integration.
If this connector helps your agent workflow, please star the repo. Stars make the project easier for other AI builders to discover and help Delx keep shipping local-first wellness infrastructure.
[WHOOP MCP local-first agent workflow demo]
Why this exists
WHOOP gives you rich physiology — recovery score, HRV, sleep stages, strain — but it lives behind an OAuth API and a closed app. Bringing it into your AI agent today means writing the OAuth dance yourself, storing tokens safely, normalizing responses and handling pagination.
This package does all of that locally, exposes WHOOP through the Model Context Protocol, and lets any MCP-compatible agent read your WHOOP context with one config snippet. Tokens never leave your machine.
Setup in 60 seconds
You'll need a WHOOP Developer app (create one here) with redirect URI http://127.0.0.1:3000/callback.
Then add this to your MCP client config:
For Claude Desktop, run setup --client claude and the snippet is written for you.
See it before you connect
No WHOOP account yet? Call whoop_demo — it returns realistic synthetic recovery, sleep and strain payloads (tagged is_demo: true) so your agent learns the data contract before any OAuth. Just ask:
Default (markdown) output:
With response_format=json you get the full shape the live tools return:
The records array is trimmed to its first entry here; the live tool returns all
three, each with the same keys. records[].score is the untouched WHOOP object,
not a number — a parser that reads it as a scalar silently gets undefined.
Once you finish OAuth setup below, whoop_daily_summary, whoop_wellness_context and whoop_list_recoveries return this same shape with your live WHOOP data.
Record a real demo safely
After OAuth is connected, generate a privacy-sanitized transcript for README demos, issue updates or agent evals:
demo-capture runs the same readiness path an agent should use:
whoop_connection_status shape first, then whoop_daily_summary, then a short
recovery-aware prompt. It fails closed when setup is incomplete and the
sanitizer blocks OAuth secrets, local token paths, raw payloads, exact recovery
numbers and exact sleep details. The committed
redaction contract is a
fixture-only sample; real captures should be reviewed before publishing.
Try it with your agent
Three things to ask first:
Data availability
This package uses the official WHOOP OAuth API (v2). It does not access raw device sensor streams.
When this README says raw, it means the upstream WHOOP API JSON for a supported endpoint — not raw sensor samples.
Tools
Start with these:
whoop_demo— realistic synthetic recovery/sleep/strain payloads, no OAuth needed (see See it before you connect)whoop_connection_status— verify local setup before calling WHOOPwhoop_data_inventory— inventory supported data domains, scopes, privacy modes and recommended first calls without calling WHOOP APIs.whoop_daily_summary— readiness, sleep, load and action candidates for todaywhoop_weekly_summary— scorecard, comparison vs prior week, next-week plan
Auth & diagnostics
whoop_capabilities,whoop_agent_manifest,whoop_privacy_audit,whoop_cache_statuswhoop_get_auth_url,whoop_exchange_code,whoop_revoke_access
Profile
whoop_get_profile,whoop_get_body_measurements
Collections (paginated, with start/end filters and privacy-mode override)
whoop_list_recoveries,whoop_list_sleeps,whoop_list_cycles,whoop_list_workouts
Common collection params: start, end, limit (max 25), next_token, all_pages, max_pages, response_format (markdown/json), privacy_mode (summary/structured/raw).
start and end remain exact timezone-aware ISO date-times at the WHOOP boundary. Invalid or reversed ranges fail before a network request.
Single records by id
whoop_get_cycle,whoop_get_sleep,whoop_get_workoutwhoop_get_cycle_sleep,whoop_get_cycle_recovery
Prompts
whoop_daily_performance_coach— practical daily plan from today's signalswhoop_weekly_training_review— week comparison + next-week planwhoop_sleep_recovery_investigator— investigate sleep ↔ recovery patterns
Each accepts timezone (IANA, default UTC).
Resources
whoop://capabilitieswhoop://summary/daily,whoop://summary/weeklywhoop://latest/recovery,whoop://latest/sleep,whoop://latest/cycle
Privacy & security
- OAuth tokens are stored in
~/.whoop-mcp/tokens.jsonwith0600permissions and are never returned by tools. - Refresh-token rotation uses a lock file to avoid concurrent refresh races.
whoop_revoke_accessis the only destructive tool — it deletes local tokens and revokes the grant.WHOOP_PRIVACY_MODEdefaults tostructured. Raw WHOOP API payloads are opt-in viarawmode or per-call override.- Structured mode preserves complete nested physiological data and future upstream fields while removing GPS and secret-bearing values.
demo-captureredacts demo transcripts before writing anything intended for docs or issues.- The MCP client never sees access or refresh tokens.
- This is not medical advice. The server exposes user-authorized data for personal AI workflows, not diagnosis or treatment.
Configuration
setup writes most of these into ~/.whoop-mcp/config.json (0600). Manual env override is supported:
Hermes / remote setup
After Hermes config changes, use /reload-mcp or hermes mcp test whoop. Don't restart the gateway for normal data access.
If browser OAuth has to happen on a different machine than Hermes, run auth locally and copy ~/.whoop-mcp/tokens.json to the server with chmod 600.
Requirements
- Node.js 20+
- A WHOOP Developer app with redirect URI
http://127.0.0.1:3000/callback
Default OAuth scopes:
Development
Test with MCP Inspector:
HTTP (v2 stateless)
Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:
Env: WHOOP_MCP_HOST, WHOOP_MCP_PORT, WHOOP_MCP_TRANSPORT=http.
Docs
Links
- npm: https://www.npmjs.com/package/whoop-mcp-unofficial
- Docs site: https://wellness.delx.ai/connectors/whoop
- Legacy docs: https://whoopmcp.vercel.app/
- GitHub Pages mirror: https://davidmosiah.github.io/whoop-mcp/
- Delx Wellness registry: https://github.com/davidmosiah/delx-wellness
- Connector quality standard: https://github.com/davidmosiah/delx-wellness/blob/main/docs/connector-quality-standard.md
- Official WHOOP API docs: https://developer.whoop.com/api/
See also
The full Delx Wellness connector library:
One-command setup for Hermes — preconfigures every connector above plus wellness skills + onboarding: delx-wellness-hermes.
📧 Contact & Support
- 📨 [email protected] — general questions, integration help, partnerships
- 🐛 Bug reports / feature requests — GitHub Issues
- 🐦 Updates — @delx369 on X
- 🌐 Site — wellness.delx.ai
License
MIT — see LICENSE. Code of Conduct.
Disclaimer
This software is provided as-is. It is not a medical device, does not provide medical advice, and should not be used for diagnosis or treatment. Always consult qualified professionals for medical concerns.
Demo: docs/readme-demo-synthetic.md (synthetic if no device recording).
Raw mode means official WHOOP API JSON, not continuous sensor streams.
Skill or MCP
Same package, two doors. MCP registers tools on stdio/HTTP. The skill can drive the same tools through the CLI when the client has no MCP:
Copy skill/SKILL.md into your agent skills dir.
Release migration
Before upgrading to 0.7.0, review the compatibility and migration notes.
来源:README.md,提交 6968e61
工具
0版本历史
1- v0.5.3最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分