WHOOP MCP Server for Claude
Access your WHOOP fitness data (recovery, sleep, workouts, cycles) directly in Claude Code, Claude Desktop, and the Claude web app via the Model Context Protocol.
Ask Claude "should I go heavy today?" and have it answer from your actual recovery, HRV, sleep, and strain data.
Features
-
6 powerful tools expose your WHOOP data to Claude:
whoop_get_daily_summary— recovery + sleep + today's strain in one callwhoop_get_recovery— recovery score, HRV, resting HR, SpO2, skin tempwhoop_get_sleep— performance/efficiency scores, sleep stages, disturbanceswhoop_get_workouts— strain, HR zones, calories, distance by sportwhoop_get_cycles— WHOOP day summaries with strain and HR metricswhoop_get_profile/whoop_get_body_measurements— user info and measurements
-
Local & private — runs as a stdio MCP server on your machine; your tokens never leave
-
Automatic token refresh — handles OAuth refresh token rotation seamlessly
-
Works everywhere — Claude Code CLI, Claude Desktop app, and claude.ai/code
Quick Start (3 Steps)
1. Install via pip
pip install whoop-as
2. Run interactive setup
whoop-as-setup
This will:
- Open your browser
- Ask you to sign in to WHOOP
- Automatically save your tokens
- Confirm you're ready to go
3. Add to Claude
Claude Code:
claude mcp add --transport stdio whoop --scope user -- python -m whoop_mcp.server
Claude Desktop (Optional):
Edit ~/Library/Application Support/Claude/claude_desktop_config.json and add:
{
"mcpServers": {
"whoop": {
"command": "python",
"args": ["-m", "whoop_mcp.server"]
}
}
}
That's it! You're ready to use whoop-as with Claude. 🎉
Manual Setup (If Needed)
If you prefer to configure manually or have an existing WHOOP developer app:
1. Create a WHOOP Developer App (if you don't have one)
- Go to WHOOP Developer Dashboard
- Sign in with your WHOOP account
- Create an App with Redirect URI:
http://localhost:8766/callback - Enable scopes:
offline read:profile read:recovery read:cycles read:sleep read:workout read:body_measurement - Copy your Client ID and Client Secret
2. Set environment variables
export WHOOP_CLIENT_ID=your_client_id
export WHOOP_CLIENT_SECRET=your_client_secret
Or create ~/.whoop-as/.env:
mkdir -p ~/.whoop-as
cat > ~/.whoop-as/.env << 'EOF'
WHOOP_CLIENT_ID=your_client_id
WHOOP_CLIENT_SECRET=your_client_secret
EOF
3. Run setup
whoop-as-setup
Usage
Once installed, you can ask Claude things like:
- "Show me my recovery and sleep for the last week"
- "How's my strain today?"
- "What was my hardest workout this month?"
- "Should I go heavy or recovery today?"
Claude will use the WHOOP tools to fetch real data and answer based on your actual fitness metrics.
Troubleshooting
| Problem | Solution |
|---|---|
No WHOOP tokens found |
Run whoop-mcp-auth to authenticate |
redirect_uri mismatch |
Ensure .env WHOOP_REDIRECT_URI matches your Dashboard settings exactly |
Permission denied (403) |
Enable all required scopes in the Developer Dashboard, then re-run whoop-mcp-auth |
| Auth fails silently | Check that WHOOP_CLIENT_ID and WHOOP_CLIENT_SECRET are correct in .env |
| Tokens keep expiring | The refresh token was revoked — re-run whoop-mcp-auth |
| MCP server won't connect | Verify the server is running: python -m whoop_mcp.server should start without errors |
Development
To develop locally:
git clone https://github.com/anmolsharma/whoop-mcp.git
cd whoop-mcp
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
whoop-mcp-auth
python -m whoop_mcp.server
License
MIT — See LICENSE for details.
Metadata
Release files for whoop-as 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| whoop_as-1.0.1.tar.gz | 13.0 kB | Without provenance | Details for whoop_as-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| whoop_as-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for whoop_as-1.0.1-py3-none-any.whl |
Total release size: 28.2 kB
Release files / whoop_as-1.0.1.tar.gz
| Download URL | whoop_as-1.0.1.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
85e9e7e9e66baddc0f6d590662820877621e0169965edbad8f0a71e53626a2b8
|
|
BLAKE2b-256 checksum How to use checksums |
b9a1b47c03a0729a8d364157d739d0ca0cdff86e52e737ea66154bacfc744e98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Release files / whoop_as-1.0.1-py3-none-any.whl
| Download URL | whoop_as-1.0.1-py3-none-any.whl |
|---|---|
| Size | 15.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aca8225745f74ff720f37efdb042216401ec39a19b4560ca38b78ed10fc724bb
|
|
BLAKE2b-256 checksum How to use checksums |
12f1462f6e96b586a2069015a2cfa65296340b05c2d398e10a7afcb0ba2fbd2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for whoop-as 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.