How do I get WHOOP API credentials?

Visit [**developer.whoop.com**](https://developer.whoop.com/), create an app to get a Client ID and Client Secret. Then complete the OAuth2 flow to obtain an Access Token. All three are required for API access.

What is a WHOOP cycle?

A WHOOP cycle represents a 24-hour period combining your sleep, strain and recovery data. Each cycle starts when you wake up and includes the previous night's sleep, the day's strain, and your recovery score for the next day.

How much historical data can I access?

You can access all historical data recorded by your WHOOP device. Use the start and end date parameters (ISO 8601 format) to filter results. Pagination returns up to 25 records per request; use the nextToken to retrieve more.

Does the API include heart rate data?

Yes! Heart rate data (average and max) is included in the cycle, workout and recovery responses. There's no dedicated heart rate endpoint, but the data is nested within these resources.

WHOOP MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: WHOOP
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to WHOOP through Vinkius, pass the Edge URL in the `mcps` parameter and every WHOOP tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="WHOOP Specialist",
    goal="Help users interact with WHOOP effectively",
    backstory=(
        "You are an expert at leveraging WHOOP tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in WHOOP "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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.

When paired with CrewAI, WHOOP becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call WHOOP tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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 CrewAI 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 CrewAI via MCP

Follow these steps to integrate the WHOOP MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 11 tools from WHOOP

Why Use CrewAI with the WHOOP MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with WHOOP through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

WHOOP + CrewAI Use Cases

Practical scenarios where CrewAI combined with the WHOOP MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries WHOOP for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries WHOOP, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain WHOOP tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries WHOOP against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

WHOOP MCP Tools for CrewAI (11)

These 11 tools become available when you connect WHOOP to CrewAI 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 CrewAI

Ready-to-use prompts you can give your CrewAI 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 CrewAI

Common issues when connecting WHOOP to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

WHOOP + CrewAI FAQ

Common questions about integrating WHOOP MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.