# whoop-mcp [Health: Active]

**Category:** 🏃 Sports  
**Repository:** https://github.com/davidmosiah/whoop-mcp  
**GitHub Stars:** 14  
**npm Downloads (last month):** 143  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/whoop-mcp-3

## Description
Privacy-first, unofficial WHOOP MCP server for AI health, sleep, recovery, and performance agents.

## Tools
Capabilities this server exposes over MCP:

- **whoop_demo** — realistic **synthetic** recovery/sleep/strain payloads, no OAuth needed (see [See it before you connect](#see-it-before-you-connect))
- **whoop_connection_status** — verify local setup before calling WHOOP
- **whoop_data_inventory** — inventory supported data domains, scopes, privacy modes and recommended first calls without calling WHOOP APIs.
- **whoop_daily_summary** — readiness, sleep, load and action candidates for today
- **whoop_weekly_summary** — scorecard, comparison vs prior week, next-week plan

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "whoop-mcp": {
    "command": "npx",
    "args": ["-y","delx-wellness-hermes"]
  }
}
```

## Documentation

## What whoop-mcp MCP server does

The whoop-mcp MCP server connects MCP-compatible AI agents to data from a user’s WHOOP account. Its focus is read-oriented context for recovery, sleep, strain, HRV, readiness, and training load rather than data entry or device control.

The project is unofficial and is intended for use with the user’s own WHOOP account. It gives an agent structured summaries instead of requiring the user to copy metrics from the WHOOP application. The returned information can support prompts about today’s readiness, recent sleep, training load, and planning for the following week.

## How it works

The server runs locally and uses WHOOP OAuth to obtain access to the account configured by the user. After setup and authorization, an MCP client starts the package through the configured command and can call the available tools.

Before connecting an account, `whoop_demo` provides synthetic recovery, sleep, and strain data. Demo responses are marked with `is_demo: true`, and JSON output follows the shape used by the live summary tools. This makes it possible to inspect the data contract without OAuth or a WHOOP account.

The live summaries combine supported WHOOP data into agent-facing results. Daily output covers readiness, sleep, load, and possible actions. Weekly output includes a scorecard, a comparison with the previous week, and a plan for the next week.

## Setup and configuration

Install and configure the package with the npm commands documented by the project. Create a WHOOP Developer app first and set its redirect URI to `http://127.0.0.1:3000/callback`. Run `npx -y whoop-mcp-unofficial setup` to provide the client ID and secret, then run `npx -y whoop-mcp-unofficial auth` to complete browser-based authorization. The `doctor` command checks whether the local setup is ready.

A standard MCP client configuration starts the package with `npx`, using `-y whoop-mcp-unofficial` as its arguments.

## Tools and capabilities

- `whoop_demo` returns synthetic recovery, sleep, and strain payloads without OAuth.
- `whoop_connection_status` checks the local setup before WHOOP calls are made.
- `whoop_data_inventory` lists supported domains, scopes, privacy modes, and suggested first calls without calling WHOOP APIs.
- `whoop_daily_summary` reports current readiness, sleep, load, and action candidates.
- `whoop_weekly_summary` produces a weekly scorecard, prior-week comparison, and next-week planning context.

The whoop-mcp MCP server also normalizes WHOOP responses and handles pagination as part of its local connector workflow, according to the project description.

## Limitations and notes

The whoop-mcp MCP server is not affiliated with, endorsed by, or supported by WHOOP, Inc. Users should follow WHOOP’s Developer Terms and use the connector only with their own account. Demo results are synthetic and must not be treated as personal measurements. Live access requires a WHOOP Developer app and OAuth authorization. The provided tools describe recovery and performance context; the material does not claim that the server provides medical advice or clinical interpretation.

_Full upstream README: https://allmcps.com/mcp/whoop-mcp-3/readme_