mcp-whoop
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
mcp-whoop
An MCP server that exposes the WHOOP v2 API over Streamable HTTP, authenticated with GitHub OAuth.
It is built for remote use — as a custom connector in claude.ai / Claude
Desktop, or over claude mcp add --transport http — rather than as a local
stdio server. Two consequences follow from that:
Clients authenticate with OAuth, handled by FastMCP's
GitHubProvider. The server publishes/.well-known/oauth-authorization-serverand supports Dynamic Client Registration, which is what claude.ai requires.WHOOP credentials are held server-side. The refresh token is stored on a mounted volume and rotated automatically, so the browser OAuth flow is done once, not after every restart.
Why a GitHub OAuth app?
It is reasonable to ask what GitHub has to do with reading your own WHOOP data. Nothing — GitHub is only the login screen. The chain that puts it there:
claude.ai will not accept a static token. Its connector dialog can send fixed request headers, but that feature is in limited beta. Without it the only way to add a remote MCP server is OAuth.
OAuth needs something that authenticates a human. The server must run an authorization flow, which means a browser sign-in that proves who you are.
The server has no user database, and should not have one. FastMCP's
OAuthProxytranslates between the MCP client and an existing identity provider; it does not store users or passwords itself.
So an identity provider is required, and GitHub is a convenient one. The app
requests the user scope only — it reads your profile, not your repositories —
and the single field taken from it is your login, which is compared against
ALLOWED_GITHUB_LOGINS.
Nothing depends on GitHub specifically. FastMCP ships providers for Google,
Azure, Auth0, Keycloak, Discord, WorkOS and others; swapping is a one-line
import change in server.py plus the matching credentials. What will not
work is FastMCP's InMemoryOAuthProvider — it simulates the flow for tests and
authenticates nobody, so on a public URL it would admit anyone.
Related MCP server: whoop-mcp
Access control
Holding a valid GitHub identity is not enough. ALLOWED_GITHUB_LOGINS lists
the accounts permitted to use the server, and every message is checked against
it. If the list is empty the server refuses to start — an unset allowlist fails
closed rather than exposing health data to any GitHub user.
Tools
Diagnostics — whoop_status
User — whoop_get_profile, whoop_get_body_measurement,
whoop_revoke_access (destructive, requires confirm=true)
Cycles — whoop_get_cycles, whoop_get_cycle, whoop_get_current_cycle,
whoop_get_sleep_for_cycle, whoop_get_recovery_for_cycle
Recovery — whoop_get_recoveries, whoop_get_latest_recovery,
whoop_get_recovery_summary
Sleep — whoop_get_sleeps, whoop_get_sleep, whoop_get_latest_sleep,
whoop_get_sleep_summary
Workouts — whoop_get_workouts, whoop_get_workout,
whoop_get_strain_summary
A WHOOP cycle is a physiological day that begins at sleep onset, not at midnight — which is why cycle ids, not dates, tie sleep and recovery together.
Setup
1. GitHub OAuth app
Create one at Settings → Developer settings → OAuth Apps with the callback
URL <BASE_URL>/auth/callback. Copy the client id and secret.
2. WHOOP developer app
Create one at developer.whoop.com with:
redirect URI
<BASE_URL>/oauth/callbackthese scopes ticked:
read:profile,read:body_measurement,read:cycles,read:recovery,read:sleep,read:workout
You will not find an offline scope in the dashboard, and that is expected.
offline is not configured on the app — it is sent in the authorization
request, and it is what makes WHOOP return a refresh token instead of a
one-hour access token. The server adds it automatically; nothing to do.
3. Configure and run
cp .env.example .env # then fill it in
docker build -t mcp-whoop .
docker run -d --name mcp-whoop --env-file .env -v /srv/whoop-data:/data -p 8000:8000 mcp-whoop4. Connect WHOOP (once)
Open <BASE_URL>/oauth/start?token=<SETUP_TOKEN> in a browser and approve.
The refresh token is written to /data/whoop_token.json with mode 0600.
Verify with the whoop_status tool.
5. Add the connector
Claude Code —
claude mcp add --transport http whoop <BASE_URL>/mcpclaude.ai / Claude Desktop — Settings → Connectors → Add custom connector →
<BASE_URL>/mcp
Both then send you through GitHub to sign in.
Configuration
Variable | Purpose |
| Public URL of this server, no trailing slash |
| GitHub OAuth app credentials |
| Comma-separated logins permitted to connect |
| Stable key for client tokens; unset means clients are signed out on restart |
| WHOOP developer app credentials |
| Guards |
| Token store location (default |
| Bind address (default |
Notes
WHOOP rotates refresh tokens: each refresh returns a new one and invalidates the old. The store therefore writes atomically and under a lock, so a crash or two concurrent requests cannot strand the server without a valid token.
Licence
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for Withings health data — sleep, activity, heart, and body metrics.
Remote MCP server for training, nutrition, wellness, and performance data with OAuth 2.0.
Multi-tenant hosted MCP server for Oura Ring — 21 read-only tools, OAuth per user.
Hosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA local MCP server providing read-only access to WHOOP fitness data via direct OAuth, with a local SQLite cache for offline queries.118 PyPIMIT
- AlicenseAqualityDmaintenanceMCP server providing read access to WHOOP biometric data including recovery, sleep, strain, and workouts.161MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that wraps the Whoop API v2 to let Claude Code pull workouts, sleep, and recovery data.-
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes Whoop API v2 data as tools, enabling natural language queries for cycles, recovery, sleep, workouts, and profile.MIT