Whoop Mcp Unofficial
@davidmosiah
Unofficial local-first MCP server for WHOOP — recovery, strain, sleep stages, HRV, RHR and workouts. Privacy modes (summary/structured/raw), SQLite cache and doctor CLI for setup. Works with Claude Desktop, Cursor, Windsurf, Hermes, OpenClaw and any MCP-compatible client. Install
Overview
What is Whoop Mcp Unofficial?
A local-first MCP server that connects AI agents to your WHOOP recovery, sleep, strain, and HRV data. It is an unofficial project not affiliated with WHOOP, Inc., built for users of Claude, Cursor, Hermes, and other MCP-compatible agents.
How to use Whoop Mcp Unofficial?
Install and configure using npx -y whoop-mcp-unofficial setup (paste WHOOP developer credentials), then npx -y whoop-mcp-unofficial auth (opens browser for OAuth), and npx -y whoop-mcp-unofficial doctor to verify. Add a JSON config snippet to your MCP client. The whoop_connection_status tool checks setup; then ask your agent to call tools like whoop_daily_summary.
Key features of Whoop Mcp Unofficial
- OAuth tokens stored locally with 0600 permissions
- Privacy modes: summary, structured, or raw (opt-in)
- Tools for recovery, sleep, cycles, workouts, and profile
- Built-in prompts: daily performance coach, weekly review, sleep investigator
- Resources expose capability and summary endpoints
- Paginated collection tools with filters and privacy override
Use cases of Whoop Mcp Unofficial
- Ask your AI agent for a daily operating brief based on recovery and sleep
- Generate a weekly training and sleep plan from scorecard data
- Investigate how sleep patterns affect recovery scores over time
FAQ from Whoop Mcp Unofficial
What data is available?
Recovery score, HRV, RHR, SpO2, skin temp, sleep sessions with stages, cycle strain, kilojoules, workouts with heart-rate zones, profile, and body measurements. Continuous HR or BLE listening is not supported.
What are the runtime requirements?
Node.js 20+ and a WHOOP Developer app with redirect URI http://127.0.0.1:3000/callback.
How are tokens stored?
OAuth tokens are stored in ~/.whoop-mcp/tokens.json with file permissions 0600. They are never returned by tools, and the MCP client never sees the tokens.
Can I access raw WHOOP API payloads?
Yes, by setting WHOOP_PRIVACY_MODE=raw or by passing privacy_mode: raw per tool call. The default is structured.
Is this medical advice?
No. The server exposes user-authorized data for personal AI workflows, not for diagnosis or treatment. It is provided as-is and is not a medical device.
