A
licenseA
qualityB
maintenanceEnables Claude to query personal WHOOP health data including recovery, sleep, strain, workouts, and profile via WHOOP's OAuth 2.0 REST API.
6
14 npm
MIT
WHOOP MCP Server
by jorgedcb
Related Servers
Alternatives to WHOOP MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables users to query WHOOP health data including recovery, sleep, workouts, and cycles through Claude Desktop using MCP tools.-
- 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 WHOOP data such as recovery, sleep, strain, and workouts through local MCP tools.14 npm-
- FlicenseNot gradedqualityCmaintenanceEnables Claude to access and summarize WHOOP health data such as recovery, sleep, strain, workouts, and profile information through natural language queries.-
- AlicenseNot gradedqualityCmaintenanceConnects Whoop health data to Claude via an MCP server, enabling retrieval of recovery, sleep, strain, and workout metrics through natural language tools.458 npmMIT
TDQS
A3.5/5.0
Scored across 11 tools
Disambiguation4/5
The main list tools (get_recovery, get_sleep, get_cycles, get_workouts) are distinct, but the four by_id/relationship tools (get_sleep_by_id, get_cycle_by_id, get_sleep_for_cycle, get_recovery_for_cycle) have subtle boundaries, particularly the cycle-relationship pair versus the ID lookups, risking misselection.
Naming Consistency4/5
Most tools follow a consistent get_noun pattern, with get_sleep_by_id and get_workout_by_id deviating only by adding an _by_id suffix. This is a minor, readable deviation rather than a true inconsistency.
Tool Count5/5
Eleven tools are well-scoped for WHOOP's core domains (profile, recovery, sleep, cycles, workouts, body), with relationship helpers earning their place. Nothing feels excessive or thin.
Completeness4/5
Read/list coverage is strong across all main resources, including relationship helpers, but the surface is read-only, with no create/update/delete and no explicit pagination or error tools. Minor gaps agents can work around.