프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요
초보자 모드 끄기
색상시스템 설정라이트다크
언어ไทยEnglish中文日本語한국어EspañolDeutsch
☰ 메뉴설정
초보자 모드 끄기
색상시스템 설정라이트다크
언어ไทยEnglish中文日本語한국어EspañolDeutsch

Whoop MCP Server

제작자: 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의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 내 컴퓨터에서 실행
  • 전송 방식: 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

비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.

필요한 것

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

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는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

  • 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월 8일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 GitHub 계정 yuridivonis 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • – 해당 없음

    엔드포인트 응답

    내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요

  • – 해당 없음

    OAuth로 로그인

    내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요

  • … 아직 점검 안 함

    도구 설명에 숨겨진 지시 없음

    내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

클리닉 및 건강 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 1028개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 1028개 중 47%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 1028개 중 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)은 36일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Docker도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Mirobody, FHIR MCP Server, Google Health MCP

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Mirobody

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

제작자: thetahealth성장 중↓ 290/주★ 1.4천어제 업데이트

내 컴퓨터에서 실행✓ thetahealth.ai
설치

FHIR MCP Server

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

제작자: wso2성장 중↓ 823/주★ 13710일 전 업데이트

내 컴퓨터에서 실행
설치

Google Health MCP

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

제작자: davidmosiah성장 중↓ 1천/주★ 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

ToolDescription
get_todayMorning briefing: the latest recovery, last night's sleep with its need and naps, and today's strain, every field, each dated
get_recovery_trendsDaily recovery, HRV, resting heart rate, SpO2, skin temperature and calibrating flag, with averages over the scored days
get_sleep_analysisNightly sleep: times, stages, performance, efficiency, consistency, disturbances, respiratory rate and sleep need; naps; averages
get_strain_historyDaily strain, calories, heart rate and steps, with averages over the completed days
get_workoutsWorkouts with activity, duration, strain, heart rate, calories, every heart-rate zone, distance and elevation; totals
get_auth_urlLink 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:

  1. Click the service card. Its address is at the top of the Deployments tab, whoop-mcp-server-production-xxxx.up.railway.app. Open it.
  2. 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.

  1. 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.
  2. 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.
  1. 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.
  2. 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.
  3. 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:

  1. 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.

  1. 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
  1. In a chat, ask your AI about your recovery. The first answer is a Whoop link (it calls get_auth_url).
  2. Open the link, log in to Whoop, and approve the app, once. You're redirected back, and your AI answers from then on.
  3. 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:

  1. 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.
  2. 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.
  3. 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.
  4. sync_data is gone. If your app still lists it, remove the connector and add it again.
  5. 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:

  1. Update your fork

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

PopNx에게 묻기