Whoop FAQs

Question 1

How do I set up the Whoop MCP Server?

Accepted Answer

Setup involves creating a Whoop Developer App for client credentials, configuring them in a `.env` file, obtaining access tokens, and then running the server using Docker Compose or locally via `uv run` commands.

Question 2

Can I integrate this with other MCP clients or AI tools?

Accepted Answer

Yes, the server is designed for MCP client configuration. You simply add the server's URL (e.g., `http://localhost:8000/mcp`) to your MCP client's settings (like Claude Desktop or Cursor) to enable data access.

Question 3

What kind of health data can I retrieve using this server?

Accepted Answer

You can access a wide range of data including user profiles, body measurements, physiological cycles (strain, recovery, sleep), detailed sleep sessions, daily recovery scores (HRV, RHR, SpO2, skin temperature), and activity data with heart rate zones and distance.

Question 4

What is the Whoop MCP Server?

Accepted Answer

It's a Model Context Protocol (MCP) server that provides a standardized API to access your Whoop wearable health and fitness data, enabling integration into other applications or AI clients.

Whoop

Key Features

Use Cases

Whoop

Key Features

Use Cases