Log inSubmit server
Whoop MCP logo

Whoop MCP

Connects MCP-compatible agents to local WHOOP recovery, sleep, strain, and HRV summaries.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Whoop MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "whoop-mcp-3": {
      "command": "npx",
      "args": [
        "-y",
        "delx-wellness-hermes"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y delx-wellness-hermes

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 10d ago.

Overview

WHOOP recovery, sleep, strain, and HRV data become agent-readable through the whoop-mcp MCP server using a local OAuth setup. It provides connection checks, data-domain discovery, synthetic demo payloads, and daily or weekly summaries over MCP. Tokens remain on the local machine, while the server handles WHOOP API access and response normalization. Reach for it when an agent needs personal WHOOP context for training, sleep, recovery, or performance workflows.

Use cases

  • Review today’s WHOOP readiness and sleep signals
  • Compare this week’s recovery and training load with the prior week
  • Test an agent’s WHOOP data handling with synthetic payloads
  • Check local OAuth readiness before requesting account data

Key features

  • Local OAuth-based WHOOP access
  • Synthetic demo recovery, sleep, and strain payloads
  • Connection and data-inventory checks
  • Daily readiness and sleep summaries
  • Weekly scorecards and comparisons
  • Local token handling

Tools5

What Whoop MCP lets your agent do. Expand a tool for its parameters.

Self-reported~120 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

10/10 checks healthy over the last 51d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev ¡ delx-wellness-hermes (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars14Stargazers on the source repository.
npm downloads143Package downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed5Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Whoop MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Whoop MCP

whoop-mcp is an MCP server that connects AI agents to a user’s WHOOP account for recovery, sleep, strain, and HRV context. Its main tools provide synthetic demos, connection checks, data inventories, daily summaries, and weekly summaries. OAuth and token handling run locally, and the project is unofficial.

Install it through `npx` and run its setup command. Use `npx -y whoop-mcp-unofficial setup`, provide a WHOOP Developer app client ID and secret, then run `npx -y whoop-mcp-unofficial auth` and `doctor` to authorize and verify the local setup.

Yes, whoop-mcp works with Cursor through the standard MCP configuration shown in the README. Add an MCP server entry that starts `npx` with `-y whoop-mcp-unofficial` after completing the WHOOP setup and authorization steps.

Yes, call `whoop_demo` to receive realistic synthetic recovery, sleep, and strain data without OAuth. The response is marked `is_demo: true`, and JSON mode exposes the sample shape used by the live summary tools.

Related MCP servers

All in Sports All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWhoop MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/whoop-mcp-3?style=directory)](https://allmcps.com/mcp/whoop-mcp-3)
HTML Embed
<a href="https://allmcps.com/mcp/whoop-mcp-3"><img src="https://allmcps.com/api/badge/whoop-mcp-3?style=directory" alt="Whoop MCP on AllMCPs" /></a>