whoop-tracker-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_auth_url | Generate OAuth authorization URL for Whoop |
| whoop_exchange_token | Exchange authorization code for access token |
| whoop_refresh_token | Refresh the access token using refresh token |
| whoop_get_profile | Get basic user profile (name, email) |
| whoop_get_body_measurement | Get user body measurements (height, weight, max heart rate) |
| whoop_get_cycles | Get physiological cycles for a date range |
| whoop_get_cycle_by_idB | Get a specific cycle by ID |
| whoop_get_recoveryC | Get recovery data for a date range |
| whoop_get_recovery_for_cycleA | Get recovery for a specific cycle |
| whoop_get_sleep | Get sleep data for a date range |
| whoop_get_sleep_by_id | Get a specific sleep by ID |
| whoop_get_sleep_for_cycleC | Get sleep for a specific cycle |
| whoop_get_workoutsC | Get workout data for a date range |
| whoop_get_workout_by_id | Get a specific workout by ID |
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 5 tools
Tools are mostly distinct: cycles, recovery (two variants but scoped differently), sleep, and workouts. The two recovery tools could cause minor confusion, but descriptions clarify date range vs. cycle-specific.
All tools follow a consistent 'whoop_get_<resource>' pattern with qualifiers like 'by_id' or 'for_cycle'. No mixed conventions or irregular verbs.
With 5 tools covering core fitness metrics (cycles, recovery, sleep, workouts), the count is well-scoped and not excessive or sparse for the server's apparent purpose.
The set covers key read operations, but notably lacks a tool to list cycles (e.g., 'get_cycles'), which agents would need to obtain cycle IDs for other tools. This gap could hinder some workflows.