Whoop MCP Server

A Model Context Protocol (MCP) server that connects your Whoop health data to Claude. Designed to be hosted remotely and used as a custom connector in Claude.ai.

Built using the Whoop Developer API v2.

Features

• Recovery Data: Daily recovery scores, HRV, resting heart rate, SpO2, skin temperature

• Sleep Analysis: Sleep duration, stages, efficiency, performance, respiratory rate

• Strain Tracking: Daily strain scores, calories burned, heart rate zones

• Workout History: All logged workouts with detailed metrics

• Auto-Sync: Automatically keeps data fresh with smart sync logic

• 90-Day History: Maintains local cache of your health data for trend analysis

Related MCP server: WHOOP MCP Server

MCP Tools

Setup

1. Create a Whoop Developer App

1. Go to developer.whoop.com

2. Create a new application

3. Note your Client ID and Client Secret

4. Set the redirect URI to your deployed server's callback URL (e.g., https://your-app.railway.app/callback)

2. Deploy to Railway

1. Fork/push this repo to GitHub

2. Create a new project on Railway

3. Connect your GitHub repo

4. Add environment variables:

   • WHOOP_CLIENT_ID: Your Whoop app client ID

   • WHOOP_CLIENT_SECRET: Your Whoop app client secret

   • WHOOP_REDIRECT_URI: https://your-app.railway.app/callback

• MCP_AUTH_TOKEN: a long random secret — generate with openssl rand -hex 32. The server refuses to start without it.

• DB_PATH: /data/whoop.db

5. Add a volume mounted at /data for persistent SQLite storage

6. Deploy!

3. Authorize with Whoop

1. Visit https://your-app.railway.app/health to verify it's running

2. The first time you use the get_auth_url tool in Claude, it will provide an authorization link

3. Visit the link, log in to Whoop, and authorize the app

4. You'll be redirected back and the initial 90-day sync will begin

4. Connect to Claude

1. Go to Claude.ai settings → Connectors

2. Click "Add custom connector"

3. Enter:

   • Name: Whoop

   • Remote MCP server URL: https://your-app.railway.app/mcp/<your MCP_AUTH_TOKEN> (the token in the URL is what authenticates Claude; an Authorization: Bearer header also works)

4. Use it in any chat!

Local Development

# Install dependencies
npm install

# Create .env file
cat > .env << EOF
WHOOP_CLIENT_ID=your_client_id
WHOOP_CLIENT_SECRET=your_client_secret
WHOOP_REDIRECT_URI=http://localhost:3000/callback
MCP_MODE=http
EOF

# Run in development mode
npm run dev

Environment Variables

Architecture

┌─────────────────────────────────────────────────┐
│              Whoop MCP Server                   │
│                                                 │
│  ┌─────────────┐      ┌──────────────────┐    │
│  │ MCP Server  │◄────►│  SQLite Database │    │
│  │ (HTTP)      │      │  - cycles        │    │
│  └─────────────┘      │  - recovery      │    │
│         │             │  - sleep         │    │
│         │             │  - workouts      │    │
│         ▼             │  - tokens        │    │
│  ┌─────────────┐      └──────────────────┘    │
│  │ Whoop API   │                               │
│  │ Client      │                               │
│  └─────────────┘                               │
└─────────────────────────────────────────────────┘
         │
         ▼
┌─────────────────────────────────────────────────┐
│  Claude.ai (Custom Connector)                   │
│  "Hey, what's my recovery today?"               │
└─────────────────────────────────────────────────┘

API Endpoints Used

This server uses the following Whoop API v2 endpoints:

• GET /v2/user/profile/basic - User profile

• GET /v2/user/measurement/body - Body measurements

• GET /v2/cycle - Physiological cycles (strain data)

• GET /v2/recovery - Recovery scores

• GET /v2/activity/sleep - Sleep records

• GET /v2/activity/workout - Workout records

License

MIT - See LICENSE for details.