AgentStack
MCP verified MIT Self-run

Whoop Mcp Server

mcp-yuridivonis-whoop-mcp-server · by yuridivonis

MCP server connecting Whoop health data to Claude

No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add mcp-yuridivonis-whoop-mcp-server

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Whoop Mcp Server? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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
  1. Add a volume mounted at /data for persistent SQLite storage
  2. 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
  1. 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](LICENSE) for details.

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.