Skip to main content
Glama
nMoreau39122

whoop-ai-mcp

by nMoreau39122
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

whoop-ai-mcp is a read-only WHOOP MCP server for Claude Desktop, Claude Code, Codex and GitHub Copilot. Ask about your recovery, compare weeks of sleep, or check today against your own baseline, without exporting the data yourself.

npx -y whoop-ai-mcp@latest setup --client=claude-desktop

Ask your WHOOP data anything

Ask

You get

"How am I doing today?"

Recovery, primary sleep, strain and your latest workout, with gaps flagged where data is missing

"Is my HRV unusual for me?"

Your personal baseline: distribution, percentiles and how many days it's based on

"How did my sleep change this month?"

Trends, period-to-period comparisons, sleep debt and consistency

"Give me my weekly health review."

Recovery, sleep and training in one summary

Statistics describe your recorded history. They aren't medical diagnoses or predictions.

Related MCP server: whoop-mcp

Quickstart

You need: Node.js 20 or later, an active WHOOP membership, and a WHOOP Developer App with the redirect URL http://localhost:3000/callback.

  1. Set up. Run the command for your assistant and enter your developer app's client ID and secret when asked.

    Assistant

    Command

    Claude Desktop

    npx -y whoop-ai-mcp@latest setup --client=claude-desktop

    Claude Code

    npx -y whoop-ai-mcp@latest setup --client=claude-code

    Codex

    npx -y whoop-ai-mcp@latest setup --client=codex

    GitHub Copilot

    npx -y whoop-ai-mcp@latest setup --client=copilot

    For Claude Code, Codex and Copilot, run the registration command that setup prints. Nothing is installed globally, and optional usage telemetry defaults to No.

  2. Authorize. Fully quit and reopen your assistant. The first time the server starts, WHOOP opens in your browser so you can approve access.

  3. Ask. Try "Summarize my sleep and recovery this week."

Need manual configuration, environment variables or a remote deployment? See the full setup guide.

The Rust implementation supports the same four assistants without a Node.js runtime. It needs Rust 1.88 or later:

cargo install whoop-mcp
whoop-mcp setup --client=claude-desktop

How it works

  • Read-only. The server has no tools that create, change or delete anything in your WHOOP account.

  • Local by default. The server runs on your machine. No hosted relay is involved.

  • Your assistant sees the results. Health data reaches the assistant provider you use, the same as anything else you share in that chat.

  • Aggregate mode limits the server to five summary tools and hides per-record data. It reduces what's shared, but it isn't anonymization.

  • Telemetry is off unless you opt in. It never includes health data or chat text.

Details: data handling and telemetry controls.

What's included

In standard mode, the server provides 16 read-only tools, 4 resources and 5 prompt templates. Support for resources, prompts and remote connections depends on your assistant.

Group

Tools

Today and baselines

get_today, get_baselines, get_sleep_debt

Trends and reviews

get_weekly_summary, get_trend, compare_periods, get_calendar

Records

get_recovery_collection, get_sleep_collection, get_workout_collection, get_cycle_collection, get_sleep_by_id, get_workout_by_id, get_cycle_by_id

Profile

get_profile, get_body_measurement

Prompt templates: weekly_health_review, sleep_analysis, recovery_trend, workout_recap, health_check

Parameters, date expressions, resources and caching are in the tool reference.

Documentation

Guide

What's in it

Installation

Assistants, manual configuration, environment variables and WHOOP authorization

Tool reference

Every tool and its parameters, date expressions, resources, prompts and caching

Privacy

Structured results, aggregate mode and what your assistant provider receives

Telemetry

Consent, opting out, what's collected and how long it's kept

Troubleshooting

Local diagnostics, common errors and MCP Inspector

Deployment

Docker, cloud hosting and remote connector OAuth

Development

Tests, project structure and release workflow

Background

Ecosystem research and the video walkthrough

What changed recently? See the changelog or the latest release.

Feedback and contributing

Something not working, or a question you wish you could ask? Use the buttons above. Each opens a short form that asks for the details needed to help. Issues are public, so never include credentials or health records; security problems go through the security policy instead.

Want to contribute code? Read the contributing guide. Everyone taking part follows the Code of Conduct.

If whoop-ai-mcp is useful to you, a GitHub star helps other people find it, and you can buy me a coffee to support development.

License

MIT. This is an unofficial project and isn't affiliated with WHOOP. A WHOOP membership and API access are separate from this package.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityActive
ResponsivenessResponsive

Resources

Related MCP Connectors

Related MCP Servers

  • WHOOP MCP Server

    izqui
    A
    license
    A
    quality
    D
    maintenance
    Enables LLMs to retrieve and analyze sleep, recovery, and physiological cycle data from the WHOOP API. It provides tools for accessing detailed metrics such as strain, HRV, and readiness scores through secure OAuth 2.0 authentication.
    4
    12 npm
    1
    MIT

  • WHOOP MCP Server

    jorgedcb
    A
    license
    A
    quality
    B
    maintenance
    Enables Claude, Cursor, or any MCP client to query your own recovery scores, sleep, strain cycles, workouts, profile, and body measurements through every WHOOP API v2 read endpoint. Tools return records exactly as WHOOP sends them, with paging and date-range filtering, and refresh tokens automatically after a one-time login.
    11
    6 npm
    1
    MIT