WHOOP MCP by usefulapi

Each tool is clearly differentiated by resource and operation: retrieval of singular items (whoop_get_cycle, whoop_get_sleep, etc.) versus listing collections (whoop_list_cycles, whoop_list_sleep, etc.), and the get_cycle_recovery tool is specifically about recovery for a given cycle. There is no overlap that would confuse an agent.

All tools follow a consistent prefix (whoop_?) and verb_noun pattern (whoop_get_*, whoop_list_*, whoop_body_measurement, whoop_get_profile). The naming is predictable and easy to parse.

With 10 tools covering core WHOOP endpoints (cycles, recoveries, sleep, workouts, profile, body measurement), the count is well-scoped: enough to cover key data domains without redundancy or bloat.

The server covers read operations for all major WHOOP data types (cycles, recoveries, sleep, workouts, profile, body measurement), with both list and get for most. However, it lacks write operations (e.g., creating or updating workouts) and some related resources like sleep stages or detailed workout analysis, but for a read-only MCP this is minor.