wtf is whoop-mcp-server?

whoop-mcp-server connects an AI assistant like Claude to your Whoop fitness tracker data. It is built with the Model Context Protocol, or MCP, which is a way for tools like Claude Code or Claude Desktop to call out to small helper programs and get real information back instead of guessing. This project acts as that helper program for anyone who wears a Whoop band. It talks to the official Whoop API and exposes your health data as a set of tools an assistant can call: your profile, body measurements, daily cycles, recovery scores, sleep stages, and workouts. Each tool returns the same data shapes Whoop's own API provides, so nothing is simplified or hidden, all the detail Whoop tracks, such as heart rate, strain, and sleep stage durations, stays available to the model. There is also a built in tool for calculating your average strain over a chosen number of days. Setting it up takes a few steps. You first register a small app on Whoop's developer site to get a client ID and secret, then install the server itself, using Homebrew, a prebuilt binary, or building from source with Go. After that you run a one time authorization command that opens a browser so you can log into Whoop and grant access. The resulting login token is saved locally and refreshes itself automatically from then on. The final step is registering the server with Claude Code or Claude Desktop by pointing it at the installed program along with your Whoop credentials. Once connected, you can ask plain questions like what is my recovery score today, show my sleep for the past week, or what is my average strain over the last seven days, and the assistant will pull real answers from your Whoop account. The project is released under the MIT license and is written in Go.