whoop

This MCP server exposes a Whoop API interface for model-assisted queries. It provides tools to fetch cycle data, recovery and strain metrics, and user profile/auth status. Specifically, you can query for cycle collections within a date range, retrieve the latest cycle, obtain recovery and strain data across dates, compute average strain over a number of days, and fetch your user profile or authentication status. Dates should be supplied in ISO format (YYYY-MM-DD). Use these endpoints to feed LLMs with timely, structured Whoop data for tasks like trend analysis or activity planning.

To use, ensure your Whoop credentials are configured (email and password). The server authenticates with the Whoop API and then serves the data to client requests (e.g., via the MCP interface or the HTTP API server if you run that variant). You can integrate with Claude or other agents by pointing them at the MCP server, then issuing natural language prompts that translate to the available tool calls such as get_cycle_collection or get_average_strain.

Prerequisites:

• Python 3.12+ installed on your system
• Access to Whoop credentials (email and password)
• Internet access to reach the Whoop API

Installation steps:

1. Clone or download the Whoop MCP server repository to your environment
2. Create a Python virtual environment (optional but recommended):
   • python -m venv venv
   • source venv/bin/activate (Linux/macOS) or venv\Scripts\activate (Windows)
3. Install dependencies:
   • pip install -r requirements.txt
4. Configure credentials in environment variables or a secure config file. Example environment variables (adjust paths as needed):
   • WHOOP_EMAIL=your.email@example.com
   • WHOOP_PASSWORD=your_password
5. Run the MCP server:
   • python /path/to/whoop/src/whoop_server.py (If you prefer the HTTP API server, you can run the provided run_whoop_server.sh script if available in your environment.)
6. Verify the server is running and accessible at the configured port (default is typically 8000 or as defined in the server code).

Tips and common considerations:

• Ensure the Whoop credentials have the necessary permissions and are valid; authentication errors will surface as API errors.
• If you encounter network issues, verify connectivity to the Whoop API and that any required API endpoints are reachable.
• Keep your credentials secure; avoid hard-coding them in shared files. Use environment variables or a secrets manager.
• If you update the server code, re-run the server to apply changes.
• The server expects dates in ISO format (YYYY-MM-DD). Validate inputs to avoid invalid date errors.
• The HTTP API variant (if used) may require different startup scripts or ports; consult the repository’s script documentation for exact commands.