WHOOP MCP Server

What is WHOOP MCP Server?

WHOOP MCP Server is an MCP (Machine Conversation Protocol) server implementation that interfaces with the WHOOP API, enabling AI assistants to access and interact with your WHOOP fitness data. It is designed for developers and users who want to integrate their WHOOP health metrics—such as sleep, workouts, recovery, and cycles—into AI-driven workflows.

How to use WHOOP MCP Server?

Install Node.js (v16+), clone the repository, install dependencies, and configure a .env file with your WHOOP API key obtained from the WHOOP Developer Portal. Start the server with npm start (or npm run dev for auto-restart). All endpoints require authentication via an Authorization: Bearer YOUR_WHOOP_API_TOKEN header.

Key features of WHOOP MCP Server

• Access WHOOP user profile data
• Retrieve sleep data and analytics
• Fetch workout information
• Get recovery metrics
• View cycle data
• Server runs on configurable port (default 3000)

Use cases of WHOOP MCP Server

• Integrate WHOOP health data into AI-powered personal health dashboards
• Enable natural-language queries about recent sleep, workouts, or recovery
• Automate analysis of fitness trends over a date range
• Combine WHOOP metrics with other data sources via MCP-based assistants

FAQ from WHOOP MCP Server

What dependencies or runtime are required?

Node.js v16 or higher is required. The server is built with JavaScript and uses npm for package management.

How do I obtain and use authentication?

You need a WHOOP API key from the WHOOP Developer Portal. Requests must include an Authorization: Bearer header with your API token.

What data can I retrieve?

The server supports endpoints for user profile, sleep, workouts, recovery, and cycle data, all filterable by start and end dates.

Where does data live and how is it transmitted?

The server acts as a bridge between the WHOOP API and MCP clients; data is fetched on demand from WHOOP's servers over HTTPS. No local storage is mentioned.

What transport or protocol does the server use?

The server exposes plain HTTP endpoints (GET) on the configured port. It follows the MCP architecture pattern but does not specify advanced transport protocols beyond HTTP.