Whoop Mcp Unofficial
@davidmosiah
About Whoop Mcp Unofficial
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
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"whoop": {
"command": "npx",
"args": [
"-y",
"whoop-mcp-unofficial"
]
}
}
}Tools
30Inventory supported WHOOP data domains, auth scope requirements, privacy boundary and recommended first calls. Does not call WHOOP APIs or expose user data.
Explain supported WHOOP data, unavailable raw sensor streams, privacy modes, recommended agent workflow, and project links. Does not read WHOOP or expose secrets.
Machine-readable install, runtime and client guidance for AI agents operating the WHOOP MCP. Does not read WHOOP or expose secrets.
Personalized 3-step setup walkthrough for the human user. Adapts to current state (env vars set? token present? what's next?). Call this first when the user asks 'how do I connect WHOOP?'
Returns realistic example payloads of whoop_daily_summary, whoop_wellness_context, and whoop_list_recoveries so agents see the contract before calling real WHOOP APIs. Shapes are verified against the real tools by a build gate, so a parser written against this demo works on live data.
Read the shared Delx wellness profile (~/.delx-wellness/profile.json). Returns the user's preferred name, body basics, goals, devices, training context, nutrition context, agent preferences, and missing critical fields. Cross-connector — the same profile is also available from other Delx Wellness MCPs (Oura, Garmin, Nourish, Fitbit, etc). Read-only.
Persist a partial patch to the shared Delx wellness profile (~/.delx-wellness/profile.json). REQUIRES explicit_user_intent=true. Top-level fields stored: profile (preferred_name, language, timezone, units, age_or_birth_year, height, weight, sex_or_gender_context), goals, devices, training, nutrition, preferences, safety, notes. NEVER stores OAuth tokens, API keys, refresh tokens, cookies, or any secret-shaped field — writes will be rejected at validation time. Cross-connector — the same profile is read by other Delx Wellness MCPs.
Return the 11-question Delx wellness onboarding flow (in English or pt-BR) plus the current shared profile state and missing critical fields. Read-only. The agent should ask these questions one-by-one, then call whoop_profile_update with explicit_user_intent=true to save. The same profile is reused by every Delx Wellness connector (Oura, Garmin, Nourish, etc.) — agents can call the equivalent {connector}_onboarding tools to cover their respective domains, or rely on this one since all connectors share the same questions.
Generate a WHOOP OAuth authorization URL. This does not read or modify WHOOP data. Use this first when no local token exists.
Exchange a WHOOP OAuth authorization code for local tokens. Tokens are stored locally with 0600 permissions and are never returned by this tool. Gated: requires explicit user intent — agents must not call this autonomously.
Get the authenticated user's basic WHOOP profile. Requires read:profile scope.
Get the authenticated user's WHOOP body measurements (height, weight, max heart rate). Requires read:body_measurement scope. Not medical advice.
List WHOOP physiological cycles. Supports start/end filters and WHOOP pagination. Requires read:cycles scope.
List WHOOP recoveries sorted by related sleep start time descending. Returns recovery score, HRV, RHR, SpO2 and skin temperature when scored. Requires read:recovery scope. Not medical advice.
List WHOOP sleep activities. Returns sleep stages, performance, consistency and efficiency when scored. Supports start/end filters and WHOOP pagination. Requires read:sleep scope. Not medical advice.
List WHOOP workouts. Supports start/end filters and WHOOP pagination. Requires read:workout scope.
Check whether local WHOOP env vars, token file, Node version, privacy mode and cache are ready. Does not call WHOOP or expose secrets.
Show optional local SQLite cache status. Enable with WHOOP_CACHE=sqlite or WHOOP_CACHE=true.
Return the local privacy, cache, token-path, env-presence and redaction posture without revealing secret values.
Revoke the current WHOOP OAuth access grant and delete the local token file. Use only when the user explicitly wants to disconnect WHOOP. Gated: requires explicit user intent — agents must not call this autonomously.
Build a privacy-conscious daily performance summary from WHOOP recovery, sleep, cycle and workout data. This workflow tool fetches recent WHOOP v2 records, computes a defensive baseline, and returns readiness, sleep, load, diagnostic signals and concrete action candidates. It does not provide medical advice and does not store data locally.
Build a weekly WHOOP operating review with recovery, sleep, strain, workouts, bottlenecks, action candidates and next-week success metrics. This workflow tool compares a recent window against a prior window when available. It is intended for coaching and agent workflows, not medical diagnosis.
Aggregate WHOOP recovery over the last N days (default 30) into a per-metric trend for recovery score, HRV (hrv_rmssd_milli) and resting heart rate. Each metric returns { avg, min, max, slope, direction, n_valid } where slope is a least-squares fit over the chronologically ordered scored records (oldest to newest) and direction is rising, falling, stable or insufficient_data. Use this to answer "is my recovery trending up or down?" without paging the raw collection yourself. Read-only; fetches recent WHOOP v2 records, computes statistics, stores nothing. Not medical advice.
Aggregate WHOOP sleep over the last N days (default 30) into a per-metric trend for sleep performance percentage, sleep duration (hours) and sleep efficiency percentage. Each metric returns { avg, min, max, slope, direction, n_valid } where slope is a least-squares fit over the chronologically ordered scored sleeps (oldest to newest) and direction is rising, falling, stable or insufficient_data. Use this to answer "is my sleep improving or degrading?" without paging the raw collection yourself. Read-only; fetches recent WHOOP v2 records, computes statistics, stores nothing. Not medical advice.
Normalize WHOOP recovery, sleep, strain and recent workout load into the shared wellness_context shape for exercise recommendation engines and Telegram agents.
Get one WHOOP cycle by numeric cycle id. Requires read:cycles scope.
Get one WHOOP sleep activity by UUID. Requires read:sleep scope. Not medical advice.
Get one WHOOP workout by UUID. Requires read:workout scope.
Get the sleep associated with a WHOOP cycle. Requires read:sleep scope. Not medical advice.
Get the recovery associated with a WHOOP cycle. Requires read:recovery scope. Not medical advice.
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.
Frequently asked questions
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.
Basic information
More Developer Tools MCP servers

discoverGPT
Joe MonastierodiscoverGPT is visualAI's unified MCP gateway for AI commerce, exposing 29 tools across four capabilities on one canonical product catalog: trimodal search (natural-language, precise-color, and image-similarity), AI cata
Vibgrate MCP
VibgrateQuery your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

SSH MCP Server
hypnosisSSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.

Routebase
RoutebaseRoutebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.

Meticulous
MeticulousMCP server and skills to connect to the Meticulous UI testing platform.
Comments