Whoop MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 141 installs a week from pypi. Last commit 27 Apr 2026.
Read-only WHOOP v2 data for MCP clients, with local SQLite cache and CSV/JSONL/Parquet exports.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
anomList.innerHTML = anoms.map(a => `
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add whoop-mcp -e 'WHOOP_CLIENT_ID=<WHOOP_CLIENT_ID>' -e 'WHOOP_CLIENT_SECRET=<WHOOP_CLIENT_SECRET>' -- uvx whoop-mcp{
"mcpServers": {
"whoop-mcp": {
"command": "uvx",
"args": [
"whoop-mcp"
],
"env": {
"WHOOP_CLIENT_ID": "<WHOOP_CLIENT_ID>",
"WHOOP_CLIENT_SECRET": "<WHOOP_CLIENT_SECRET>"
}
}
}
}[mcp_servers.whoop-mcp]
command = "uvx"
args = ["whoop-mcp"]
env = { WHOOP_CLIENT_ID = "<WHOOP_CLIENT_ID>", WHOOP_CLIENT_SECRET = "<WHOOP_CLIENT_SECRET>" }{
"mcpServers": {
"whoop-mcp": {
"command": "uvx",
"args": [
"whoop-mcp"
],
"env": {
"WHOOP_CLIENT_ID": "<WHOOP_CLIENT_ID>",
"WHOOP_CLIENT_SECRET": "<WHOOP_CLIENT_SECRET>"
}
}
}
}{
"servers": {
"whoop-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"whoop-mcp"
],
"env": {
"WHOOP_CLIENT_ID": "<WHOOP_CLIENT_ID>",
"WHOOP_CLIENT_SECRET": "<WHOOP_CLIENT_SECRET>"
}
}
}
}Put your own values in place of
<WHOOP_CLIENT_ID> (Client ID from your WHOOP developer app (https://developer-dashboard.whoop.com/apps/create)), <WHOOP_CLIENT_SECRET> (Client secret from your WHOOP developer app. Used for OAuth token refresh).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
WHOOP_REDIRECT_URI (OAuth redirect URI. Defaults to http://localhost:8000/callback — only change if you registered a different URI), WHOOP_LOG_LEVEL (Log level (DEBUG / INFO / WARNING / ERROR). Default INFO), WHOOP_LOG_FILE (Path to the rotating log file. Set to empty string to disable file logging. Default ~/.whoop-mcp-server/logs/whoop-mcp.log), WHOOP_LOG_JSON (Structured JSON logs (true) vs human-readable (false). Default true).
Alternatives to Whoop MCP
same job, measured the same wayLocal data runtime for AI agents: query CSV, Excel, Parquet and JSON files with DuckDB SQL.
Local-first bridge: export your own Mi Fitness (Xiaomi) health data to SQLite/JSON/CSV and MCP.
Query a folder of CSV / Parquet / JSON files with SQL — one queryable source, read-only.
Read-only SQL database and plain-text SQL dump schema extraction to compact TOON for MCP clients.
MCP server for the Withings Health API with OAuth, local SQLite cache, and trend analysis.
MCP server for the Google Health API, with a local SQLite cache and trend analysis.
Local retrieval for AI agents: index code, docs, PDFs, data in SQLite; 24 parsers, served via MCP.
Every spreadsheet is a table: Excel, CSV, Parquet and JSON as SQL tables for AI agents.
Whoop MCP — questions
Answers built from our own checks of this server.