Whoop Mcp
Give your agent full read-and-write Whoop API access through 48 MCP tools backed by private iOS API tokens.
Overview
Whoop MCP is a Build-phase MCP server with 48 tools for full read and write access to your Whoop data via Cognito tokens over stdio.
What is this MCP server?
- 48 tools with full read and write access to Whoop fitness data
- npm @briangaoo/whoop-mcp v1.3.0 over stdio transport
- `whoop-mcp auth` obtains bearer and refresh tokens after email, password, and SMS MFA
- Running server uses tokens only—credentials are not read at runtime
- Same Cognito refresh and ~24h bearer refresh behavior as Totem-family auth
- 48 MCP tools for Whoop data
- Package version 1.3.0 as @briangaoo/whoop-mcp
- Read and write access stated in registry description
Community signal: 66 GitHub stars.
What problem does it solve?
You cannot let an agent adjust or query Whoop metrics programmatically while you code unless you build brittle scrapers or manual exports.
Who is it for?
Whoop users who want write-capable agent automation (logging, updates) from Claude Code, Cursor, or Codex.
Skip if: Builders without Whoop hardware, those avoiding unofficial APIs, or teams needing enterprise HIPAA-grade health pipelines.
What do I get? / Deliverables
Registering whoop-mcp gives your agent authenticated tool calls against your Whoop account after a one-time MFA auth CLI.
- Agent-callable Whoop MCP tool surface with read and write operations
- Locally managed Cognito token pair for the private API
- 48-tool integration documented in server metadata
Recommended MCP Servers
Journey fit
Whoop MCP is installed when you extend your agent toolchain with personal telemetry, which happens in the build phase. This server is a direct third-party integration (Whoop Cognito) rather than app frontend or backend product code.
How it compares
Dedicated Whoop-named MCP with write access, not the broader Totem wearable umbrella brand—tooling overlap is high.
Common Questions / FAQ
Who is io.github.briangaoo/whoop-mcp for?
Individual developers with Whoop accounts who want MCP-native read and write fitness tooling inside AI coding assistants.
When should I use io.github.briangaoo/whoop-mcp?
When your agent workflows need to mutate or fetch Whoop data during build-side automation rather than copying numbers by hand.
How do I add io.github.briangaoo/whoop-mcp to my agent?
Add @briangaoo/whoop-mcp as a stdio MCP server, run `whoop-mcp auth`, and inject the required WHOOP_* environment variables into your host config.