Whoop FAQs

Question 1

How do I secure my Whoop data when using this server?

Accepted Answer

The server supports an optional `MCP_AUTH_TOKEN` for authenticated access, which is highly recommended for network deployments. It stores Whoop authentication tokens in memory only, for 24 hours.

Question 2

What is the Whoop MCP Server?

Accepted Answer

It's a Model Context Protocol (MCP) server designed to integrate your Whoop fitness and biometric data directly with LLMs, Claude, and other AI applications for advanced analysis.

Question 3

What types of Whoop data can I access through this server?

Accepted Answer

You can access a comprehensive overview of daily metrics, detailed sleep analysis, in-depth recovery data (HRV, RHR), strain tracking with heart rate zones, and healthspan metrics like biological age and pace of aging.

Question 4

What are the deployment options for the Whoop MCP Server?

Accepted Answer

You can deploy it locally, using Docker, on cloud platforms like Railway and Smithery, or integrate it directly within Claude Desktop's `mcpServers` configuration for a seamless experience.

Question 5

How does this server enable AI integration with my Whoop data?

Accepted Answer

By providing Whoop data via the Model Context Protocol, it allows AI models like Claude to query, analyze, and generate personalized insights from your fitness and health metrics programmatically.

Whoop

Whoop

주요 기능

사용 사례

주요 기능

사용 사례