Whoop Mcp
Let Claude or Cursor query your WHOOP recovery, sleep, and strain history with local caching and file exports for personal performance reviews.
Overview
WHOOP MCP is a MCP server for the Grow phase that exposes read-only WHOOP v2 metrics to agents with SQLite caching and multi-format exports.
What is this MCP server?
- Read-only WHOOP Developer API v2 access from MCP clients over stdio
- Local SQLite cache to cut repeat API calls during agent sessions
- Export cached data to CSV, JSONL, and Parquet for notebooks or dashboards
- OAuth via WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET, and configurable redirect URI
- Installable with uvx from PyPI (whoop-mcp package v0.8.5)
- Server version 0.8.5 on PyPI with stdio transport
- Read-only WHOOP Developer API v2 integration
- Three export formats: CSV, JSONL, and Parquet
What problem does it solve?
Solo builders who wear WHOOP still copy stats manually when they want an AI to reason over weeks of sleep, recovery, and training data.
Who is it for?
Developers who already use WHOOP and want MCP-native Q&A plus offline-friendly exports without building a custom OAuth client.
Skip if: Teams that need write access to WHOOP, clinical workflows, or a hosted dashboard without running stdio MCP locally.
What do I get? / Deliverables
Your agent can pull cached WHOOP history on demand and drop structured exports you can chart or join with other life logs.
- Agent-accessible read-only WHOOP metric queries
- Local SQLite cache of API responses
- CSV, JSONL, or Parquet export files from cached data
Recommended MCP Servers
Journey fit
Fitness and recovery metrics sit in the grow phase when solo builders treat their own data like a product metric stream. Analytics is the right shelf because the server is optimized for reading, caching, and exporting time-series health data rather than changing WHOOP settings.
How it compares
MCP health-data bridge with local cache, not a WHOOP mobile app replacement or generic fitness skill.
Common Questions / FAQ
Who is WHOOP MCP for?
It is for developers and solo builders who use WHOOP and want Claude Code, Cursor, or other MCP clients to read their v2 data safely in read-only mode.
When should I use WHOOP MCP?
Use it when you are reviewing recovery trends, preparing exports for analysis, or asking an agent to summarize sleep and strain over a date range.
How do I add WHOOP MCP to my agent?
Create a WHOOP developer app, set WHOOP_CLIENT_ID and WHOOP_CLIENT_SECRET, run the server via uvx whoop-mcp with stdio transport, and register it in your MCP client config.