WHOOP MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@WHOOP MCP Server show my recovery score from yesterday"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
WHOOP MCP Server
A Model Context Protocol (MCP) server that provides access to all WHOOP API endpoints. This server allows you to integrate WHOOP fitness and health data into your applications through the MCP standard.
Features
Complete WHOOP API Coverage: Access to all WHOOP v2 API endpoints
OAuth 2.0 Authentication: Secure authentication flow
User Data: Profile information and body measurements
Cycles: Physiological cycle data with strain and heart rate metrics
Recovery: Recovery scores, HRV, and resting heart rate data
Sleep: Detailed sleep analysis including stages and performance metrics
Workouts: Exercise data with strain, heart rate zones, and activity metrics
Pagination Support: Handle large datasets with pagination
TypeScript: Full type safety and IntelliSense support
Related MCP server: whoop-tracker-mcp-server
Prerequisites
Node.js 18+
WHOOP Developer Account
WHOOP API credentials
Setup
1. Install Dependencies
npm install2. WHOOP API Setup
Go to the WHOOP Developer Platform
Create a new application
Note your
Client IDandClient SecretSet your redirect URI (e.g.,
http://localhost:3000/callback)
3. Environment Configuration
Copy the example environment file and configure your WHOOP credentials:
cp env.example .envEdit .env with your WHOOP API credentials:
# WHOOP API Configuration
WHOOP_CLIENT_ID=your_client_id_here
WHOOP_CLIENT_SECRET=your_client_secret_here
WHOOP_REDIRECT_URI=http://localhost:3000/callback
# MCP Server Configuration
MCP_SERVER_PORT=30014. Build and Run
# Build the project
npm run build
# Run the MCP server
npm start
# Or run in development mode
npm run devAuthentication Flow
The MCP server supports OAuth 2.0 authentication with WHOOP. Here's how to authenticate:
Get Authorization URL: Use the
whoop-get-authorization-urltool to get the OAuth URLUser Authorization: Direct users to the authorization URL
Copy Authorization Code: When WHOOP redirects you back, copy the authorization code from the URL
Share Code with Claude: IMPORTANT - You must copy and paste the authorization code directly to Claude in the chat
Exchange Code: Claude will use the
whoop-exchange-code-for-tokentool with the authorization codeSet Access Token: Claude will use the
whoop-set-access-tokentool to set the access token for API calls
⚠️ Important Note About Authorization Codes
When you complete the WHOOP authorization in your browser, you'll be redirected to a URL that contains an authorization code. You must copy this code and paste it directly into your chat with Claude. The code will look something like this in the URL:
http://localhost:3000/callback?code=ABC123XYZ789&scope=read:recovery%20read:cycles...Copy the code parameter value (e.g., ABC123XYZ789) and paste it in your chat with Claude. Claude will then use this code to exchange it for an access token and set up the connection to your WHOOP data.
Available Tools
User Tools
whoop-get-user-profile- Get basic user profile informationwhoop-get-user-body-measurements- Get body measurements (height, weight, max heart rate)whoop-revoke-user-access- Revoke user access token
Cycle Tools
whoop-get-cycle-by-id- Get specific cycle data by IDwhoop-get-cycle-collection- Get paginated list of cycleswhoop-get-sleep-for-cycle- Get sleep data for a specific cycle
Recovery Tools
whoop-get-recovery-collection- Get paginated recovery datawhoop-get-recovery-for-cycle- Get recovery data for a specific cycle
Sleep Tools
whoop-get-sleep-by-id- Get specific sleep record by IDwhoop-get-sleep-collection- Get paginated sleep records
Workout Tools
whoop-get-workout-by-id- Get specific workout record by IDwhoop-get-workout-collection- Get paginated workout records
OAuth Tools
whoop-get-authorization-url- Get OAuth authorization URLwhoop-exchange-code-for-token- Exchange authorization code for access tokenwhoop-refresh-token- Refresh access tokenwhoop-set-access-token- Set access token for API calls
Usage Examples
Getting User Profile
// First set your access token
await callTool('whoop-set-access-token', { accessToken: 'your_access_token' });
// Then get user profile
const profile = await callTool('whoop-get-user-profile', {});Getting Recent Cycles
const cycles = await callTool('whoop-get-cycle-collection', {
limit: 10,
start: '2024-01-01T00:00:00Z'
});Getting Sleep Data
const sleepData = await callTool('whoop-get-sleep-collection', {
limit: 5,
end: '2024-01-31T23:59:59Z'
});Getting Workout Data
const workouts = await callTool('whoop-get-workout-collection', {
limit: 10,
start: '2024-01-01T00:00:00Z'
});Data Types
The server provides comprehensive TypeScript types for all WHOOP API responses:
User Data: Profile information, body measurements
Cycles: Strain scores, heart rate data, kilojoule expenditure
Recovery: Recovery scores, HRV, resting heart rate, SpO2, skin temperature
Sleep: Sleep stages, performance metrics, respiratory rate, efficiency
Workouts: Activity strain, heart rate zones, distance, altitude data
Pagination
Most collection endpoints support pagination with the following parameters:
limit: Number of records to return (max 25)start: Start time filter (ISO 8601)end: End time filter (ISO 8601)nextToken: Token for next page
Error Handling
The MCP server includes comprehensive error handling:
Invalid credentials
Rate limiting
Network errors
Invalid parameters
Missing required fields
Development
Project Structure
src/
├── index.ts # Main entry point
├── mcp-server.ts # MCP server implementation
├── whoop-api.ts # WHOOP API client
└── types.ts # TypeScript type definitionsAvailable Scripts
npm run build- Build the TypeScript projectnpm start- Run the built servernpm run dev- Run in development mode with hot reloadnpm run watch- Watch for changes and rebuild
Adding New Endpoints
To add new WHOOP API endpoints:
Add the endpoint method to
WhoopApiClientinwhoop-api.tsAdd corresponding types to
types.tsAdd the tool definition and handler to
mcp-server.ts
WHOOP API Documentation
For detailed information about the WHOOP API, visit:
License
MIT License - see LICENSE file for details.
Support
For issues and questions:
Check the WHOOP API documentation
Review the error messages from the MCP server
Ensure your OAuth credentials are correctly configured
Verify your access token is valid and not expired
Migration Notice
IMPORTANT: WHOOP v2 API is now available and migration is required by October 1, 2025. The current v1 API and webhooks will be removed after this date. This MCP server uses the v2 API.
Available Tools
16 toolswhoop-exchange-code-for-tokenB
Exchange authorization code for access token
Inputs: code (required).
whoop-get-authorization-urlB
Get the authorization URL for OAuth flow
Inputs: no named parameters.
whoop-get-cycle-by-idC
Get the cycle for the specified ID
Inputs: cycleId (required).
whoop-get-cycle-collectionA
Get all physiological cycles for a user, paginated
Inputs: limit, start, end, nextToken.
whoop-get-recovery-collectionB
Get all recovery data for a user, paginated
Inputs: limit, start, end, nextToken.
whoop-get-recovery-for-cycleB
Get recovery data for a specific cycle
Inputs: cycleId (required).
whoop-get-sleep-by-idC
Get the sleep record for the specified ID
Inputs: sleepId (required).
whoop-get-sleep-collectionB
Get all sleep records for a user, paginated
Inputs: limit, start, end, nextToken.
whoop-get-sleep-for-cycleB
Get sleep data for a specific cycle
Inputs: cycleId (required).
whoop-get-user-body-measurementsA
Get body measurements (height, weight, max heart rate) for the authenticated user
Inputs: no named parameters.
whoop-get-user-profileA
Get basic user profile information (name, email) for the authenticated user
Inputs: no named parameters.
whoop-get-workout-by-idB
Get the workout record for the specified ID
Inputs: workoutId (required).
whoop-get-workout-collectionA
Get all workout records for a user, paginated
Inputs: limit, start, end, nextToken.
whoop-refresh-tokenB
Refresh access token using refresh token
Inputs: refreshToken (required).
whoop-revoke-user-accessB
Revoke the access token granted by the user
Inputs: no named parameters.
whoop-set-access-tokenC
Set the access token for API calls
Inputs: accessToken (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Most tools have distinct purposes targeting specific resources like cycles, sleep, workouts, recovery, and authentication. However, there is some potential overlap between collection tools (e.g., whoop-get-cycle-collection and whoop-get-recovery-collection) and their cycle-specific counterparts (e.g., whoop-get-recovery-for-cycle), which could cause minor confusion in selection.
All tools follow a consistent verb_noun pattern with the prefix 'whoop-' and clear action-object naming (e.g., whoop-get-cycle-by-id, whoop-refresh-token). The naming is uniform across all 16 tools, making them predictable and easy to understand.
With 16 tools, the count is slightly high but reasonable for a fitness/health API server covering authentication, user data, cycles, sleep, workouts, and recovery. It provides comprehensive coverage without being overly bloated, though it borders on the upper limit of typical scoping.
The tool set covers core CRUD-like operations for key resources (cycles, sleep, workouts, recovery) and includes essential authentication flows (OAuth, token management). Minor gaps exist, such as lack of update or delete operations for user data or workout records, but agents can likely work around these for most use cases.
Maintenance
Related MCP Connectors
Read WHOOP recovery, sleep, cycles, workouts and body measurements.
Read your Aidlab sleep, heart rate, HRV, steps and workouts through OAuth. Read-only access.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Your WHOOP data in the assistant, read-only: recovery, sleep, strain, workouts, cycles and body meas
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables querying WHOOP fitness data including recovery, sleep, workouts, physiological cycles, and profile via the WHOOP API v2.1114 npmMIT
- AlicenseBqualityDmaintenanceIntegrates with Whoop API v2 to access user profile, sleep, recovery, cycles, and workout data via natural language, with OAuth2 authentication and automatic token refresh.1418 npmMIT
- AlicenseAqualityCmaintenanceEnables Claude to query personal WHOOP health data including recovery, sleep, strain, workouts, and profile via WHOOP's OAuth 2.0 REST API.614 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables read-only access to your WHOOP health data, including recovery, sleep, strain, workouts, cycles, and body measurements, through the official v2 API with OAuth 2.0.MIT