Developer · Local MCP server
Whoop MCP
Read-only WHOOP v2 data for MCP clients, with local SQLite cache and CSV/JSONL/Parquet exports.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.AshwanthramKL/whoop-mcp- Version
- 0.8.5
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-04-25
- Updated
- 2026-04-25
- Publisher
- AshwanthramKL (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/AshwanthramKL) · how
- Listed under
- SQLite MCP servers
- Repository
- github.com/AshwanthramKL/whoop-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | whoop-mcp | 0.8.5 | stdio |
How to connect Whoop MCP
Whoop MCP runs locally from a Python package published to PyPI: whoop-mcp version 0.8.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx whoop-mcp. It reads these environment variables: WHOOP_CLIENT_ID (required), WHOOP_CLIENT_SECRET (required, secret), WHOOP_REDIRECT_URI, WHOOP_LOG_LEVEL, WHOOP_LOG_FILE and WHOOP_LOG_JSON; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"whoop-mcp": {
"command": "uvx",
"args": [
"whoop-mcp"
],
"env": {
"WHOOP_CLIENT_ID": "<value>",
"WHOOP_CLIENT_SECRET": "<secret>",
"WHOOP_REDIRECT_URI": "<value>",
"WHOOP_LOG_LEVEL": "<value>",
"WHOOP_LOG_FILE": "<value>",
"WHOOP_LOG_JSON": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| WhiteCapData DevOperate a k3s / Kubernetes cluster from your AI agent - safe-by-default MCP server. | Local · stdio |
| Whmcs MCP ServerMCP server for WHMCS - 73 tools, 10 resources, 8 prompts, simulate mode, rate limiting. | Local · stdio |
| Whois MCP ServerDomain registration, availability, DNS records, and IP/ASN resolution via RDAP and DNS-over-HTTPS. | Local · stdio, HTTP |
| WhoisJSONWHOIS, DNS, SSL, and domain availability lookups for AI assistants. | Local · stdio |
| WHOOP MCPSync WHOOP recovery, sleep, strain, and workouts into Postgres and query them from any MCP client. | Local · stdio |
| WhycantRoast any AI agent idea from your IDE: verdict tier, readiness score, top risk, shareable URL. | Remote · HTTPLive check: ✓ handshake |
| WikimintGenerate wiki docs from source code. Supports PowerShell, Python, Go, C#, Java, COBOL. | Remote · HTTPLive check: sign-in required |
| WikimothDeterministic, token-minimal agent memory: multi-hop [[wikilink]] recall with no LLM in the loop. | Local · stdio |