Bring WHOOP recovery data into every agent
WHOOP tracks your recovery, sleep, and strain. Connect it to AIP once, and Claude, Claude Code, Codex, or any MCP client can read your data over a single URL — with you deciding which tools each agent sees.
What your agent can do
This is the complete WHOOP tool snapshot AIP exposes: profile, body, recovery, sleep, cycle, and workout reads, plus the account-level OAuth revoke operation. Every tool can be Allow, Confirm, or Hide per agent and connected account.
| Tool | What it does | Access |
|---|---|---|
| getProfileBasic | Basic profile of the connected user: name and email. | read |
| getBodyMeasurement | Body measurements: height, weight, and max heart rate. | read |
| getCycleCollection | All physiological cycles (daily strain), newest first, paginated. | read |
| getCycleById | One physiological cycle by ID. | read |
| getRecoveryCollection | All recovery scores, newest first, paginated. | read |
| getRecoveryForCycle | The recovery score for a specific cycle. | read |
| getSleepCollection | All sleep activities, newest first, paginated. | read |
| getSleepById | One sleep activity by ID, including stages. | read |
| getSleepForCycle | The sleep associated with a specific cycle. | read |
| getWorkoutCollection | All workouts, newest first, paginated. | read |
| getWorkoutById | One workout by ID, with strain and heart-rate zones. | read |
| getActivityMapping | Look up the V2 UUID for a legacy V1 activity ID. | read |
| revokeUserOAuthAccess | Revoke the OAuth access token AIP holds for your WHOOP account. | write |
Capability snapshot: 21 August 2026 · provider source
Why route WHOOP through AIP
WHOOP already holds intimate health signals. AIP adds a separate control boundary between that account and every client you use: review the per-tool control room, keep a recovery coach read-only, and hide body measurements from agents that do not need them. The connection works alongside the rest of the integration catalog, and the pricing page explains how many accounts and agents each plan supports.
How to connect
- Open the dashboard and connect WHOOP — OAuth, one time.
- Create an agent and switch on the WHOOP tools it should see. Everything starts hidden.
- Plug the resulting URL into your agent the way you’d add any other MCP server.
The same URL works in Claude Code, Codex, Cursor, and anything else that speaks MCP — only the config file’s location changes. Agents that don’t speak MCP can use the generated OpenAPI document instead.
What to ask your agent
WHOOP becomes useful when an agent compares signals instead of repeating a single score. These prompts give it a concrete time window and decision to support: