mcp-server-whoop
Related Servers
Alternatives to mcp-server-whoop
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA local MCP server providing read-only access to WHOOP fitness data via direct OAuth, with a local SQLite cache for offline queries.96 PyPIMIT
- FlicenseBqualityCmaintenanceLocal MCP server for the WHOOP API v2 that provides tools to access recovery, sleep, strain, and workout data, with local history and JSON export.9-
- AlicenseAqualityDmaintenanceMCP server providing read access to WHOOP biometric data including recovery, sleep, strain, and workouts.161MIT
- AlicenseNot gradedqualityCmaintenanceMCP server providing full read/write access to Whoop wearable data, including recovery, sleep, workouts, journal, and more, via Whoop's private iOS API.20 npmMIT
- AlicenseAqualityBmaintenancePrivacy-first, unofficial WHOOP MCP server for AI health, sleep, recovery, and performance agents.30138 npm13MIT
- AlicenseAqualityBmaintenanceA read-only MCP server for the WHOOP API v2 that lets you query and analyze your own recovery, sleep, strain, cycles, and workout data. Note: currently a pre-alpha scaffold with stubbed internals.161MIT
TDQS
Scored across 4 tools
Each tool targets a distinct WHOOP data domain: overall overview, sleep history, cycle strain history, and workout history. There is no overlap in purpose, making it easy for an agent to select the correct tool.
All tool names follow a consistent pattern: 'whoop_' followed by a descriptive noun phrase (e.g., latest_overview, sleep_history). The naming is uniform and predictable.
With 4 tools, the server covers the core WHOOP data categories (overview, sleep, cycle strain, workouts) without unnecessary bloat. The count is well-scoped for a focused integration.
The tool set covers the most commonly accessed WHOOP data types. However, it lacks dedicated tools for specific metrics like HRV or recovery details, though the overview tool may subsume some of these. Minor gap for a comprehensive read-only surface.