Whoop MCP Server

Whoop MCP Server

A Model Context Protocol (MCP) server that connects your Whoop health data to Claude. You host it yourself and add it to Claude.ai as a custom connector. Your data is stored on your own server, Claude signs in with a password you choose, and it receives only the answers to the tools it calls.

Built on the Whoop Developer API v2.

This is an independent open-source project. It uses the WHOOP API to access data from WHOOP products, and is not affiliated with, endorsed by, or sponsored by WHOOP.

Features

• Recovery: daily recovery score, HRV, resting heart rate, SpO2, skin temperature
• Sleep: duration, stages, efficiency, performance, respiratory rate
• Strain: daily strain score and calories burned
• Workouts: activity, local start time, duration, strain, heart rate, calories, and time in heart-rate zones 4–5
• Auto-sync: before answering, the server pulls new data from Whoop if the last sync is more than an hour old, and keeps everything it has synced (at least the last 90 days) for trends
• Private by default: Claude signs in with a password you choose (OAuth 2.1), so nobody else can read your data

MCP Tools

Setup

1. Create a Whoop Developer App

1. In the Whoop Developer Dashboard, create an app and fill in:

• Contacts: your email. Only Whoop sees it.
• Privacy Policy: the PRIVACY.md in your fork, e.g. https://github.com//whoop-mcp-server/blob/main/PRIVACY.md. People see this link when they approve the app.
• Redirect URL: your server's callback, e.g. https://your-app.up.railway.app/callback
• Scopes: read:recovery, read:cycles, read:sleep, and read:workout. The server doesn't use the others. The login also asks for offline, which lets the server renew its Whoop access without you logging in again; the dashboard doesn't list it.
• Webhooks: leave empty.

1. Note your Client ID and Client Secret.

2. Deploy to Railway

1. Fork this repo to your GitHub account
2. Create a new project on Railway and deploy it from your fork
3. Add environment variables:

• WHOOPCLIENTID: Your Whoop app client ID
• WHOOPCLIENTSECRET: Your Whoop app client secret
• WHOOPREDIRECTURI: https://your-app.up.railway.app/callback
• MCPAUTHPASSWORD: the password Claude will ask for when you connect. Generate one with openssl rand -base64 24 and keep it in your password manager. The server refuses to start without it (at least 16 characters).
• ENCRYPTION_SECRET (optional, recommended): generate one with openssl rand -base64 32. It encrypts your stored Whoop tokens, so rotating the Whoop client secret later won't disconnect your account.

1. Add a volume mounted at /data. The database lives there; without a volume, every redeploy loses your data and signs Claude out.
2. Deploy, then open https://your-app.up.railway.app/health to check it's running.

3. Connect Claude

Shortened. The full README is on GitHub.