whoop-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WHOOP_CLIENT_ID | Yes | Your Whoop client ID | |
| WHOOP_TOKEN_PATH | No | Optional custom path for token storage | |
| WHOOP_CLIENT_SECRET | Yes | Your Whoop 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoop_get_profileA | Retrieves basic profile information for the authenticated Whoop user. Returns:
Use this to identify the user and personalize responses. |
| whoop_get_body_measurementsA | Retrieves body measurements for the authenticated Whoop user. Returns:
Useful for calculating calories burned and personalizing workout recommendations. |
| whoop_get_recoveryA | Retrieves recovery data from Whoop including recovery score, HRV, resting heart rate, and SpO2. Recovery score indicates how ready your body is for strain:
Parameters:
Returns for each recovery:
|
| whoop_get_sleepA | Retrieves detailed sleep data from Whoop including sleep stages, performance, and respiratory rate. Parameters:
Returns for each sleep:
|
| whoop_get_workoutsA | Retrieves workout data from Whoop including strain, heart rate zones, calories, and distance. Strain is measured on a 0-21 scale:
Parameters:
Returns for each workout:
|
| whoop_get_cyclesA | Retrieves physiological cycle (day) data from Whoop including daily strain, calories, and heart rate. A cycle represents a physiological day (wake to wake), not a calendar day. Day Strain is cumulative and measured on a 0-21 scale:
Parameters:
Returns for each cycle:
|
| whoop_get_health_overviewA | Gets a comprehensive health overview combining your latest recovery, sleep, and strain data. This is the best tool to use when you want a quick summary of current health status. Returns:
Use this for:
|
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 7 tools
Each tool targets a distinct Whoop data domain: profile, body measurements, recovery, sleep, workouts, cycles, and a combined health overview. The health overview is clearly complementary rather than overlapping, and the parameterized filters on date/limit further distinguish the data-retrieval tools.
All tools follow the exact same 'whoop_get_<resource>' pattern, with clear and consistent resource names. This uniform verb_noun structure makes it easy to predict tool behavior and select the right one.
Seven tools is well-scoped for a Whoop data retrieval server. Each tool covers a meaningful health data category without redundancy, and the count feels appropriately balanced—not too sparse, not overwhelming.
The tool set provides comprehensive read coverage of Whoop's main health data types: profile, body metrics, recovery, sleep, workouts, daily cycles, and a combined overview. Since the server's purpose is data retrieval, the absence of write operations is not a gap; all core data categories are represented, and the health overview tool nicely ties everything together.