Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
docker run -i --rm ghcr.io/yuridivonis/whoop-mcp-server:1.5.1Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
WHOOP_CLIENT_ID=<value> WHOOP_CLIENT_SECRET=<secret> WHOOP_REDIRECT_URI=<value> MCP_AUTH_PASSWORD=<secret> PUBLIC_URL=<value> ENCRYPTION_SECRET=<secret> UPDATE_CHECK=<value> claude mcp add yuridivonis-whoop-mcp-server -- docker run -i --rm ghcr.io/yuridivonis/whoop-mcp-server:1.5.1รันในเทอร์มินัล
{ "mcpServers": { "yuridivonis-whoop-mcp-server": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/yuridivonis/whoop-mcp-server:1.5.1" ], "env": { "WHOOP_CLIENT_ID": "<value>", "WHOOP_CLIENT_SECRET": "<secret>", "WHOOP_REDIRECT_URI": "<value>", "MCP_AUTH_PASSWORD": "<secret>", "PUBLIC_URL": "<value>", "ENCRYPTION_SECRET": "<secret>", "UPDATE_CHECK": "<value>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดYour WHOOP data in whichever AI you use, or, soon, in your own code. Self-hosted, private, and open source.
Ask Claude, ChatGPT or another MCP app "How did I sleep this week?" and get the answer from your own recovery, sleep, strain and workouts. You run the server yourself: it fetches your data from WHOOP when you ask and keeps no copy, and only the apps you've allowed can reach it.
This is an independent open-source project. It uses the WHOOP API to access data from WHOOP products, and is not affiliated with, endorsed by, or sponsored by WHOOP.
Built on the Whoop Developer API v2, and the Model Context Protocol (MCP), the open standard AI apps use to call tools like these.
The template is published by this project's maintainer. Railway pays template creators a share of what deployments spend, and the link carries a referral code; neither costs you anything extra. Railway's Hobby plan is enough.
One click creates a Railway project running the :1 image with a volume, auto updates and generated secrets; there's nothing to fill in. Tested live on 2026-09-29. Then:
whoop-mcp-server-production-xxxx.up.railway.app. Open it.To set it up by hand instead, or elsewhere, read on.
Every release is published as a ready-made image, ghcr.io/yuridivonis/whoop-mcp-server. Deploy that: there's no need to fork this repository unless you want to change the code (see Changing the code). The steps below use Railway; to run it anywhere else, see Docker.
ghcr.io/yuridivonis/whoop-mcp-server:1. Then, in the service's Settings → Networking → Public Networking, choose Generate Domain: that's your server's address, your-app.up.railway.app below. The server works out its Whoop callback address from it.MCP_AUTH_PASSWORD: the password each AI app asks for when you connect it. Generate one with openssl rand -base64 24 and keep it in your password manager. The server refuses to start without it (at least 16 characters).ENCRYPTION_SECRET (optional, recommended): generate one with openssl rand -base64 32. It encrypts your stored Whoop tokens, so rotating the Whoop client secret later won't disconnect your account.WHOOP_CLIENT_ID = replace-with-your-client-id and WHOOP_CLIENT_SECRET = replace-with-your-client-secret for now. The server treats those as unset; you replace them in Create a Whoop Developer App./data. It holds the sign-ins and your encrypted Whoop tokens; without it, every redeploy signs your apps out and disconnects Whoop.:1 tag moves with every 1.x release, and Railway then redeploys the service; on the Pro plan it backs up the volume first.https://your-app.up.railway.app/: the set-up page walks you through the rest. If the deploy fails, open its logs: the server says what's missing.Already running a fork on Railway? Switch it to the image: open the service's Settings, change Service Source to ghcr.io/yuridivonis/whoop-mcp-server:1, and turn on auto updates as in step 4. Keep the same variables and volume, so Whoop stays connected. If your fork is older than 1.3.0, read Upgrading to 1.3.0 first: every app signs in once more. Your fork is then no longer used.
Your server's set-up page, https://your-app.up.railway.app/, walks through Whoop's New App form in the form's own order, with a Copy button on each value to paste. The same, in short:
In the Whoop Developer Dashboard, open New App and fill the form top to bottom:
https://github.com/yuridivonis/whoop-mcp-server/blob/main/PRIVACY.md, or your own adapted copy if you run the server for someone else. People see this link when they approve the app.https://your-app.up.railway.app/callback, exactly as the set-up page shows it.read:recovery, read:cycles, read:sleep and read:workout. The server doesn't use the others. The login also asks for offline, which lets the server renew its Whoop access without you logging in again; the dashboard doesn't list it.Click Create App: Whoop shows the app's Client ID and Client Secret.
In the service's Variables tab, select replace-with-your-client-id in WHOOP_CLIENT_ID and paste the Client ID over it; the same for replace-with-your-client-secret in WHOOP_CLIENT_SECRET; then click Deploy at the top. The set-up page then ticks steps 2 and 3.
If you add a custom domain later, open the set-up page again: if the Redirect URL it shows changed, update it in your Whoop app, or set WHOOP_REDIRECT_URI.
Add your server's address, https://your-app.up.railway.app/mcp, to your AI app as a custom connector. It opens your server's sign-in page: check it names the app you're connecting, enter your MCP_AUTH_PASSWORD, and tick the box allowing it to read your Whoop data. For example, in Claude.ai: Customize → Connectors → + → Add custom connector.
Add to your AI has the steps for Claude, ChatGPT, Claude Code, Cursor, VS Code and Windsurf, and which have been tested. Apps stay signed in across redeploys; anyone without the password gets 401 Unauthorized from /mcp.
get_auth_url).1.3.0 stops keeping a copy of your Whoop data, and asks you before each app receives it. To upgrade:
:1 tag and redeploy (Docker with :1: pull it again and restart). With a fork, use GitHub's Sync fork button, then redeploy, or switch to the image as described in Deploy.Deleted the WHOOP data stored by an earlier version.sync_data is gone. If your app still lists it, remove the connector and add it again.There's no going back to 1.2.x on the upgraded database: it can't sign apps in with the new sign-in tables.
1.1.0 puts a sign-in in front of /mcp. Version 1.0.0 had no authentication there, so any 1.0.0 server that worked with Claude over HTTP served its data to anyone who knew the URL. (Unmodified 1.0.0 also had a request-parsing bug that stopped Claude from connecting over HTTP at all; 1.1.0 fixes both.) To upgrade:
main branch), or switch the service to the image as described in Deploy.MCP_AUTH_PASSWORD in your Railway variables (see Setup, step 1). Without it, the new version won't start. That's deliberate.get_auth_url once to reconnect.read:profile and read:body_measurement. 1.1.0 no longer uses them.If your 1.0.0 server worked with Claude on a public URL, assume your data could have been read. As a precaution, rotate your client secret in the Whoop developer dashboard, update WHOOP_CLIENT_SECRET, and run get_auth_url once afterwards. Unless ENCRYPTION_SECRET is set, the stored Whoop tokens were encrypted with the old client secret. The server starts anyway and treats Whoop as disconnected until you reconnect.
/mcp only answers signed-in clients. Sign-in codes and refresh tokens work once and are stored as hashes; if one is ever used twice, the whole sign-in is revoked.MCP_ALLOWED_REDIRECT_HOSTS. The sign-in page shows where you'll return: only sign in if you started the connection yourself.MCP_AUTH_PASSWORD signs every client out.See SECURITY.md for the full security model and how to report a vulnerability privately, and PRIVACY.md for what a deployment stores and shares.
When you deploy this server, you register your own Whoop developer app, so you are the developer (the "Company") under WHOOP's API Terms of Use, effective 6 October 2026. The terms number their sections but not the paragraphs inside them, so this cites each paragraph by its section and heading. It's a summary of the obligations that touch how the server handles data, not legal advice, and not a promise that any deployment complies: read the terms before you deploy.
Each deployment serves one Whoop account. If you deploy it for someone else, they're your end user, and under 2. Company Applications you're responsible for:
MCP_AUTH_PASSWORD). Don't tick it for them (End User Authorization and Consent).Each release is published as an image for amd64 and arm64 on GitHub's container registry. It runs the same server as the Railway setup above:
docker run -d --name whoop-mcp -p 3000:3000 -v whoop-data:/data \
-e WHOOP_CLIENT_ID=replace-with-your-client-id \
-e WHOOP_CLIENT_SECRET=replace-with-your-client-secret \
-e WHOOP_REDIRECT_URI=https://your-server.example.com/callback \
-e MCP_AUTH_PASSWORD=replace-with-a-password-of-16-or-more-characters \
ghcr.io/yuridivonis/whoop-mcp-server:1
WHOOP_REDIRECT_URI to that address's /callback, and connect your AI app to its /mcp, as with Railway. The set-up page at the server's root shows what's left to do./callback. Add -e PUBLIC_URL=http://localhost:3000, so MCP clients on the same computer connect to http://localhost:3000/mcp.whoop-data volume, so restarts and upgrades keep you connected.:1 always points to the newest 1.x release, so pulling it again (or redeploying) picks up fixes and new features without breaking changes. :1.3.0 and the like pin one exact version; :latest follows every release, including a future 2.0.To check that an image was built by this repository's release workflow, run gh attestation verify oci://ghcr.io/yuridivonis/whoop-mcp-server:1 --owner yuridivonis.
The server is also listed in the official MCP Registry as io.github.yuridivonis/whoop-mcp-server.
Requires Node.js 22 or later.
# Install dependencies
npm install
# Create .env file (npm run dev loads it)
cat > .env << EOF
WHOOP_CLIENT_ID=replace-with-your-client-id
WHOOP_CLIENT_SECRET=replace-with-your-client-secret
# Whoop needs an https address: use your tunnel's (see below)
WHOOP_REDIRECT_URI=https://your-tunnel.example.com/callback
MCP_AUTH_PASSWORD=replace-with-a-password-of-16-or-more-characters
MCP_MODE=http
EOF
# Run in development mode (restarts on changes)
npm run dev
# Run the tests and the type check
npm test
npm run typecheck
The repository is an npm workspace: the server in src/, and the WHOOP API client it's built on in packages/whoop-client, a library you can also use on its own. npm install links the two, and npm test, npm run typecheck, npm run build and npm run dev build the library first. When you're changing the library itself, npx tsc -b -w packages/whoop-client rebuilds it as you go.
Whoop's redirect URLs must be https (or an app scheme), so a server on your computer needs an https tunnel, for example cloudflared tunnel --url http://localhost:3000 or ngrok http 3000. Then:
WHOOP_REDIRECT_URI to the tunnel's /callback address./mcp address.Quick tunnels get a new address every time they start, so you'd repeat steps 1 to 3; a named tunnel keeps one address. The tunnel provider carries the traffic, including the tools' answers.
MCP_MODE=stdio runs the server for MCP clients that start it as a local command. It has no sign-in, because only the app that started it can reach it. It can't receive the Whoop login either, so connect Whoop once with the server in http mode and the same DB_PATH, stop it, then start the stdio server. Don't run both at once: Whoop replaces the refresh token on every use, so two servers sharing one database log each other out.
To run your own changes, fork this repository and deploy the fork instead of the image: on Railway, New → GitHub Repo, which builds the Dockerfile. A fork doesn't update itself: to pick up new releases, use GitHub's Sync fork button and redeploy, and merge your changes as you go. If you don't need changes, the image is simpler and keeps itself up to date.
┌─────────────────────────────────────────────────┐
│ Your AI app (Claude, ChatGPT, ...) │
│ "How did I sleep last night?" │
└────────────────────────┬────────────────────────┘
│ signs in once (OAuth 2.1),
│ then calls tools on /mcp
▼
┌─────────────────────────────────────────────────┐
│ Whoop MCP Server │
│ │
│ ┌─────────────┐ ┌──────────────────┐ │
│ │ Sign-in │─────►│ SQLite Database │ │
│ │ (OAuth 2.1) │ │ - sign-ins │ │
│ └─────────────┘ │ - Whoop tokens │ │
│ ┌─────────────┐ │ (encrypted) │ │
│ │ MCP tools │ └──────────────────┘ │
│ └──────┬──────┘ ▲ │
│ ▼ │ │
│ ┌─────────────┐ │ │
│ │ whoop-client│─── tokens ────┘ │
│ │ (library) │ (no health data is stored) │
│ └─────────────┘ │
└─────────┬───────────────────────────────────────┘
│ Whoop OAuth + API v2, live on every call
▼
┌─────────────────────────────────────────────────┐
│ Whoop API │
└─────────────────────────────────────────────────┘
The server talks to WHOOP through whoop-client, in packages/whoop-client: the same small, typed library anyone can use to build on WHOOP data, with the sign-in and token refresh handled. It isn't published to npm yet.
GET /v2/cycle - Physiological cycles (strain data)GET /v2/recovery - Recovery scoresGET /v2/activity/sleep - Sleep recordsGET /v2/activity/workout - Workout recordsIssues and pull requests are welcome. Every change goes through a pull request, and can merge only once CI passes and the maintainer has reviewed it.
test/, the WHOOP client's in packages/whoop-client/test/. Before opening a pull request, run npm test and npm run typecheck. Every pull request runs both in CI, along with a Docker smoke test, and a CodeQL scan.src/, packages/whoop-client/src/ and the tests, written like the code around it. No new dependency without a reason in the pull request.@yuridivonis/whoop-client, never by a path into packages/whoop-client/src: a second copy of the library would break instanceof checks on its errors. The one exception is the tests' fake WHOOP, imported from packages/whoop-client/test/.Synthetic data only. The tests run against a fake Whoop API that serves made-up records (packages/whoop-client/test/fake-whoop.ts), and future evaluations will too. Never put real Whoop data, yours or anyone else's, in tests, fixtures, issues or pull requests: WHOOP's terms forbid using it to test AI systems, and it's personal health data.
See CHANGELOG.md.
MIT - See LICENSE for details.
Your WHOOP recovery, sleep, strain and workouts in Claude, ChatGPT or other MCP apps. Self-hosted.
{ "mcpServers": { "yuridivonis-whoop-mcp-server": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/yuridivonis/whoop-mcp-server:1.5.1" ], "env": { "WHOOP_CLIENT_ID": "<value>", "WHOOP_CLIENT_SECRET": "<secret>", "WHOOP_REDIRECT_URI": "<value>", "MCP_AUTH_PASSWORD": "<secret>", "PUBLIC_URL": "<value>", "ENCRYPTION_SECRET": "<secret>", "UPDATE_CHECK": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET, WHOOP_REDIRECT_URI, MCP_AUTH_PASSWORD, PUBLIC_URL, ENCRYPTION_SECRET, UPDATE_CHECK
Whoop ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 Your WHOOP recovery, sleep, strain and workouts in Claude, ChatGPT or other MCP apps. Self-hosted.