Whoop Mcp Server

io.github.Zayden16Published by GitHub account Zayden16v1.1.0Updated Oct 24, 2026

MCP server for the official Whoop API v2: cycles, recovery, sleep, workouts, and profile data

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Local MCP server that connects to the official Whoop API v2 so an assistant can read your cycles, recovery, sleep, workout and profile data.

What you can do
  • Read profile and body measurements (name, email, height, weight, max heart rate)
  • Fetch daily cycles with strain, kilojoules and heart rates, including the latest cycle
  • Fetch recovery records with recovery score, resting heart rate, HRV, SpO2 and skin temperature
  • Fetch sleep records with stage durations, respiratory rate and sleep performance
  • Fetch workouts with sport, strain, heart rates, distance and time-in-zone
  • Compute an average strain over a chosen number of days and check authorization status
When to use it
Useful when you want an assistant to answer questions about your own Whoop data, such as today's recovery score, last week's sleep, or average strain over recent days, without exporting data by hand.
Requirements
Runs as a local binary (Homebrew, prebuilt release, go install, or built from source). Needs a Whoop developer app with the listed read scopes and the redirect URI on localhost, plus WHOOP_CLIENT_ID and WHOOP_CLIENT_SECRET environment variables. A one-time browser OAuth authorization stores a token locally, which is refreshed automatically. Network access to the Whoop API is required.
Before you install
Requires your Whoop client ID and client secret, which are passed as environment variables to the MCP client configuration. A token file is stored on disk and refreshed automatically. The server reads personal health data (email, body measurements, sleep, recovery, workouts) and sends it to the model; all tools are read-only. The OAuth flow opens a browser and listens on a local callback port.

Installation

In SourceWeft

  1. Open Whoop Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

whoop-mcp-server

[CI] [Release] [Go Version] [License: MIT]

MCP server for the official Whoop API v2, written in Go. Exposes cycles, recovery, sleep, workouts, and profile data as MCP tools.

Tools

All tools return JSON. Record shapes are the unmodified Whoop API v2 objects, so every field the API exposes is available to the model.

ToolInputsReturns
get_profile—Single object: user_id, email, first_name, last_name
get_body_measurement—Single object: height_meter, weight_kilogram, max_heart_rate
get_cyclesstart_date, end_date, limit (all optional)Array of cycle records — one per physiological day: start/end, score_state, and score with day strain, kilojoule, average_heart_rate, max_heart_rate
get_latest_cycle—Single cycle record (the current/most recent day)
get_recoveriesstart_date, end_date, limit (all optional)Array of recovery records — one per sleep: cycle_id, sleep_id, and score with recovery_score (0–100), resting_heart_rate, hrv_rmssd_milli, spo2_percentage, skin_temp_celsius
get_recovery_for_cyclecycle_id (required)Single recovery record for that cycle
get_sleepstart_date, end_date, limit (all optional)Array of sleep records: start/end, nap flag, and score with per-stage durations (light/SWS/REM/awake, in ms), respiratory_rate, sleep_performance_percentage, sleep_efficiency_percentage, sleep-need breakdown
get_workoutsstart_date, end_date, limit (all optional)Array of workout records: sport_name, start/end, and score with workout strain, heart rates, kilojoule, distance_meter, altitude_gain_meter, time-in-zone durations (zone_durations, ms per HR zone)
get_average_straindays (optional, default 7)Computed aggregate: {days, cycles_counted, average_strain}
check_auth_status—{authenticated: bool} plus the profile on success or an error string on failure

Notes:

  • Dates are YYYY-MM-DD; end_date is inclusive (internally mapped to the start of the next day, per the API's exclusive end semantics).
  • Collections are date-descending (most recent first) and paginated transparently — the server follows next_token until limit records (default 25, max 100) are collected.
  • Scores are point-in-time per record, not time-series: one strain value per cycle, one recovery per sleep. For trends, fetch a range and let the model aggregate (or use get_average_strain for the built-in strain average).
  • A record's score_state can be SCORED, PENDING_SCORE, or UNSCORABLE — score is only present when SCORED.

Setup

1. Create a Whoop developer app

At developer.whoop.com, create an app with:

  • Redirect URI: http://localhost:8719/callback
  • Scopes: read:cycles, read:recovery, read:sleep, read:workout, read:profile, read:body_measurement, offline

Note the client ID and client secret.

2. Install

Homebrew:

sh
brew install zayden16/tap/whoop-mcp-server

Or download a prebuilt binary from Releases, or:

sh
go install github.com/Zayden16/whoop-mcp-server@latest

Or build from source:

sh
go build -o whoop-mcp-server .

3. Authorize (one time)

sh
export WHOOP_CLIENT_ID=...export WHOOP_CLIENT_SECRET=..../whoop-mcp-server auth

Opens a browser for the OAuth flow; the token is saved to ~/Library/Application Support/whoop-mcp/token.json (macOS) and refreshed automatically thereafter (rotating refresh tokens).

4. Register with Claude Code

sh
claude mcp add whoop --scope user \  -e WHOOP_CLIENT_ID=... \  -e WHOOP_CLIENT_SECRET=... \  -- /path/to/whoop-mcp-server

Or for Claude Desktop, in claude_desktop_config.json:

json
{  "mcpServers": {    "whoop": {      "command": "/path/to/whoop-mcp-server",      "env": {        "WHOOP_CLIENT_ID": "...",        "WHOOP_CLIENT_SECRET": "..."      }    }  }}

Example queries

  • "What's my recovery score today?"
  • "Show my sleep for the past week"
  • "What's my average strain over the last 7 days?"

Source: README.md at commit a25ce1a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts