Health · Local MCP server
Whoop
MCP server for WHOOP health data - recovery, sleep, workouts, cycles, and trends.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.shashankswe2020-ux/whoop- Version
- 0.5.2
- Status
- Active
- Category
- health
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-03
- Updated
- 2026-06-03
- Publisher
- shashankswe2020-ux (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/shashankswe2020-ux) · how
- Repository
- github.com/shashankswe2020-ux/whoop-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | whoop-ai-mcp | 0.5.2 | stdio |
How to connect Whoop
Whoop runs locally from a Node.js package published to the npm registry: whoop-ai-mcp version 0.5.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y whoop-ai-mcp@0.5.2. It reads these environment variables: WHOOP_CLIENT_ID (required, secret) and WHOOP_CLIENT_SECRET (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"whoop": {
"command": "npx",
"args": [
"-y",
"whoop-ai-mcp@0.5.2"
],
"env": {
"WHOOP_CLIENT_ID": "<secret>",
"WHOOP_CLIENT_SECRET": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More health servers
| Server | Runs |
|---|---|
| Wellness ProjectConnect your health, fitness, nutrition, sleep, and wearable data to your AI assistant. | Remote · HTTPLive check: sign-in required |
| WgerWger MCP - wraps wger Workout Manager REST API (free, no auth for read) | Remote · HTTPLive check: ✓ handshake |
| Wger MCPExercises, muscles, and workout data from the open wger database. No key required. | Local · stdio |
| WHOOPYour WHOOP data in the assistant, read-only: recovery, sleep, strain, workouts, cycles and body meas. | Remote · HTTPLive check: ✓ handshake |
| WhoopRead WHOOP recovery, sleep, cycles, workouts and body measurements. | Remote · HTTPLive check: ✓ handshake |
| WHOOP - MissingMCPWHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source. | Remote · HTTPLive check: sign-in required |
| WHOOP Health SignalsLocal-first, read-only WHOOP MCP server for recovery, sleep, strain, workouts, and body signals. | Local · stdio |
| Whoop MCPMCP server for WHOOP - gives Claude access to your recovery, sleep, strain, and workout data. | Local · stdio |