whoop-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP transport (default 3000, use 7860 on HuggingFace Spaces). | 3000 |
| PUBLIC_URL | No | Public origin URL of the server, used as OAuth issuer. Required if AUTH_PASSWORD is set. | |
| WHOOP_EMAIL | Yes | Your Whoop login email | |
| AUTH_PASSWORD | No | Password for OAuth connector flow (optional, enables OAuth for claude.ai web/mobile). | |
| MCP_TRANSPORT | No | Transport for MCP server: stdio (local) or http (remote). | stdio |
| WHOOP_USER_ID | No | Your Whoop user ID — used by whoop_profile and whoop_leaderboard. Avoids one bootstrap call per session. | |
| MCP_AUTH_TOKEN | No | Bearer token for HTTP transport, also used as JWT signing secret. Required if MCP_TRANSPORT=http. | |
| WHOOP_PASSWORD | No | Your Whoop login password (bootstrap only, used only during initial login and wiped from .env after) | |
| WHOOP_TIMEZONE | No | IANA timezone (e.g., America/Los_Angeles). If unset, auto-detected from your Whoop profile and refreshed hourly. Set explicitly to override. | |
| WHOOP_TOKEN_STORE | No | Where to persist refreshed tokens: 'envfile' (default) or 'memory' (for read-only filesystems; re-bootstrap every ~30 days). | envfile |
| WHOOP_INSTALLATION_ID | No | The per-install device identifier sent as x-whoop-installation-identifier. Generated once and written to .env on first run — don't set it by hand. | |
| WHOOP_IOS_BEARER_TOKEN | Yes | Cognito access token (24h, auto-refreshed) | |
| WHOOP_COGNITO_REFRESH_TOKEN | Yes | Cognito refresh token (~30d) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rishi-mittal-web/whoop-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server