mcp-whoopCAUTION
Read-only Model Context Protocol server for WHOOP, over stdio. Browser OAuth login with automatic token refresh, and scope-gated tools across WHOOP's v2 API: cycles, sleep, recovery, workouts, profile and body measurements, plus summaries that digest the last N days into one answer.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A Model Context Protocol (MCP) server for WHOOP, served over stdio.
Published on npm as `mcp-whoop`.
Status: pre-1.0. The authentication surface is complete — browser login, automatic token refresh, scope-gated tools, and logout, against WHOOP's v2 API — and every read scope WHOOP defines now carries tools: profile and body measurements, the cycle, sleep, recovery and workout reads, and the summaries over them. The server speaks the current MCP spec revision (2026-07-28) via SDK v2.
Usage
Run directly with npx (Node.js ^22.22.1 || >=24.10.0):
npx mcp-whoop
Logging in
Every user brings their own WHOOP application. Register one in the WHOOP Developer Dashboard, give it a loopback redirect URI (for example http://127.0.0.1:8788/callback), then run the login once in a terminal.
POSIX shells:
WHOOP_CLIENT_ID=... WHOOP_CLIENT_SECRET=... WHOOP_REDIRECT_URI=... npx mcp-whoop login
PowerShell:
$env:WHOOP_CLIENT_ID = "..." $env:WHOOP_CLIENT_SECRET = "..." $env:WHOOP_REDIRECT_URI = "http://127.0.0.1:8788/callback" npx mcp-whoop login
It prints an authorization URL, opens it in your browser, captures the redirect, and saves the resulting tokens — together with the app credentials, which WHOOP requires again on every token refresh — in your platform's per-user data directory. That directory is readable only by you: by file mode on POSIX, and by your user profile's ACLs on Windows, where Node cannot set one.
From then on the server refreshes the rotating tokens by itself; you log in again only if WHOOP stops honoring the stored refresh token. Two optional variables adjust the login: WHOOP_SCOPES narrows what is asked for (all six read scopes by default), and WHOOP_TOKEN_STORE moves the token file elsewhere. Narrowing is required when your app
43c212aa8046OBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add mcp-whoop -- npx -y [email protected]
{
"mcpServers": {
"mcp-whoop": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (14)
14 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
get_body_measurements | read | |
get_cycle | read | |
get_cycle_recovery | read | |
get_cycle_sleep | read | |
get_profile | read | |
get_recovery_summary | read | |
get_sleep | read | |
get_sleep_summary | read | |
get_today_snapshot | read | |
get_workout | read | |
list_cycles | read | |
list_recoveries | read | |
list_sleeps | read | |
list_workouts | read |
Trust audit
CAUTIONgrade B · trust 86/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (4 observation(s))
- Shell
- declared (1 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (12)
WHOOP_REDIRECT_URI=http://127.0.0.1:8788/callback
"must be the URL WHOOP sends the browser back to, like http://127.0.0.1:8788/callback",
remedy: `A login offered inside an MCP client catches WHOOP's redirect on a plain-HTTP loopback port of this machine, so only an http:// loopback redirect URI — one on http://127.0.0.1, http://localho
const secret = "reader-upstream-secret";
new URL("../../dist/index.js", import.meta.url),readFileSync(new URL("../../package.json", import.meta.url), "utf8"),const readmePath = fileURLToPath(new URL("../../README.md", import.meta.url));new URL("../../.env.example", import.meta.url),const readmePath = fileURLToPath(new URL("../../README.md", import.meta.url));loopback redirect URI (for example `http://127.0.0.1:8788/callback`), then run the
$env:WHOOP_REDIRECT_URI = "http://127.0.0.1:8788/callback"
@modelcontextprotocol/server, zod, @biomejs/biome, @commitlint/cli, @commitlint/config-conventional, @modelcontextprotocol/client, @semantic-release/changelog, @semantic-release/git
Gates applied: no_behavioural_pass.
43c212aa8046full audit observations/trust-audit/mcp-server/alixakhribi__mcp-whoop.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | 43c212aa8046 | CAUTION | B | 86 | first audit |
Questions
What is the mcp-whoop MCP server?
Read-only Model Context Protocol server for WHOOP, over stdio. Browser OAuth login with automatic token refresh, and scope-gated tools across WHOOP's v2 API: cycles, sleep, recovery, workouts, profile and body measurements, plus summaries that digest the last N days into one answer.
What tools does mcp-whoop expose?
14 in total: 14 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is mcp-whoop safe to connect to an agent?
With care. The audit graded it B (86/100) and found 12 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does mcp-whoop need?
No credential environment variables were found in its source, so it appears to need none.
How current is this page?
The grade is for one exact copy of the source (43c212aa8046), read on 2026-10-12. The repository is watched and re-audited when it changes.