whoop-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WHOOP_CLIENT_ID | Yes | Your WHOOP Developer App Client ID | |
| WHOOP_REDIRECT_URI | Yes | Redirect URI for OAuth callback, typically http://localhost:3000/callback | |
| WHOOP_CLIENT_SECRET | Yes | Your WHOOP Developer App Client Secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoop-get-user-profileA | Get basic user profile information (name, email) for the authenticated user |
| whoop-get-user-body-measurementsA | Get body measurements (height, weight, max heart rate) for the authenticated user |
| whoop-revoke-user-accessB | Revoke the access token granted by the user |
| whoop-get-cycle-by-idC | Get the cycle for the specified ID |
| whoop-get-cycle-collectionA | Get all physiological cycles for a user, paginated |
| whoop-get-sleep-for-cycleB | Get sleep data for a specific cycle |
| whoop-get-recovery-collectionB | Get all recovery data for a user, paginated |
| whoop-get-recovery-for-cycleB | Get recovery data for a specific cycle |
| whoop-get-sleep-by-idC | Get the sleep record for the specified ID |
| whoop-get-sleep-collectionB | Get all sleep records for a user, paginated |
| whoop-get-workout-by-idB | Get the workout record for the specified ID |
| whoop-get-workout-collectionA | Get all workout records for a user, paginated |
| whoop-get-authorization-urlB | Get the authorization URL for OAuth flow |
| whoop-exchange-code-for-tokenB | Exchange authorization code for access token |
| whoop-refresh-tokenB | Refresh access token using refresh token |
| whoop-set-access-tokenC | Set the access token for API calls |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool targets a distinct resource or action: OAuth tokens, user profile, and various physiological data (cycles, recovery, sleep, workouts). There is no ambiguity between tools like get-cycle-collection and get-cycle-by-id, as they serve different purposes (list vs. single item).
All tools follow a consistent verb_noun pattern starting with 'whoop-', e.g., whoop-get-cycle-by-id, whoop-get-cycle-collection, whoop-refresh-token. Verbs are clear (get, exchange, refresh, revoke, set) and nouns are specific, making the naming predictable and easy to navigate.
With 16 tools, the set covers the core WHOOP API surface: OAuth authentication, user information, and paginated retrieval of physiological data. The number is appropriate for the domain, providing comprehensive access without being excessive.
The tool set covers all essential operations for the WHOOP API: OAuth flow, user profile, body measurements, and retrieval of cycles, recovery, sleep, and workouts (both collections and by-id or by-cycle). No obvious gaps are present for a read-focused API with token management.