
jedpattersonn/whoop-mcp
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
MCP server for WHOOP - integrate your fitness and biometric data with Claude and other LLMs
概要
A Model Context Protocol (MCP) server for accessing Whoop fitness data. Integrate your WHOOP biometric data into Claude, LLMs, and other MCP-compatible applications. - - All your daily metrics in one call - - Deep dive into sleep performance and quality - - HRV, RHR, and recovery contributors - - Day strain with heart rate zones and activities - - Biological age and pace of aging metrics The server will run on http://localhost:3000/mcp by default. The --env-file .env flag automatically loads all environment variables from your .env file. The Docker image is based on the official Bun Alpine image. The container includes health checks to monitor the server's status. This server is configured to work with Smithery, a platform for deploying MCP servers. When deployed on Smithery: 1. : Smithery passes your credentials as query parameters to the /mcp endpoint (defined in smithery.
README
以下は原文 README の抜粋です。原文を見る。
Whoop MCP Server
A Model Context Protocol (MCP) server for accessing Whoop fitness data. Integrate your WHOOP biometric data into Claude, LLMs, and other MCP-compatible applications.
Features
- Comprehensive Overview - All your daily metrics in one call
- Sleep Analysis - Deep dive into sleep performance and quality
- Recovery Metrics - HRV, RHR, and recovery contributors
- Strain Tracking - Day strain with heart rate zones and activities
- Healthspan - Biological age and pace of aging metrics
Quick Start
- Clone the repository:
git clone https://github.com/yourusername/whoop-mcp.git
cd whoop-mcp
- Create a
.envfile with your WHOOP credentials:
echo "[email protected]" > .env
echo "WHOOP_PASSWORD=your-password" >> .env
echo "PORT=3000" >> .env
Or set as environment variables:
export WHOOP_EMAIL='[email protected]'
export WHOOP_PASSWORD='your-password'
- Install dependencies:
bun install
- Start the server:
bun run start
Or for development with hot reload:
bun run dev
The server will run on http://localhost:3000/mcp by default.
Docker Deployment
- Create a
.envfile with your credentials:
cp .env.example .env
# Edit .env with your actual credentials
- Build the Docker image:
docker build -t whoop-mcp .
- Run the container:
docker run -d \
--name whoop-mcp \
whoop-mcp
The --env-file .env flag automatically loads all environment variables from your .env file.
- View logs:
docker logs -f whoop-mcp
- Stop the container:
docker stop whoop-mcp
The Docker image is based on the official Bun Alpine image. The container includes health checks to monitor the server’s status.
Smithery Deployment
This server is configured to work with Smithery, a platform for deploying MCP servers. When deployed on Smithery:
-
Configuration via Query Parameters: Smithery passes your credentials as query parameters to the
/mcpendpoint (defined insmithery.yaml):whoopEmail- Your Whoop account emailwhoopPassword- Your Whoop account passwordmcpAuthToken- Optional authentication token
-
Automatic Configuration: The server automatically extracts these from query parameters when running on Smithery, so you don’t need to set environment variables manually.
-
Deploy Button: Use the Railway deploy button above for quick deployment, or follow Smithery’s documentation for other deployment options.
The smithery.yaml file in the repository root defines the configuration schema that Smithery uses to collect your credentials securely.
インストール
docker run -d \設定
{
"mcpServers": {
"whoop": {
"command": "bun",
"args": ["run", "/absolute/path/to/whoop-mcp/index.ts"],
"env": {
"WHOOP_EMAIL": "[email protected]",
"WHOOP_PASSWORD": "your-password"
}
}
}
}