mcpField
W
WHOOP MCP Server

WHOOP MCP Server

Local
github.com/RyanLisseHealth0Updated 82w ago
Repository

About WHOOP MCP Server

WHOOP MCP Server connects AI assistants to WHOOP fitness data through the WHOOP API. It provides access to profile, sleep, workout, recovery, and cycle information for WHOOP account holders with API access.

Key features

  1. 01Retrieve WHOOP profile data
  2. 02Read sleep data and analytics
  3. 03Fetch workout information
  4. 04Access recovery metrics
  5. 05View cycle data

Use cases

  1. 01Review sleep across a date range
  2. 02Inspect workout history
  3. 03Check recovery metrics
  4. 04Retrieve WHOOP profile and cycle details

MCP support

It implements an MCP server that exposes WHOOP API data to AI assistant clients. Access requires a WHOOP API key.

#whoop#mcp-server#fitness-data

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

WHOOP MCP Server

An MCP (Machine Conversation Protocol) server implementation for the WHOOP API.

Overview

This project provides a server that interfaces with the WHOOP API, allowing you to interact with your WHOOP fitness data. It follows the MCP architecture pattern, which enables interoperability with AI assistants.

Features

  • Access to WHOOP user profile data
  • Retrieve sleep data and analytics
  • Fetch workout information
  • Get recovery metrics
  • View cycle data

Prerequisites

Installation

  1. Clone this repository:

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

  2. Install dependencies:

    npm install

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

    cp .env.example .env

  4. Edit the .env file and add your WHOOP API key and other configuration options.

Usage

Starting the Server
npm start

For development with auto-restart:

npm run dev

The server will start on the port specified in your .env file (default: 3000).

API Endpoints

All API endpoints require authentication with your WHOOP API key.

User Profile
  • GET /whoop/profile - Get user profile information
Sleep Data
  • GET /whoop/sleep?start_date=YYYY-MM-DD&end_date=YYYY-MM-DD - Get sleep data for the specified date range
Workout Data
  • GET /whoop/workouts?start_date=YYYY-MM-DD&end_date=YYYY-MM-DD - Get workout data for the specified date range
Recovery Data
  • GET /whoop/recovery?start_date=YYYY-MM-DD&end_date=YYYY-MM-DD - Get recovery data for the specified date range
Cycle Data
  • GET /whoop/cycles?start_date=YYYY-MM-DD&end_date=YYYY-MM-DD - Get cycle data for the specified date range

Authentication

Add your WHOOP API token to the Authorization header in your requests:

Authorization: Bearer YOUR_WHOOP_API_TOKEN

License

MIT

Contributing

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.