Whoop API MCP Server

Created By
RyanLissea year ago
MCP server for interacting with the Whoop API to retrieve fitness and health data
Overview

What is Whoop API MCP Server?

The Whoop API MCP Server is a Mission Control Protocol server designed to interact with the Whoop API, allowing users to retrieve various fitness and health data seamlessly.

How to use Whoop API MCP Server?

To use the Whoop API MCP Server, clone the repository, install the necessary dependencies, set up your environment variables with your Whoop API credentials, and start the server. You can then access the MCP endpoint and authenticate users to retrieve their fitness data.

Key features of Whoop API MCP Server?

  • OAuth 2.0 authentication with Whoop API
  • Access to user profile, recovery, sleep, workout, and menstrual cycle data
  • MCP-compliant discovery endpoint
  • Clean error handling and logging

Use cases of Whoop API MCP Server?

  1. Integrating Whoop fitness data into health and fitness applications.
  2. Analyzing user recovery and sleep patterns for better health insights.
  3. Tracking menstrual cycles in fitness applications.

FAQ from Whoop API MCP Server?

  • What data can I retrieve using this server?

You can retrieve user profile information, recovery data, sleep data, workout data, and menstrual cycle tracking data.

  • Do I need a Whoop developer account?

Yes, you need a Whoop developer account and API credentials to use this server.

  • Is there any cost associated with using the Whoop API?

The usage of the Whoop API may depend on your account type and the terms set by Whoop.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
RyanLisse
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago