A
licenseA
qualityF
maintenanceA TypeScript server that acts as a bridge to the Strava API, enabling LLMs to access users' activities, routes, segments, and athlete data through natural language interaction.
24
631 npm
500
MIT
Whoop MCP Server
by yuridivonis
Related Servers
Alternatives to Whoop MCP Server
- AlicenseAqualityAmaintenanceAn MCP server that allows users to query and analyze their Apple Health data using SQL and natural language, utilizing DuckDB for fast and efficient health data analysis.354 npm576MIT
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol (MCP) server that brings your Withings health data into Claude, allowing natural conversation access to sleep patterns, body measurements, workouts, heart data, and more.45MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceConnects Whoop health data to Claude via an MCP server, enabling retrieval of recovery, sleep, strain, and workout metrics through natural language tools.48 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to access and analyze Whoop recovery, sleep, strain, and workout data through MCP tools, including trends and manual syncs.48 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables users to query WHOOP health data including recovery, sleep, workouts, and cycles through Claude Desktop using MCP tools.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude to access WHOOP data such as recovery, sleep, strain, and workouts through local MCP tools.7 npmISC
- AlicenseNot gradedqualityDmaintenanceIntegrates WHOOP biometric data into Claude and other MCP-compatible applications, providing access to sleep analysis, recovery metrics, strain tracking, and biological age data through natural language queries.7 npm13MIT
- FlicenseNot gradedqualityCmaintenanceEnables Claude to access and summarize WHOOP health data such as recovery, sleep, strain, workouts, and profile information through natural language queries.-
TDQS
A4.8/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct data slice (today snapshot, recovery, sleep, strain, workouts, auth), and the descriptions explicitly cross-reference each other to steer selection (e.g. 'for today alone use get_today; for the sleep behind the numbers use get_sleep_analysis'). Boundaries between the single-day and trend tools are clearly spelled out, so misselection is unlikely.
Naming Consistency5/5
All six tools use a uniform snake_case get_* pattern (get_auth_url, get_today, get_recovery_trends, get_sleep_analysis, get_strain_history, get_workouts). The convention is predictable and readable throughout.
Tool Count5/5
Six tools is well-scoped for a read-only WHOOP data server: one auth helper, one current-status snapshot, and four trend/history tools. Each tool earns its place with no redundancy or filler.
Completeness4/5
The surface covers the core lifecycle of WHOOP data: auth, today's recovery/sleep/strain, and trend views for recovery, sleep, strain, and workouts. Minor gaps exist (e.g. no user profile/basic account info and no auth-revocation tool), but agents can work around these.
Maintenance
ActivityMaintained
ResponsivenessNo issues