whoop
MCP serverSecurityLets your agent check your Whoop fitness stats like recovery, sleep, strain and workouts.
Available today. Use it from your connected AI after setup.
Needs your own whoop account. You sign in to it and approve access when you connect.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use whoop
About this server
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Install whoop
The server’s own address, for the clients that take one directly. Or connect ahel onceand every client you use reads it from one address, with the account kept on ahel rather than in each client’s config.
Claude Code
claude mcp add --transport http --scope user whoop 'https://missingmcp.com/whoop/mcp'Run it once in your project, then open /mcp to approve any sign-in the server asks for.
Claude Desktop
https://missingmcp.com/whoop/mcpAdd a custom connector in Settings, paste this address, and approve the sign-in.
Cursor
cursor://anysphere.cursor-deeplink/mcp/install?name=whoop&config=eyJ1cmwiOiJodHRwczovL21pc3NpbmdtY3AuY29tL3dob29wL21jcCJ9Open the link and Cursor adds the server at that address.
ChatGPT
https://missingmcp.com/whoop/mcpIn Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.
Codex
codex mcp add whoop --url 'https://missingmcp.com/whoop/mcp'Run it once, then sign in with codex mcp login whoop if the server asks for an account.
From the project's README
As published by velkyvenik/missingmcp in README.md. This repository publishes several servers, so only the opening is shown here.
The MCP servers exist. Connecting them shouldn't be complicated.
A multi-user, OAuth 2.1–protected gateway that hosts the connectors Claude is
missing, so a small trusted circle can connect their own accounts from any
Claude client (iOS, Android, Web, Desktop). The flagship connector is
Garmin Connect: the gateway wraps the
unmodified garmin_mcp worker and
adds OAuth, per-user token isolation, and a reverse proxy. WHOOP
is served the same way but in-process, on WHOOP's own official OAuth v2 API.
The core is adapter-based and supports three forward strategies — worker
(garmin), local (whoop, in-process, no subprocess), and remote (MCP +
header injection, for services with a hosted MCP that lacks its own OAuth) —
see Connectors. The reference deployment runs at
missingmcp.com.
Claude → POST /garmin/mcp (Bearer) → Gateway → 127.0.0.1:<port>/mcp (per-user garmin_mcp) → connect.garmin.com
Why
Shortened here. Read the whole README on GitHub.
Signals
- GitHub stars
- 10
- Forks
- 13
- Last commit
- Sep 2026
Advanced
- Delivery
- whoop MCP server → your ahel connector (mcp.ahel.ai) → your AI.
- Item type
- mcp-server
- Key
com-missingmcp-whoop- Source
- github.com/velkyvenik/missingmcp
- Hosted endpoint
https://missingmcp.com/whoop/mcp