Whoop Mcp
Pull WHOOP sleep, recovery, strain, and performance data into a privacy-first local MCP server for health and coaching agents.
Overview
WHOOP MCP is an MCP server for the Build phase that provides local, privacy-first WHOOP OAuth and health, sleep, recovery, and performance data tools for AI agents.
What is this MCP server?
- Unofficial, privacy-first WHOOP MCP (npm whoop-mcp-unofficial v0.4.5) over stdio
- OAuth via WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET, and WHOOP_REDIRECT_URI with optional whoop-mcp-server setup
- Tokens default to ~/.whoop-mcp/tokens.json with configurable WHOOP_TOKEN_PATH
- WHOOP_PRIVACY_MODE and local config in ~/.whoop-mcp/config.json to keep secrets out of MCP client JSON
- Targets AI agents focused on health, sleep, recovery, and performance coaching
- Server version 0.4.5 with npm identifier whoop-mcp-unofficial
- Default OAuth token path ~/.whoop-mcp/tokens.json unless WHOOP_TOKEN_PATH is set
- Optional WHOOP_PRIVACY_MODE and four documented WHOOP OAuth environment variables
Community signal: 4 GitHub stars.
What problem does it solve?
Agents that should use WHOOP metrics get stuck on OAuth, token storage, and unofficial API plumbing without a dedicated MCP bridge.
Who is it for?
Solo builders crafting recovery or training agents who accept an unofficial WHOOP integration and want secrets kept off the MCP client config.
Skip if: Enterprise wellness programs needing WHOOP partnership compliance, or users who will not run local OAuth setup.
What do I get? / Deliverables
After setup with whoop-mcp-server and stdio registration, your agent can call WHOOP-oriented MCP tools using tokens stored locally under ~/.whoop-mcp.
- MCP tools backed by WHOOP health, sleep, recovery, and performance data
- Local OAuth token file (default ~/.whoop-mcp/tokens.json)
- Agent-ready wearable context without embedding secrets in MCP client config
Recommended MCP Servers
Journey fit
How it compares
Unofficial WHOOP OAuth MCP server, not WHOOP’s official app SDK or a generic fitness CSV skill.
Common Questions / FAQ
Who is WHOOP MCP for?
Developers building local AI agents for sleep, recovery, and performance who wear WHOOP and want MCP tools with privacy-oriented token storage.
When should I use WHOOP MCP?
Use it in build integrations when your agent product needs live WHOOP data and you can complete OAuth via the WHOOP Developer Dashboard and whoop-mcp-server setup.
How do I add WHOOP MCP to my agent?
Install the npm package (identifier whoop-mcp-unofficial), prefer whoop-mcp-server setup for ~/.whoop-mcp/config.json, register stdio MCP in your agent, and set redirect URI and token path env vars as documented.