WHOOP MCP Server for Claude Desktop 11 tools — connect in under 2 minutes
Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install WHOOP and 2,500+ MCP Servers from a single visual interface.




{
"mcpServers": {
"whoop": {
// Your Vinkius token — get it at cloud.vinkius.com
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About WHOOP MCP Server
Connect your WHOOP account to any AI agent and access your personal health data through natural conversation.
Claude Desktop is the definitive way to connect WHOOP to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
What you can do
- Profile — View your WHOOP profile and body measurements (height, weight, max HR)
- Cycles — Browse your 24-hour WHOOP cycles combining sleep, strain and recovery
- Sleep — Analyze sleep data with stages (light, deep, REM), duration and performance
- Recovery — Track recovery scores, HRV, resting heart rate and sleep balance
- Workouts — Review workout data with strain, heart rate zones, duration and calories
- Pagination — Navigate through historical data with date ranges and pagination tokens
The WHOOP MCP Server exposes 11 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect WHOOP to Claude Desktop via MCP
Follow these steps to integrate the WHOOP MCP Server with Claude Desktop.
Open Claude Desktop Settings
Go to Settings → Developer → Edit Config to open claude_desktop_config.json
Add the MCP Server
Paste the configuration above into the mcpServers section
Restart Claude Desktop
Close and reopen Claude Desktop to load the new server
Start using WHOOP
Look for the 🔌 icon in the chat — your 11 tools are now available
Why Use Claude Desktop with the WHOOP MCP Server
Claude Desktop by Anthropic provides unique advantages when paired with WHOOP through the Model Context Protocol.
Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network
WHOOP + Claude Desktop Use Cases
Practical scenarios where Claude Desktop combined with the WHOOP MCP Server delivers measurable value.
Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation
Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language
Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary
Learning and training: new team members can explore API capabilities conversationally without needing to read documentation
WHOOP MCP Tools for Claude Desktop (11)
These 11 tools become available when you connect WHOOP to Claude Desktop via MCP:
get_body_measurement
Useful for tracking physical metrics alongside your WHOOP data. Get your body measurement data
get_cycle
Includes sleep, recovery, strain and heart rate metrics for that 24-hour period. Get a specific WHOOP cycle by ID
get_cycle_recovery
Includes recovery score, resting heart rate, HRV (heart rate variability), sleep balance and strain balance. Get recovery data for a specific WHOOP cycle
get_cycle_sleep
Includes sleep duration, stages (light, deep, REM, awake), disturbances and sleep performance percentage. Get sleep data for a specific WHOOP cycle
get_cycles
Cycles represent 24-hour periods of recovery and strain data. Each cycle includes sleep, recovery, strain and heart rate metrics. Supports date range filtering with start/end in ISO 8601 format. Pagination: max 25 results, use nextToken for more. Get your WHOOP cycle data
get_profile
Use this to verify your authentication is working and get your user ID for other endpoints. Get your WHOOP profile info
get_recovery
Supports date range filtering. Pagination: max 25 results per request. Get your WHOOP recovery data
get_sleep
Supports date range filtering. Pagination: max 25 results. Get your WHOOP sleep data
get_sleep_by_id
Includes full sleep stages, disturbances, respiratory rate and sleep performance. Get a specific WHOOP sleep record by ID
get_workout
Includes strain score, duration, heart rate zones, calories burned and GPS data if available. Get a specific WHOOP workout by ID
get_workouts
Supports date range filtering. Pagination: max 25 results. Get your WHOOP workout data
Example Prompts for WHOOP in Claude Desktop
Ready-to-use prompts you can give your Claude Desktop agent to start working with WHOOP immediately.
"Show me my recovery score from today."
"How did I sleep last night?"
"Show me my workouts from this week."
Troubleshooting WHOOP MCP Server with Claude Desktop
Common issues when connecting WHOOP to Claude Desktop through the Vinkius, and how to resolve them.
Server not appearing after restart
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).Authentication error
Tools not showing in chat
WHOOP + Claude Desktop FAQ
Common questions about integrating WHOOP MCP Server with Claude Desktop.
How does Claude Desktop discover MCP tools?
claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.What happens if the MCP server is temporarily unavailable?
Can I connect multiple MCP servers simultaneously?
mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.Is there a limit on the number of tools per server?
Does Claude Desktop support Streamable HTTP transport?
Connect WHOOP with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect WHOOP to Claude Desktop
Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.
