davidmosiah/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 .
> ⚡ **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.
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: