Whoop-mcp Server

Whoop-mcp is an MCP integration. Full read + write access to your Whoop fitness data via the private iOS API. 48 tools.

Packages and local setup

The published npm package is @briangaoo/whoop-mcp, version 1.3.0. Its declared MCP transport is stdio.

The package declares WHOOP_IOS_BEARER_TOKEN (required): Whoop Cognito access token. Obtain via whoop-mcp auth from the repo, which prompts for your Whoop email + password + SMS MFA code, then writes both tokens to a local .env. Auto-refreshes every ~24h.; WHOOP_COGNITO_REFRESH_TOKEN (required): Whoop Cognito refresh token (~30 day lifetime). Obtained alongside the bearer token from whoop-mcp auth. When this expires, run whoop-mcp auth to get a fresh pair.; WHOOP_EMAIL (required): Your Whoop account email. Used only by whoop-mcp auth — the running server reads tokens, not credentials.; WHOOP_USER_ID: Your numeric Whoop user ID. Optional — used by whoop_profile and whoop_leaderboard. Avoids one redundant bootstrap call per session if set.; WHOOP_TIMEZONE: IANA timezone (e.g., America/Los_Angeles) for response timestamps. Optional — if unset, the server auto-detects from your Whoop profile's timezone_offset field (refreshed hourly)..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 1.3.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.