Whoop MCP Server

Name: Whoop MCP Server
Author: yuridivonis

作者：yuridivonisバージョン 1.5.1i★ –iパソコンで動く

レジストリ名io.github.yuridivonis/whoop-mcp-server

インストール

概要

作者による説明（英語の原文）

Your WHOOP recovery, sleep, strain and workouts in Claude, ChatGPT or other MCP apps. Self-hosted.

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

利用者の声iレビューはまだありませんレビューは今後のステップで、アカウント機能と一緒に始まります
私たちの基本チェックi1項目中1項目に合格公開情報からチェック。コードはまだスキャンしていません
利用状況iとても新しい★ –

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

接続方法: パソコンで動く
トランスポート: Streamable HTTP
カテゴリ: クリニック・健康
入力が必要なもの：WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET, WHOOP_REDIRECT_URI, MCP_AUTH_PASSWORD, PUBLIC_URL, ENCRYPTION_SECRET

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

基本チェック：1項目中1項目に合格
あなたのパソコンで、あなたのユーザーと同じ権限（ファイル、ネットワーク、アプリ）で動きます。
自分で入力するもの： WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET, WHOOP_REDIRECT_URI, MCP_AUTH_PASSWORD, PUBLIC_URL, ENCRYPTION_SECRET, UPDATE_CHECK

「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。

必要なもの

DockerDockerのインストール

どのアプリを使っていますか？

ClaudeClaude CodeCursorVS CodeChatGPT

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます

{
  "mcpServers": {
    "whoop": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "WHOOP_CLIENT_ID",
        "-e",
        "WHOOP_CLIENT_SECRET",
        "-e",
        "WHOOP_REDIRECT_URI",
        "-e",
        "MCP_AUTH_PASSWORD",
        "-e",
        "PUBLIC_URL",
        "-e",
        "ENCRYPTION_SECRET",
        "-e",
        "UPDATE_CHECK",
        "ghcr.io/yuridivonis/whoop-mcp-server:1.5.1"
      ],
      "env": {
        "WHOOP_CLIENT_ID": "your-value",
        "WHOOP_CLIENT_SECRET": "your-value",
        "WHOOP_REDIRECT_URI": "your-value",
        "MCP_AUTH_PASSWORD": "your-value",
        "PUBLIC_URL": "your-value",
        "ENCRYPTION_SECRET": "your-value",
        "UPDATE_CHECK": "your-value"
      }
    }
  }
}

ターミナルでこれを実行します

claude mcp add whoop --env WHOOP_CLIENT_ID=your-value --env WHOOP_CLIENT_SECRET=your-value --env WHOOP_REDIRECT_URI=your-value --env MCP_AUTH_PASSWORD=your-value --env PUBLIC_URL=your-value --env ENCRYPTION_SECRET=your-value --env UPDATE_CHECK=your-value -- docker run -i --rm -e WHOOP_CLIENT_ID -e WHOOP_CLIENT_SECRET -e WHOOP_REDIRECT_URI -e MCP_AUTH_PASSWORD -e PUBLIC_URL -e ENCRYPTION_SECRET -e UPDATE_CHECK ghcr.io/yuridivonis/whoop-mcp-server:1.5.1

動かす前に、空欄の値を入力してください。

Cursorで開く

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます

{
  "mcpServers": {
    "whoop": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "WHOOP_CLIENT_ID",
        "-e",
        "WHOOP_CLIENT_SECRET",
        "-e",
        "WHOOP_REDIRECT_URI",
        "-e",
        "MCP_AUTH_PASSWORD",
        "-e",
        "PUBLIC_URL",
        "-e",
        "ENCRYPTION_SECRET",
        "-e",
        "UPDATE_CHECK",
        "ghcr.io/yuridivonis/whoop-mcp-server:1.5.1"
      ],
      "env": {
        "WHOOP_CLIENT_ID": "your-value",
        "WHOOP_CLIENT_SECRET": "your-value",
        "WHOOP_REDIRECT_URI": "your-value",
        "MCP_AUTH_PASSWORD": "your-value",
        "PUBLIC_URL": "your-value",
        "ENCRYPTION_SECRET": "your-value",
        "UPDATE_CHECK": "your-value"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

{
  "servers": {
    "whoop": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "WHOOP_CLIENT_ID",
        "-e",
        "WHOOP_CLIENT_SECRET",
        "-e",
        "WHOOP_REDIRECT_URI",
        "-e",
        "MCP_AUTH_PASSWORD",
        "-e",
        "PUBLIC_URL",
        "-e",
        "ENCRYPTION_SECRET",
        "-e",
        "UPDATE_CHECK",
        "ghcr.io/yuridivonis/whoop-mcp-server:1.5.1"
      ],
      "env": {
        "WHOOP_CLIENT_ID": "your-value",
        "WHOOP_CLIENT_SECRET": "your-value",
        "WHOOP_REDIRECT_URI": "your-value",
        "MCP_AUTH_PASSWORD": "your-value",
        "PUBLIC_URL": "your-value",
        "ENCRYPTION_SECRET": "your-value",
        "UPDATE_CHECK": "your-value"
      }
    }
  }
}

これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

自分で入力する値

WHOOP_CLIENT_ID 必須 env
Client ID of your WHOOP developer app.
WHOOP_CLIENT_SECRET 秘密必須 env
Client secret of your WHOOP developer app.
WHOOP_REDIRECT_URI 必須 env
The server's /callback address, also added to your WHOOP app. WHOOP needs an https address, such as a tunnel to this computer.
MCP_AUTH_PASSWORD 秘密必須 env
Password for the sign-in page that protects /mcp, at least 16 characters.
PUBLIC_URL 必須 env
The address MCP clients use to reach the server. Keep the default when running it on this computer.
ENCRYPTION_SECRET 秘密 env
Key for encrypting the stored WHOOP tokens. Defaults to WHOOP_CLIENT_SECRET.
UPDATE_CHECK env
Once a day, ask GitHub for the latest release number and mention a newer version in get_today. Sends nothing about you. Set to false to turn it off.

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月9日にチェック

✓ 合格
作者とリポジトリが一致
レジストリ名は、リポジトリを所有するGitHubアカウント yuridivonis で確認済みです
… 未チェック
今もメンテナンスされている
このリポジトリはまだGitHubから読み取っていません
… 未チェック
ライセンスがある
このリポジトリはまだGitHubから読み取っていません
– 対象外
エンドポイントが応答する
これはパソコンで動くため、インターネット上のエンドポイントはありません
– 対象外
OAuthでサインイン
パソコンで動き、代わりにローカルの設定を使います
… 未チェック
ツールの説明に隠れた指示がない
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです

クリニック・健康のほかのサーバーとの比較i

このカテゴリのほかの1034件のうち0%よりスターが多い
このカテゴリのほかの1034件のうち46%より最近レジストリに公開
基本チェックの結果が、このカテゴリのほかの1034件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

Whoop MCP Serverは安全ですか？

当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか？

入力が必要なもの：WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET, WHOOP_REDIRECT_URI, MCP_AUTH_PASSWORD, PUBLIC_URL, ENCRYPTION_SECRET

パソコンで動きますか、それともクラウドですか？

あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません（サーバー自体がオンラインサービスを呼び出す場合を除きます）。

今もメンテナンスされていますか？

GitHubリポジトリの最終更新は–、最新バージョン（1.5.1）がレジストリに届いたのは37 日前です。

どのアプリで使えますか？

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにDockerも必要です。

代わりに使えるものは？

同じカテゴリには：Mirobody, FHIR MCP Server, Google Health MCP

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方：↓ 週あたりのダウンロードi★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

Mirobody

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

作者：thetahealth成長中↓ 290/週★ 1408一昨日更新

パソコンで動く✓ thetahealth.ai

インストール

FHIR MCP Server

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

作者：wso2成長中↓ 823/週★ 13711 日前更新

パソコンで動く

インストール

Google Health MCP

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

作者：davidmosiah成長中↓ 1024/週★ 794 か月前更新

パソコンで動く

インストール

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

Whoop MCP Server

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.

Two ways in

Talk to your data. Deploy the server, connect it to your AI, and ask. Start with Setup, then Add to your AI, which also lists the apps tested so far.
Build with it. The WHOOP client inside this server (typed, tested, and careful with WHOOP's single-use refresh tokens) is being split out as a library for your own code. It isn't published yet: watch this repository's releases to hear when it is.

Built on the Whoop Developer API v2, and the Model Context Protocol (MCP), the open standard AI apps use to call tools like these.

Features

Everything Whoop sends, nothing hidden: every physiological field of Whoop's API, with a date on every record, zeros shown as zeros and unscored days marked as such
Recovery: daily recovery score, HRV, resting heart rate, SpO2, skin temperature, and whether Whoop is still calibrating
Sleep: bed and wake times, time asleep and in bed, awake and no-data time, light/deep/REM stages, sleep cycles, disturbances, performance, efficiency, consistency, respiratory rate, the sleep needed before each night (baseline, debt, strain, nap credit), and naps
Strain: daily strain score, calories, average and max heart rate, and steps
Workouts: activity, local start time, duration, strain, heart rate, calories, time in every heart-rate zone, distance, elevation gain and altitude change, and the share of heart-rate data recorded
Live data: every answer is fetched from Whoop when you ask, so it's always current. The server stores only its sign-ins and your encrypted Whoop tokens, never your health data
Private by default: each app signs in with a password you choose (OAuth 2.1), and only after you tick a box allowing it, so nobody else can read your data
Your choice of AI: tested live with Claude and ChatGPT; other apps that sign in with OAuth should work the same way (see compatibility)

MCP Tools

Tool	Description
`get_today`	Morning briefing: the latest recovery, last night's sleep with its need and naps, and today's strain, every field, each dated
`get_recovery_trends`	Daily recovery, HRV, resting heart rate, SpO2, skin temperature and calibrating flag, with averages over the scored days
`get_sleep_analysis`	Nightly sleep: times, stages, performance, efficiency, consistency, disturbances, respiratory rate and sleep need; naps; averages
`get_strain_history`	Daily strain, calories, heart rate and steps, with averages over the completed days
`get_workouts`	Workouts with activity, duration, strain, heart rate, calories, every heart-rate zone, distance and elevation; totals
`get_auth_url`	Link to connect your Whoop account (works once, expires in 10 minutes)

Setup

Fastest: Deploy on Railway

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:

Click the service card. Its address is at the top of the Deployments tab, whoop-mcp-server-production-xxxx.up.railway.app. Open it.
The page walks you through the rest: create a Whoop developer app (it shows every field), paste the app's two keys over the placeholders in the service's variables, add the address it shows to Claude or ChatGPT, and approve Whoop once on your first question.

To set it up by hand instead, or elsewhere, read on.

1. Deploy

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.

In a Railway project, click New, choose Docker Image, and enter 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.
Add environment variables:

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.

Add a volume mounted at /data. It holds the sign-ins and your encrypted Whoop tokens; without it, every redeploy signs your apps out and disconnects Whoop.
Turn on updates: in the service's Settings, under Source, choose Configure Auto Updates and a maintenance window (for example Night). The :1 tag moves with every 1.x release, and Railway then redeploys the service; on the Pro plan it backs up the volume first.
Deploy, then open 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.

2. Create a Whoop Developer App

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:

Name: anything. You see it when you approve the app.
Logo: skip it.
Contacts: your email. Only Whoop sees it.
Privacy Policy: this project's PRIVACY.md, 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.
Redirect URLs: your server's callback, https://your-app.up.railway.app/callback, exactly as the set-up page shows it.
Scopes: 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.
Webhooks: skip 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.

3. Connect your AI

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.

4. Connect your Whoop account

In a chat, ask your AI about your recovery. The first answer is a Whoop link (it calls get_auth_url).
Open the link, log in to Whoop, and approve the app, once. You're redirected back, and your AI answers from then on.
Ask away: "How did I sleep last night?"

Upgrading to 1.3.0

1.3.0 stops keeping a copy of your Whoop data, and asks you before each app receives it. To upgrade:

Get the new version: with the image, Railway's auto updates do it for you, or switch the Service Source to the :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.
On its first start, the server deletes the recovery, sleep, strain and workout data earlier versions stored, and rewrites the database file so none of it is left on disk. Your Whoop connection is kept. The log says Deleted the WHOOP data stored by an earlier version.
Every app is signed out once. The next time you use one, it opens the sign-in page: enter your password and tick the box allowing it to read your Whoop data.
sync_data is gone. If your app still lists it, remove the connector and add it again.
If your host keeps backups or snapshots of the volume, delete the ones from before the upgrade. They still hold the old copy.

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.

Upgrading from 1.0.0

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:

Update your fork

冒頭だけを表示しています。続きはリポジトリで読めます

Whoop MCP Server

概要

PopNx MCPの3つの柱

できること

インストール

インストールの前に

自分で入力する値

できること

基本チェックi

作者とリポジトリが一致

今もメンテナンスされている

ライセンスがある

エンドポイントが応答する

OAuthでサインイン

ツールの説明に隠れた指示がない

クリニック・健康のほかのサーバーとの比較i

よくある質問

代わりの候補

Mirobody

FHIR MCP Server

Google Health MCP

作者のREADME

Whoop MCP Server

Two ways in

Features

MCP Tools

Setup

Fastest: Deploy on Railway

1. Deploy

2. Create a Whoop Developer App

3. Connect your AI

4. Connect your Whoop account

Upgrading to 1.3.0

Upgrading from 1.0.0