Skip to main content
Glama
d00ennis

whoop-mcp

by d00ennis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WHOOP_MCP_DATA_DIRNoDirectory to store data (default: ~/.whoop-mcp)
WHOOP_MCP_EXPORT_PATHNoPath for JSON export (default: ~/.whoop-mcp/whoop.json)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
whoop_summaryA

Kombinierter Tagesueberblick: Recovery, Schlaf und Strain je Tag.

Das Standard-Tool fuer Fragen wie "Wie war meine Woche?". Liefert pro Tag einen Datensatz plus Durchschnitte und Trends.

whoop_recoveryC

Recovery Score, HRV, Ruhepuls, SpO2 und Hauttemperatur der letzten Tage.

whoop_sleepC

Schlafdauer, Schlafphasen, Performance, Konsistenz und Atemfrequenz.

whoop_cyclesC

Tages-Strain, Kalorienverbrauch sowie durchschnittliche und maximale Herzfrequenz.

whoop_workoutsA

Trainingseinheiten mit Strain, Herzfrequenzzonen, Distanz und Kalorien.

Mit sport laesst sich auf eine Sportart filtern, etwa "running".

whoop_bodyA

Koerpermasse aus WHOOP: Groesse, Gewicht und maximale Herzfrequenz.

whoop_historyB

Langfristige Auswertung aus der lokalen Datenbank statt aus der API.

Schnell und ohne Rate-Limit, benoetigt aber einen vorherigen Sync. Mit metric (etwa "hrv_ms", "recovery_score", "strain", "asleep_hours") kommt zusaetzlich ein Trendvergleich zurueck.

whoop_syncB

Daten von WHOOP in die lokale Datenbank holen und den Life-OS-Export schreiben.

Ohne days wird ab dem letzten Sync nachgeholt.

whoop_lifeos_updateA

Recovery, Schlaf und Strain ins Life-OS-Dashboard schreiben.

Aktualisiert nur die Whoop-Felder; Strava-Aktivitaeten, Gewicht und Ernaehrung bleiben unberuehrt. Vor dem Schreiben wird eine Sicherung angelegt. Mit dry_run werden die Aenderungen nur angezeigt.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct data category (recovery, sleep, cycles, workouts, body, history) or operation (sync, Life-OS update), with clear descriptions that eliminate ambiguity. The summary tool provides an overarching view but does not overlap with specific metric tools.

Naming Consistency5/5

All tools follow the consistent pattern 'whoop_<descriptive_noun>', with only 'whoop_lifeos_update' using a compound noun, which is still uniform and predictable.

Tool Count5/5

With 9 tools, the set is well-scoped for a health/fitness MCP server, covering essential data retrieval, history, and synchronization without unnecessary bloat.

Completeness4/5

The domain of WHOOP data is well-covered: recovery, sleep, strain, workouts, body metrics, and historical trends are all present. Minor gaps like account info or raw intraday data might be missing, but core user needs are met.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources