WHOOP MCP Server
Related Servers
Alternatives to WHOOP MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables language models to query cycles, recovery, strain, and workout data from the Whoop API.-
- AlicenseAqualityBmaintenanceEnables Claude to query personal WHOOP health data including recovery, sleep, strain, workouts, and profile via WHOOP's OAuth 2.0 REST API.66 npmMIT
- AlicenseBqualityDmaintenanceIntegrates with Whoop API v2 to access user profile, sleep, recovery, cycles, and workout data via natural language, with OAuth2 authentication and automatic token refresh.1415 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.1186 npm1MIT
- FlicenseNot gradedqualityBmaintenanceProvides read-only access to Whoop recovery, sleep, strain, workouts, and profile data, allowing users to query their Whoop metrics through natural language in Claude.-
- FlicenseNot gradedqualityCmaintenanceEnables Claude to access and summarize WHOOP health data such as recovery, sleep, strain, workouts, and profile information through natural language queries.-
TDQS
Scored across 4 tools
The tools have some overlap in purpose, particularly between 'get-sleep-by-id' and 'get-sleep-for-cycle', which both retrieve sleep data and could be confused. However, the descriptions clarify the distinction (by ID vs. by cycle), and the other tools target distinct data types (cycles, recovery), so agents can differentiate them with careful reading.
All tool names follow a consistent verb-noun pattern with hyphens ('get-recent-cycles', 'get-recovery-for-cycle', 'get-sleep-by-id', 'get-sleep-for-cycle'), using 'get' as the verb throughout. This predictability makes the set easy to navigate and understand.
With 4 tools, the count is slightly low but reasonable for a focused WHOOP data retrieval server. It covers key physiological aspects (cycles, recovery, sleep), though it might benefit from additional tools for broader health metrics or write operations, but it's not overly thin.
The tool set provides read-only access to core WHOOP data (cycles, recovery, sleep), which is appropriate for a retrieval-focused server. However, there are notable gaps: no tools for creating, updating, or deleting data, and missing operations like listing all sleeps or getting user profile info, which could limit agent workflows in a broader health context.