Skip to main content
Glama
davidmosiah

WHOOP MCP

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to WHOOP MCP

No user-submitted related servers found.

    Related Servers

    • mcp-server-whoop

      Yadheedhya06
      A
      license
      A
      quality
      A
      maintenance
      A local-first, read-only MCP server that provides compact recovery, sleep, strain, HRV, heart-rate, workout, and body-measurement data from WHOOP without sending credentials to a third party.
      5
      34 npm
      1
      MIT

    • whoop-mcp

      rishi-mittal-web
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing full read/write access to Whoop wearable data, including recovery, sleep, workouts, journal, and more, via Whoop's private iOS API.
      25 npm
      MIT

    • whoop-mcp

      swapnilbhalgat
      A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted MCP server connecting Claude to your WHOOP data via the official API, enabling queries for recovery, sleep, cycles, workouts, and profile.
      6 npm
      MIT
    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

    A3.6/5.0

    Scored across 30 tools

    Disambiguation3/5

    Most data tools are clearly separated by resource and action, but there is a cluster of overlapping meta/helper tools (data_inventory, capabilities, agent_manifest, quickstart) that all describe setup, privacy, and recommended workflows, making it easy for an agent to call the wrong one. The get/list data tools themselves are otherwise distinct.

    Naming Consistency3/5

    All tools share the whoop_ prefix and snake_case, but conventions are not uniform: data tools use get_/list_ (whoop_get_sleep, whoop_list_cycles) while profile tools use object_verb (whoop_profile_get/update) and many helpers are bare nouns (whoop_capabilities, whoop_daily_summary). The names remain readable, but verb placement is inconsistent.

    Tool Count2/5

    30 tools is above the 'too many' threshold and includes several overlapping meta/documentation tools plus status helpers that could be consolidated. The core WHOOP data tools are justified, but the extra surface adds significant selection overhead for agents.

    Completeness5/5

    The server covers the full WHOOP read surface — profile, body measurements, cycles, recoveries, sleeps, and workouts — with list and get access, plus auth lifecycle, shared profile management, trends, and summaries. There are no obvious dead ends; recovery detail is accessible via list_recoveries and get_cycle_recovery.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources