Skip to main content
Glama
AaronRoeF

whoop-mcp

by AaronRoeF
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to whoop-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      20 npm
      MIT

    • 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

    • 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

      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.
      51 PyPI
      MIT

    • mcp-whoop

      PilarJ
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes the WHOOP v2 API, enabling users to retrieve health data such as cycles, recovery, sleep, and workouts. It uses GitHub OAuth for authentication and is designed for remote use over HTTP.
      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.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: OAuth tokens, user profile, and various physiological data (cycles, recovery, sleep, workouts). There is no ambiguity between tools like get-cycle-collection and get-cycle-by-id, as they serve different purposes (list vs. single item).

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern starting with 'whoop-', e.g., whoop-get-cycle-by-id, whoop-get-cycle-collection, whoop-refresh-token. Verbs are clear (get, exchange, refresh, revoke, set) and nouns are specific, making the naming predictable and easy to navigate.

    Tool Count5/5

    With 16 tools, the set covers the core WHOOP API surface: OAuth authentication, user information, and paginated retrieval of physiological data. The number is appropriate for the domain, providing comprehensive access without being excessive.

    Completeness5/5

    The tool set covers all essential operations for the WHOOP API: OAuth flow, user profile, body measurements, and retrieval of cycles, recovery, sleep, and workouts (both collections and by-id or by-cycle). No obvious gaps are present for a read-focused API with token management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources