How to Connect WHOOP to Meta Muse via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → WHOOP, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

WHOOP + Meta Muse

Read a WHOOP member's recovery, HRV, resting heart rate, sleep and naps with stages, day strain per cycle, workouts with heart rate zones, profile and body measurements through the WHOOP Developer API v2 with OAuth. Read-only.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

WHOOP_CLIENT_ID, WHOOP_CLIENT_SECRET

Step 1 — Get credentials

Setting up takes about 10 minutes, once. You need a WHOOP account.

1. Open the WHOOP Developer Dashboard at https://developer-dashboard.whoop.com and sign in with a WHOOP account. Create a team when asked (a team can hold up to 5 apps).
2. Click Create App. Under Scopes tick read:profile, read:body_measurement, read:cycles, read:recovery, read:sleep and read:workout. The connector also asks for offline, which WHOOP needs to issue a refresh token.
3. Under Redirect URIs add https://cloud.anythingmcp.com/api/mcp-oauth/callback on AnythingMCP Cloud, or <your AnythingMCP URL>/api/mcp-oauth/callback when you host AnythingMCP yourself.
4. Save, and copy the Client ID and Client Secret into WHOOP_CLIENT_ID and WHOOP_CLIENT_SECRET. Install the connector, click Authorize with Provider and allow access with the WHOOP account whose data the AI should read.
5. Run whoop_get_profile to check the connection.

Access tokens last about an hour and are renewed automatically; WHOOP replaces the refresh token on every renewal.

What it reads: the connected member's profile and body measurements (height, weight, max heart rate); physiological cycles, where a cycle is one WHOOP day from waking up to waking up, with day strain, energy and heart rate; the recovery of each cycle with recovery score, HRV, resting heart rate and, on WHOOP 4.0 or newer, SpO2 and skin temperature; sleeps and naps with time per stage, sleep need, performance, consistency, efficiency and respiratory rate; and workouts with sport, strain, heart rate, energy, distance, altitude and time in each heart rate zone.

Finding a day: the AI lists cycles (the newest has no end while it is running) and goes from a cycle id to its recovery and its sleep. For trends it lists recoveries, sleeps or workouts between a start and an end.

Read-only: every tool only reads. The WHOOP API offers no way to write data, so there is nothing to confirm and no tool is switched off at install. Journal entries, the stress monitor, heart rate streams and WHOOP Coach are not part of the public API.

Formats: only records with score_state SCORED carry a score; PENDING_SCORE means WHOOP is still computing it, UNSCORABLE that it never will be (for example when the strap was not worn). Times are UTC, and timezone_offset is the member's local offset, which the AI applies before naming a local day. Durations ending in _milli are milliseconds. Strain is WHOOP's 0 to 21 scale, kilojoule is energy (divide by 4.184 for kilocalories), percentages are 0 to 100 and heart rates are beats per minute.

Limits: list tools return up to 25 records per call, newest first, with a next_token while more exist. WHOOP allows 100 requests per minute and 10,000 per day per app by default; over that it answers 429.

Common errors: 401 means the authorization expired or was revoked (click Authorize with Provider again), 403 or an empty answer for one kind of data usually means its scope was not granted, and 404 an unknown id.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Muse

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the WHOOP tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.

Available tools

Example prompts

• "What is my recovery score today, and how do my HRV and resting heart rate compare with my 30-day average?"
• "How long did I sleep each night this week, and how much of it was REM and slow wave sleep?"
• "List my workouts of the last two weeks with sport, strain and time in heart rate zones 4 and 5."
• "On mornings after a day strain above 15, how did my recovery look?"
• "Did I take any naps this month, and how long were they?"

FAQ

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Microsoft Copilot