whoop-mcp
Related Servers
Alternatives to whoop-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceProvides read-only access to WHOOP recovery, sleep, HRV, strain, and workout data so assistants like Claude, Codex, and GitHub Copilot can answer questions about personal health trends, baselines, and period comparisons. It runs locally with no hosted relay and never modifies anything in the user's WHOOP account.12 npm-
- FlicenseNot gradedqualityAmaintenanceEnables users to query their own WHOOP recovery, sleep, HRV, strain and workout history in natural language through read-only tools, baselines and period comparisons inside Claude, Codex and GitHub Copilot.12 npm-
- FlicenseNot gradedqualityAmaintenanceEnables read-only, natural-language access to WHOOP recovery, sleep, HRV, strain, workouts, and personal health analytics in Claude, Codex, and GitHub Copilot, with tools for daily status, baselines, trends, period comparisons, and summaries.12 npm-
- FlicenseNot gradedqualityAmaintenanceEnables read-only access to your WHOOP recovery, sleep, HRV, strain, workout and body-measurement data from Claude Desktop, Claude Code, Codex or GitHub Copilot, so you can ask natural-language questions about today's status, personal baselines, trends, period comparisons and sleep debt.12 npm-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to read a user's WHOOP recovery, sleep, HRV, strain, and workout history through a local, read-only server with tools for today's status, personal baselines, sleep debt, trends, and period comparisons. It supports Claude Desktop, Claude Code, Codex, and GitHub Copilot, letting users ask natural-language questions about their health data without exporting it themselves.12 npm-
- AlicenseAqualityCmaintenanceConnects WHOOP fitness tracker data to AI assistants like Claude and ChatGPT, enabling natural language queries about recovery, sleep, strain, and trends.24111 PyPI2MIT
TDQS
Scored across 10 tools
Tools are mostly distinct: get_daily_overview aggregates one day, get_trends aggregates N days, list_* tools retrieve by data type, and get_* tools retrieve by id. There is slight overlap between get_daily_overview and combining list_cycles/list_recoveries/list_sleeps/list_workouts, but descriptions clarify intended use.
Consistent verb_noun pattern throughout: get_profile, get_daily_overview, get_trends, list_cycles, get_cycle, list_recoveries, list_workouts, list_sleeps, get_sleep, get_workout. Singular/plural differences follow entity conventions predictably.
10 tools is well-scoped for a WHOOP data server, covering profile, daily overview, trends, cycles, recoveries, sleeps, and workouts without bloat. Each tool earns its place.
Core WHOOP domain coverage is strong: profile, daily snapshot, trends, cycles, recoveries, sleeps, and workouts are represented. Minor gaps exist, such as no direct get_recovery by id or journal/behavior data, but agents can work around these via get_cycle or list_recoveries.