WHOOP MCP Server

Created By
RyanLissea year ago
An MCP server implementation for the WHOOP API
Overview

what is WHOOP MCP Server?

WHOOP MCP Server is an implementation of a Machine Conversation Protocol (MCP) server that interfaces with the WHOOP API, allowing users to access and interact with their WHOOP fitness data.

how to use WHOOP MCP Server?

To use the WHOOP MCP Server, clone the repository, install the dependencies, configure your WHOOP API key in the .env file, and start the server using npm start.

key features of WHOOP MCP Server?

  • Access to WHOOP user profile data
  • Retrieve sleep data and analytics
  • Fetch workout information
  • Get recovery metrics
  • View cycle data

use cases of WHOOP MCP Server?

  1. Analyzing sleep patterns and quality over time.
  2. Tracking workout performance and recovery metrics.
  3. Integrating WHOOP data with AI assistants for personalized fitness insights.

FAQ from WHOOP MCP Server?

  • What are the prerequisites for using the WHOOP MCP Server?

You need Node.js (v16+), a WHOOP account with API access, and a WHOOP API key.

  • How do I authenticate my requests?

You need to add your WHOOP API token to the Authorization header in your requests.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can submit a Pull Request.

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.

14 hours ago