WHOOP MCP Server
by caxtmann
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to listen on. Defaults to 8080. | 8080 |
| DATABASE_URL | Yes | Postgres connection string. | |
| ENCRYPTION_KEY | Yes | 32-byte hex key used to encrypt stored WHOOP tokens at rest. Generate with `openssl rand -hex 32`. | |
| SESSION_SECRET | Yes | Secret used to sign the dashboard's session cookie. Generate with `openssl rand -hex 32`. | |
| PUBLIC_BASE_URL | Yes | The publicly reachable base URL of this deployment, e.g. `https://your-app.example.com` (no trailing slash). Used to build OAuth redirect/callback URLs. | |
| WHOOP_CLIENT_ID | Yes | Client ID from your WHOOP developer app. | |
| WHOOP_CLIENT_SECRET | Yes | Client secret from your WHOOP developer app. |
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/caxtmann/whoop-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server