Whoop MCP Server

Whoop MCP Server

Connects Whoop health data to Claude via an MCP server, enabling retrieval of recovery, sleep, strain, and workout metrics through natural language tools.

Category
Visit Server

README

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

MCP Tools

Tool Description
get_today Morning briefing with recovery, sleep, and strain
get_recovery_trends Recovery patterns over time with HRV/RHR
get_sleep_analysis Sleep quality trends and stage breakdowns
get_strain_history Training load and calorie trends
sync_data Manually trigger a data sync
get_auth_url Get authorization URL for Whoop connection

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
  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
  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

Variable Description Default
WHOOP_CLIENT_ID Whoop OAuth client ID Required
WHOOP_CLIENT_SECRET Whoop OAuth client secret Required
WHOOP_REDIRECT_URI OAuth callback URL http://localhost:3000/callback
DB_PATH SQLite database path ./whoop.db
PORT HTTP server port 3000
MCP_MODE http for remote, stdio for local http

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.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured