Case study
Whoop MCP Server
A remote MCP server that securely connects Whoop biometric data to Claude for personalized endurance coaching.
ROLE
Creator
STACK
PROBLEM
You're training for a race with a Whoop on your wrist collecting HRV, sleep, recovery, and strain around the clock. All that data — and the decision of whether to train hard or rest still comes down to a gut feeling.
APPROACH
Connect your Whoop to Claude through the Model Context Protocol. Instead of staring at recovery scores and guessing, you ask Claude what to do today and it answers from your actual HRV, sleep, and strain data.
DEEP DIVE
The Whoop MCP Server is a remote Model Context Protocol server that securely connects Whoop biometric APIs to Claude via OAuth 2.0. It exposes 7 distinct tools Claude can call to pull and analyze recovery, HRV, sleep, and strain data.
On top of the raw metrics, it computes the training-load numbers that actually drive decisions: acute-to-chronic workload ratio (ACWR), HRV trends, and cumulative sleep debt.
The result is a daily conversation instead of a dashboard: Claude reads the day's biometrics, weighs them against training load, and generates personalized Ironman 70.3 coaching recommendations. It's in the loop for my own race build.
HIGHLIGHTS
Remote MCP server securely bridging Whoop biometric APIs and Claude via OAuth 2.0
7 tools for pulling and analyzing recovery, HRV, and sleep metrics
Computes acute-to-chronic workload ratio (ACWR) and cumulative sleep debt
Generates personalized daily Ironman 70.3 coaching recommendations