Read-only WHOOP v2 data for MCP clients, with local SQLite cache and CSV/JSONL/Parquet exports.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
uvx whoop-mcp{
"WHOOP_CLIENT_ID": "YOUR_VALUE_HERE",
"WHOOP_CLIENT_SECRET": "YOUR_SECRET_VALUE",
"WHOOP_REDIRECT_URI": "http://localhost:8000/callback",
"WHOOP_LOG_LEVEL": "INFO",
"WHOOP_LOG_FILE": "YOUR_VALUE_HERE",
"WHOOP_LOG_JSON": "true"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-ashwanthramkl-whoop-mcp": {
"command": "uvx",
"args": [
"whoop-mcp"
],
"env": {
"WHOOP_CLIENT_ID": "YOUR_VALUE_HERE",
"WHOOP_CLIENT_SECRET": "YOUR_SECRET_VALUE",
"WHOOP_REDIRECT_URI": "http://localhost:8000/callback",
"WHOOP_LOG_LEVEL": "INFO",
"WHOOP_LOG_FILE": "YOUR_VALUE_HERE",
"WHOOP_LOG_JSON": "true"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
whoop-mcp is an MCP server for Read-only WHOOP v2 data for MCP clients, with local SQLite cache and CSV/JSONL/Parquet exports.. It supports STDIO transport.
Use the generated config in Install. This server runs with uvx whoop-mcp; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for uvx whoop-mcp. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for uvx whoop-mcp. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for uvx whoop-mcp. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for uvx whoop-mcp. Add required environment variables before starting Cursor or VS Code.
whoop-mcp uses STDIO transport. Use the package or command config in Install.
whoop-mcp inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
whoop-mcp is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
whoop-mcpstdio | pypi | 0.8.5 | Env: WHOOP_CLIENT_ID required Env: WHOOP_CLIENT_SECRET required secret Env: WHOOP_REDIRECT_URI Env: WHOOP_LOG_LEVEL Env: WHOOP_LOG_FILE Env: WHOOP_LOG_JSON |