NestDaddy

Whoop Mcp

io.github.souravpn/whoop-mcp · v1.0.2

MCP server for WHOOP — gives Claude access to your recovery, sleep, strain, and workout data

Connect Runs on your machine

Terminal
claude mcp add whoop-mcp -e WHOOP_CLIENT_ID=<WHOOP_CLIENT_ID> -e WHOOP_CLIENT_SECRET=<WHOOP_CLIENT_SECRET> -- npx -y @souravpn/[email protected]
claude_desktop_config.json
{
  "mcpServers": {
    "whoop-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@souravpn/[email protected]"
      ],
      "env": {
        "WHOOP_CLIENT_ID": "<WHOOP_CLIENT_ID>",
        "WHOOP_CLIENT_SECRET": "<WHOOP_CLIENT_SECRET>"
      }
    }
  }
}
~/.cursor/mcp.json
{
  "mcpServers": {
    "whoop-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@souravpn/[email protected]"
      ],
      "env": {
        "WHOOP_CLIENT_ID": "<WHOOP_CLIENT_ID>",
        "WHOOP_CLIENT_SECRET": "<WHOOP_CLIENT_SECRET>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "whoop-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@souravpn/[email protected]"
      ],
      "env": {
        "WHOOP_CLIENT_ID": "<WHOOP_CLIENT_ID>",
        "WHOOP_CLIENT_SECRET": "<WHOOP_CLIENT_SECRET>"
      }
    }
  }
}

Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.

Tools

This server runs locally, so its tools are listed by your MCP client once it starts.

Environment variables

NameDescription
WHOOP_CLIENT_ID
Required
OAuth2 Client ID from your WHOOP developer app at developer-dashboard.whoop.com
WHOOP_CLIENT_SECRET
Required, secret
OAuth2 Client Secret from your WHOOP developer app. Run whoop-mcp-auth-setup once to complete OAuth flow.

Details

Package@souravpn/[email protected] (NPM, stdio)
First published27 May 2026
Last updated27 May 2026
Registry nameio.github.souravpn/whoop-mcp

More other servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.