Whoop API MCP Server: Real-Time Fitness & Health Data Integration

What is Whoop API MCP Server: Real-Time Fitness & Health Data Integration?

Whoop API MCP Server acts as a bridge between your applications and the Whoop fitness ecosystem. It simplifies access to real-time data like recovery metrics, sleep patterns, workout analytics, and menstrual cycle tracking by handling complex tasks like OAuth 2.0 authentication, error management, and standardized API responses. Think of it as your dedicated control center for turning raw Whoop data into actionable insights.

How to use Whoop API MCP Server: Real-Time Fitness & Health Data Integration?

Getting started is straightforward for developers with Node.js experience:

1. Clone the repository and install dependencies via npm
2. Configure your Whoop API credentials in the .env file
3. Launch the server and initiate authentication through the login endpoint
4. Query endpoints like /recovery/latest or /workout with date parameters

Once set up, the MCP-compliant discovery endpoint provides programmatic access to all available services, making integration seamless for platforms like fitness dashboards or wellness apps.

Key Features of Whoop API MCP Server: Real-Time Fitness & Health Data Integration?

What truly sets this solution apart is its:

• Comprehensive data coverage – from basic user profiles to advanced menstrual cycle tracking
• Time-saving authentication – pre-built OAuth 2.0 flow reduces dev time by 50%+ compared to manual setups
• Granular date filtering – query historical data using precise start/end date parameters
• Developer-friendly logging – clear error messages help diagnose issues in real-time

Its MCP compliance also future-proofs integrations with other mission-critical systems.

Use cases of Whoop API MCP Server: Real-Time Fitness & Health Data Integration?

Common applications include:

• Fitness coaches building personalized recovery dashboards
• Health platforms needing menstrual cycle insights without reinventing authentication
• Corporate wellness programs tracking employee sleep patterns at scale
• Research institutions analyzing workout data trends across user cohorts

FAQ from Whoop API MCP Server: Real-Time Fitness & Health Data Integration?

Q: How do I get Whoop API credentials?
A: Apply through the Whoop Developer Portal after signing their partnership agreement.

Q: What Node.js versions are supported?
A: Officially tested on v16 LTS, but works with v14+ with minimal adjustments.

Q: Can I customize error messages?
A: Yes, response formats are modular and easily extendable in the codebase.

Q: Are historical data queries limited?
A: Rate limits apply based on your Whoop API tier, but the server handles pagination transparently.

Whoop API MCP Server

An MCP (Mission Control Protocol) server for interacting with the Whoop API to retrieve fitness and health data.

Overview

This MCP server provides a standardized interface for accessing Whoop fitness data through its API. It handles authentication, data retrieval, and formatting to make it easy to integrate Whoop data into your applications.

Features

• OAuth 2.0 authentication with Whoop API
• User profile information
• Recovery data
• Sleep data
• Workout data
• Menstrual cycle tracking data
• MCP-compliant discovery endpoint
• Clean error handling and logging

Prerequisites

• Node.js 16.x or higher
• Whoop developer account and API credentials
• Register your app in the Whoop Developer Portal

Installation

1. Clone the repository:

   git clone https://github.com/RyanLisse/whoop-api-mcp.git

cd whoop-api-mcp

2. Install dependencies:

   npm install

3. Create a .env file based on the .env.example:

   cp .env.example .env

4. Update the .env file with your Whoop API credentials:

   WHOOP_CLIENT_ID=your_client_id_here

WHOOP_CLIENT_SECRET=your_client_secret_here
WHOOP_REDIRECT_URI=http://localhost:3000/auth/callback

Usage

1. Start the server:

   npm start

2. The MCP endpoint will be available at:

   http://localhost:3000/.well-known/mcp.json

3. To authenticate a user with Whoop, direct them to:

   http://localhost:3000/auth/login

4. After authentication, you'll receive access and refresh tokens to use with the API endpoints.

Endpoints

• GET /user - Get user profile information
• GET /user/membership - Get user membership information
• GET /recovery?start=YYYY-MM-DD&end=YYYY-MM-DD - Get recovery data for a date range
• GET /recovery/latest - Get most recent recovery data
• GET /sleep?start=YYYY-MM-DD&end=YYYY-MM-DD - Get sleep data for a date range
• GET /workout?start=YYYY-MM-DD&end=YYYY-MM-DD - Get workout data for a date range
• GET /cycle?start=YYYY-MM-DD&end=YYYY-MM-DD - Get menstrual cycle data for a date range

Whoop API Documentation

For more information about the Whoop API, refer to the official Whoop API documentation.

MCP Specification

This server follows the MCP (Mission Control Protocol) specification. The MCP discovery endpoint is available at /.well-known/mcp.json.

License

MIT

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.