WHOOP MCP Server
maangy/whoop-mcp
Integre dados de saúde WHOOP ao Claude em tempo real
Ver no GitHubServidor MCP que integra dados de saúde e recuperação do WHOOP diretamente ao Claude via OAuth 2.0. Acessa métricas de recuperação, sono, treinos, ciclos fisiológicos e medições corporais através da API v2 do WHOOP.
Instalação
npx convez-ai maangy/whoop-mcp1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Análise de padrões de sono e recuperação com Claude
- Acompanhamento de desempenho em treinos e carga de trabalho
- Consultas sobre saúde e bem-estar com contexto de dados pessoais
- Monitoramento de métricas fisiológicas (HRV, frequência cardíaca, SpO2)
Veredito

Integração bem construída com a plataforma WHOOP que oferece acesso completo aos dados de saúde via MCP. Requer configuração OAuth e conta developer, mas uma vez ativa fornece contexto rico de saúde ao Claude para análises e consultas personalizadas.
README
A tradução para o português deste README ainda está na fila.
WHOOP MCP Server
A Model Context Protocol server that gives Claude access to your WHOOP health data via the WHOOP Developer API (API v2).
Tools
| Tool | Description |
|---|---|
authenticate | Start the OAuth 2.0 flow — call this once to connect your WHOOP account |
get_recovery | Latest recovery score, HRV, resting heart rate, SpO2, skin temperature |
get_sleep | Sleep duration, efficiency, stage breakdown, disturbances, respiratory rate |
get_workouts | Recent workouts with strain, sport type, HR zones, calories |
get_cycles | Physiological cycles (days) with strain and recovery summary |
get_body_measurements | Height, weight, and max heart rate |
get_profile | Basic profile (name, email) |
Parameters: the data tools (get_recovery, get_sleep, get_workouts, get_cycles) accept optional filters:
limit— number of records to return (default 1 for recovery/sleep, 5 for workouts/cycles; max 25)start_date/end_date— ISO 8601 timestamps, e.g.2024-01-01T00:00:00.000Zinclude_naps—get_sleeponly; include nap records (defaultfalse)
get_body_measurements and get_profile take no parameters.
Prerequisites
- Node.js 18 or later
- A WHOOP Developer account and OAuth app
Setup
1. Create a WHOOP Developer App
- Go to https://developer.whoop.com/ and sign in.
- Create a new application.
- Add
http://localhost:8080/callbackas a Redirect URI (or use a custom port — just keep it consistent withWHOOP_REDIRECT_URI). - Enable the following scopes on the app — the server requests all of them, and data tools will return empty or fail if any are missing:
offline(required — grants the refresh token so you only authenticate once)read:recoveryread:sleepread:workoutread:cyclesread:body_measurementread:profile
- Copy your Client ID and Client Secret.
2. Install and build
git clone <this-repo>
cd whoop-mcp
npm install
npm run build
3. Configure environment variables
cp .env.example .env
Edit .env:
WHOOP_CLIENT_ID=your_client_id_here
WHOOP_CLIENT_SECRET=your_client_secret_here
WHOOP_REDIRECT_URI=http://localhost:8080/callback
Security note:
.envis never committed. Tokens are stored in~/.whoop-mcp-tokens.jsonwith600permissions (owner read/write only).
4. Add to Claude's MCP configuration
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json)
{
"mcpServers": {
"whoop": {
"command": "node",
"args": ["/absolute/path/to/whoop-mcp/dist/index.js"],
"env": {
"WHOOP_CLIENT_ID": "your_client_id_here",
"WHOOP_CLIENT_SECRET": "your_client_secret_here",
"WHOOP_REDIRECT_URI": "http://localhost:8080/callback"
}
}
}
}
You can either set the env vars here or rely on a
.envfile in the project root (loaded bydotenv).
Claude Code (.claude/settings.json or via claude mcp add)
claude mcp add whoop node /absolute/path/to/whoop-mcp/dist/index.js \
-e WHOOP_CLIENT_ID=your_client_id \
-e WHOOP_CLIENT_SECRET=your_client_secret \
-e WHOOP_REDIRECT_URI=http://localhost:8080/callback
Or manually in .claude/settings.json:
{
"mcpServers": {
"whoop": {
"command": "node",
"args": ["/absolute/path/to/whoop-mcp/dist/index.js"],
"env": {
"WHOOP_CLIENT_ID": "...",
"WHOOP_CLIENT_SECRET": "...",
"WHOOP_REDIRECT_URI": "http://localhost:8080/callback"
}
}
}
}
5. Authenticate
Once the server is running in Claude, call the authenticate tool:
You: Use the
authenticatetool to connect my WHOOP account.
Claude will display an authorization URL. Open it in your browser, approve access, and the tokens will be saved automatically to ~/.whoop-mcp-tokens.json.
Tokens refresh automatically — you only need to authenticate once.
Example prompts
What was my recovery score this morning?
Show me my last 7 days of sleep data.
How has my HRV trended over the past month?
What workouts did I do this week and what was my strain?
What are my body measurements on WHOOP?
Token storage
- Tokens are stored in
~/.whoop-mcp-tokens.json(or the path inWHOOP_TOKEN_FILE). - The file is created with
0600permissions so only your user can read it. - Access tokens are refreshed automatically 60 seconds before expiry using the stored refresh token.
Development
# Compile TypeScript in watch mode
npm run dev
# Run directly (after building)
npm start
Troubleshooting
| Problem | Fix |
|---|---|
Missing required environment variable | Ensure WHOOP_CLIENT_ID and WHOOP_CLIENT_SECRET are set in .env or the MCP config env block |
Not authenticated | Call the authenticate tool and complete the browser flow |
| Port 8080 already in use | Change WHOOP_REDIRECT_URI to use a different port (e.g. http://localhost:9090/callback) and update your WHOOP app's redirect URI list |
| Token refresh fails | Delete ~/.whoop-mcp-tokens.json and re-authenticate |