All connectors
WHOOP logo

whoop-mcp-unofficial

WHOOP MCP server for AI agents

The WHOOP MCP server uses the official WHOOP OAuth API v2 so agents can work with recovery, sleep, strain and workout context without handing OAuth tokens to the model.

RecoveryHRVSleepStrainWorkoutsShared profile
Athletes stretching in a calm recovery space while reviewing wearable recovery context
OAuth 2.0

Best for recovery-led athletes, coaches and personal agents that need a WHOOP MCP connector for daily readiness, sleep and load briefings before training.

MCP server answers

The WHOOP MCP connector for AI agents is a local-first server provided by whoop-mcp-unofficial. It uses the official WHOOP OAuth API v2 and user-authorized scopes to expose scored recovery, HRV, resting heart rate, sleep, cycles, strain and workout context to an MCP-compatible client. OAuth tokens stay on the user's machine or server; the connector does not provide live BLE or continuous sensor telemetry, and Delx does not host a copy of the data.

Compare this connector with the other wellness pathsSet up WHOOP OAuth, recovery, sleep and rate-safe agent calls
What is the WHOOP MCP server?

The WHOOP MCP connector for AI agents is a local-first server provided by whoop-mcp-unofficial. It uses the official WHOOP OAuth API v2 and user-authorized scopes to expose scored recovery, HRV, resting heart rate, sleep, cycles, strain and workout context to an MCP-compatible client. OAuth tokens stay on the user's machine or server; the connector does not provide live BLE or continuous sensor telemetry, and Delx does not host a copy of the data.

How do I install WHOOP MCP?

Run npx -y whoop-mcp-unofficial setup, then npx -y whoop-mcp-unofficial doctor. The Quick Start section below contains the client configuration and provider-specific setup.

What can an agent read from WHOOP?

The available records start with Recovery score, HRV, RHR, SpO2, skin temperature, Sleep sessions, stages and performance, Cycles, day strain and kilojoules, Workouts, sport and heart-rate zones. Check Data Availability for scope, device and export limitations before using any result.

Quick Start

terminal
npx -y whoop-mcp-unofficial setup
npx -y whoop-mcp-unofficial doctor
mcp-client.json
{
  "mcpServers": {
    "whoop": {
      "command": "npx",
      "args": ["-y", "whoop-mcp-unofficial"]
    }
  }
}
  1. 01

    Create a WHOOP Developer app.

  2. 02

    Use redirect URI http://127.0.0.1:3000/callback.

  3. 03

    Run setup, auth and doctor before connecting an agent.

Data Availability

Available

Recovery score, HRV, RHR, SpO2, skin temperature

Available when WHOOP returns a scored recovery.

Available

Sleep sessions, stages and performance

All scored sleep records.

Available

Cycles, day strain and kilojoules

Physiological cycle records.

Available

Workouts, sport and heart-rate zones

All recorded workouts exposed by the public API.

Available

Profile and body measurements

Height, weight and max heart rate.

Not exposed

Continuous heart-rate or live BLE telemetry

Not exposed by the public WHOOP API; this connector is not a Bluetooth listener.

Agent Tools

Profile and onboarding

  • whoop_profile_get
  • whoop_profile_update
  • whoop_onboarding

Start here

  • whoop_connection_status
  • whoop_daily_summary
  • whoop_weekly_summary

Auth and diagnostics

  • whoop_capabilities
  • whoop_agent_manifest
  • whoop_privacy_audit
  • whoop_cache_status
  • whoop_get_auth_url
  • whoop_exchange_code
  • whoop_revoke_access

Profile

  • whoop_get_profile
  • whoop_get_body_measurements

Collections

  • whoop_list_recoveries
  • whoop_list_sleeps
  • whoop_list_cycles
  • whoop_list_workouts

Single records

  • whoop_get_cycle
  • whoop_get_sleep
  • whoop_get_workout
  • whoop_get_cycle_sleep
  • whoop_get_cycle_recovery

Prompts and Resources

Prompts

  • whoop_daily_performance_coach
  • whoop_weekly_training_review
  • whoop_sleep_recovery_investigator

Resources

  • whoop://capabilities
  • whoop://summary/daily
  • whoop://summary/weekly
  • whoop://latest/recovery
  • whoop://latest/sleep
  • whoop://latest/cycle

Privacy Model

Read-only by default.
OAuth secrets and refresh tokens stay on the user's machine or server.
Collection tools support summary, structured and raw response formats.
The connector distinguishes upstream raw JSON from raw sensor telemetry.
Profile and goals persist locally to ~/.delx-wellness/profile.json (mode 0600); shared with all 14 Delx Wellness connectors and never uploaded.