Skip to main content
Glama
d00ennis

whoop-mcp

by d00ennis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
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
      43 npm
      1
      MIT

    • whoop-mcp

      AshwanthramKL
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server providing read-only access to WHOOP fitness data via direct OAuth, with a local SQLite cache for offline queries.
      68 PyPI
      MIT

    • whoopmcp

      kurok
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for the WHOOP API v2 that lets you query and analyze your own recovery, sleep, strain, cycles, and workout data. Note: currently a pre-alpha scaffold with stubbed internals.
      16
      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.
      26 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

    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