WHOOP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WHOOP_MODE | No | Mode of operation: 'remote' or 'direct' | |
| WHOOP_BASE_URL | No | Base URL of WHOOP-connected app (required for remote mode) | |
| WHOOP_CLIENT_ID | No | Client ID from WHOOP developer dashboard (required for direct mode) | |
| WHOOP_CLIENT_SECRET | No | Client Secret from WHOOP developer dashboard (required for direct mode) |
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_statsB | Full biometric snapshot: recovery, strain, HR, HRV, SpO2, skin temp, sleep, latest workout |
| whoop_get_recoveryB | Recovery score and details: score (0-100), resting HR, HRV, SpO2, skin temp |
| whoop_get_strainC | Daily strain: strain score (0-21), kilojoules, average and max heart rate |
| whoop_get_workoutB | Latest workout: sport, duration, strain, distance, heart rate zones, altitude |
| whoop_get_heart_rateB | Current heart rate with context: HR value, source (live/decay/resting), resting HR baseline |
| whoop_get_sleepB | Latest sleep data: performance %, stages, efficiency, respiratory rate, disturbances, nap flag |
| whoop_get_sleep_needC | Sleep need analysis: baseline need, sleep debt, strain-based need, nap offsets |
| whoop_get_recovery_historyA | Recent recovery scores: daily recovery, resting HR, HRV, SpO2 trends over multiple days |
| whoop_get_strain_historyA | Recent daily strain: strain scores, calories, heart rate trends over multiple days |
| whoop_get_workout_historyC | Recent workouts: sport, duration, strain, calories for multiple past workouts |
| whoop_get_sleep_historyB | Recent sleep data: performance, duration, efficiency, stages over multiple nights |
| whoop_authorizeA | Start OAuth flow to connect a WHOOP account. Returns an authorization URL to open in your browser. Direct mode only. |
| whoop_check_healthB | Connection and endpoint health: status per endpoint, token expiry, connection state |
| whoop_get_cache_statusB | Cache freshness: cached data status, age, TTL remaining |
| whoop_invalidate_cacheA | Force fresh data on next request by invalidating the cache |
| whoop_get_configA | Server configuration: mode, base URL or API target, enabled scopes, cache TTL |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/NathanielDaniels/whoop-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server