WHOOP MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

WHOOP MCP by usefulapi is answering right now. Last checked 7 min ago. It exposes 10 tools. Last commit 12 Oct 2026.

Read WHOOP recovery, sleep, cycles, workouts and body measurements.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

82 ms

Response time

average over 24h

Stars

last commit 12 Oct 2026

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

7 Oct a tool changed version

1 Oct a tool changed version

30 Sep a tool changed version

and 3 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check WHOOP MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add whoop --transport http https://whoop.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "whoop": {
      "url": "https://whoop.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.whoop]
url = "https://whoop.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "whoop": {
      "url": "https://whoop.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "whoop": {
      "url": "https://whoop.usefulapi.io/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

whoop

whoop_body_measurement

The user's body measurements (height in meters, weight in kilograms, max heart rate). WHOOP REST: GET /v2/user/measurement/body. Scope: read:body_measurement.

whoop_get_cycle

Get a single physiological cycle by its id (strain, kilojoules, average/max heart rate, start/end). WHOOP REST: GET /v2/cycle/{cycleId}. Scope: read:cycles.

whoop_get_cycle_recovery

Get the recovery scored for a specific cycle (recovery %, resting heart rate, HRV RMSSD, SpO2 %, skin temperature). WHOOP REST: GET /v2/cycle/{cycleId}/recovery. Scope: read:recovery.

whoop_get_profile

The current user's basic WHOOP profile (user id, email, first name, last name). WHOOP REST: GET /v2/user/profile/basic. Scope: read:profile.

whoop_get_sleep

Get a single sleep activity by its id (stage summary, sleep needed, respiratory rate, sleep performance %, start/end). WHOOP REST: GET /v2/activity/sleep/{sleepId}. Scope: read:sleep.

whoop_get_workout

Get a single workout by its id (sport, strain, average/max heart rate, distance, zone durations, start/end). WHOOP REST: GET /v2/activity/workout/{workoutId}. Scope: read:workout.

whoop_list_cycles

List the user's physiological cycles (a WHOOP 'day', ~24h anchored to sleep), most recent first. Each cycle carries a score with day strain, kilojoules burned, and average/max heart rate. Paginated (limit/nextToken) and filterable by created-time window (start/end). WHOOP REST: GET /v2/cycle. Scope: read:cycles.

whoop_list_recoveries

List the user's recoveries, most recent first. Each recovery scores how ready the body is (recovery %, resting heart rate, HRV RMSSD, SpO2 %, skin temperature) and links to its cycle and sleep. Paginated (limit/nextToken) and filterable by created-time window (start/end). WHOOP REST: GET /v2/recovery. Scope: read:recovery.

whoop_list_sleep

List the user's sleep activities, most recent first. Each carries a score with sleep-stage summary, sleep needed, respiratory rate, and sleep performance %. Paginated (limit/nextToken) and filterable by created-time window (start/end). WHOOP REST: GET /v2/activity/sleep. Scope: read:sleep.

whoop_list_workouts

List the user's workouts, most recent first. Each carries a score with strain, average/max heart rate, distance (meters), and per-heart-rate-zone durations. Paginated (limit/nextToken) and filterable by created-time window (start/end). WHOOP REST: GET /v2/activity/workout. Scope: read:workout.

Endpoints

URL	Transport	State	Latency	Checked
https://whoop.usefulapi.io/mcp	streamable-http	answering	71 ms	7 min ago

Alternatives to WHOOP MCP by usefulapi

same job, measured the same way

WHOOP

by mcp-dir

Your WHOOP data in the assistant, read-only: recovery, sleep, strain, workouts, cycles and body meas

13 tools answering

Whoop

by shashankswe2020-ux

MCP server for WHOOP health data — recovery, sleep, workouts, cycles, and trends.

722 installs/wk local only

Whoop MCP Server

by zayden16

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

local only

WHOOP Health Signals

by yadheedhya06

Local-first, read-only WHOOP MCP server for recovery, sleep, strain, workouts, and body signals

63 installs/wk local only

Oura MCP by usefulapi

by usefulapi

Read sleep, readiness, activity, stress, heart rate and workouts from the Oura Ring.

10 tools answering

Checkout.com MCP by usefulapi

by usefulapi

Read Checkout.com payments, disputes, reports and payouts.

18 tools answering

WHOOP MCP

by cunicopia-dev

Sync WHOOP recovery, sleep, strain, and workouts into Postgres and query them from any MCP client.

82 installs/wk local only

Mindbody MCP by usefulapi

by usefulapi

Read Mindbody classes, schedules, clients, staff and sales; book clients and appointments.

20 tools answering

WHOOP MCP by usefulapi — questions

Answers built from our own checks of this server.

What can WHOOP MCP by usefulapi do?

It exposes 10 tools, read directly from the server on our last check. Among them: whoop_body_measurement, whoop_get_cycle, whoop_get_cycle_recovery, whoop_get_profile, whoop_get_sleep, whoop_get_workout and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is WHOOP MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 82 ms. The bar chart above shows every period we have measured.

How do I connect WHOOP MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does WHOOP MCP by usefulapi need an API key?

No. WHOOP MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is WHOOP MCP by usefulapi?

It answers our handshake in 82 ms on average, which is faster than 90% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is WHOOP MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.