Skip to main content
Glama
nissand

WHOOP MCP Server

by nissand
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to WHOOP MCP Server

No user-submitted related servers found.

    Related Servers

    • WHOOP

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to your WHOOP health data, including recovery, sleep, strain, workouts, cycles, and body measurements, through the official v2 API with OAuth 2.0.
      MIT

    • WhoopMCP

      wackari
      F
      license
      A
      quality
      C
      maintenance
      Enables querying WHOOP fitness data including recovery, sleep, workouts, physiological cycles, and profile via the WHOOP API v2.
      11
      6 npm
      -

    • WHOOP MCP Server

      izqui
      A
      license
      A
      quality
      D
      maintenance
      Enables LLMs to retrieve and analyze sleep, recovery, and physiological cycle data from the WHOOP API. It provides tools for accessing detailed metrics such as strain, HRV, and readiness scores through secure OAuth 2.0 authentication.
      4
      6 npm
      1
      MIT

    • Withings MCP Server

      Schimmilab
      A
      license
      A
      quality
      B
      maintenance
      Enables access to Withings Health API data including body measurements, activity tracking, sleep analysis, workouts, and heart rate monitoring through OAuth2 authentication.
      8
      1
      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 16 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources like cycles, sleep, workouts, recovery, and authentication. However, there is some potential overlap between collection tools (e.g., whoop-get-cycle-collection and whoop-get-recovery-collection) and their cycle-specific counterparts (e.g., whoop-get-recovery-for-cycle), which could cause minor confusion in selection.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with the prefix 'whoop-' and clear action-object naming (e.g., whoop-get-cycle-by-id, whoop-refresh-token). The naming is uniform across all 16 tools, making them predictable and easy to understand.

    Tool Count4/5

    With 16 tools, the count is slightly high but reasonable for a fitness/health API server covering authentication, user data, cycles, sleep, workouts, and recovery. It provides comprehensive coverage without being overly bloated, though it borders on the upper limit of typical scoping.

    Completeness4/5

    The tool set covers core CRUD-like operations for key resources (cycles, sleep, workouts, recovery) and includes essential authentication flows (OAuth, token management). Minor gaps exist, such as lack of update or delete operations for user data or workout records, but agents can likely work around these for most use cases.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources