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.
2
24
312 npm
490
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.3879 npm569MIT
- 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.42MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceConnects Whoop health data to Claude via an MCP server, enabling retrieval of recovery, sleep, strain, and workout metrics through natural language tools.196 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to access and analyze Whoop recovery, sleep, strain, and workout data through MCP tools, including trends and manual syncs.196 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables users to query WHOOP health data including recovery, sleep, workouts, and cycles through Claude Desktop using MCP tools.-
- FlicenseNot gradedqualityDmaintenanceEnables Claude to access WHOOP data such as recovery, sleep, strain, and workouts through local MCP tools.13 npm-
- 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.13 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.9/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct WHOOP metric domain (recovery trends, today's snapshot, auth, sleep, strain, individual workouts), and the descriptions explicitly cross-reference each other with guidance on when to prefer one over another. There is essentially no risk of misselection.
Naming Consistency5/5
All tools follow a uniform get_ verb + noun pattern in snake_case (get_recovery_trends, get_today, get_auth_url, 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 health data server, with one tool per major WHOOP metric plus an auth helper. Nothing feels redundant or missing at the count level.
Completeness4/5
The surface covers recovery, sleep, strain, workouts, a daily snapshot, and authorization, which matches the domain well. Minor gaps exist (e.g., no user profile/body metrics or journal data), but these are edge concerns an agent could work around.
Maintenance
ActivityMaintained
ResponsivenessNo issues