Skip to main content
Glama
alacore

whoop-tracker-mcp-server

by alacore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to whoop-tracker-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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
      8 npm
      1
      MIT

    • WHOOP MCP Server

      nissand
      A
      license
      B
      quality
      F
      maintenance
      Enables access to WHOOP fitness and health data through all WHOOP v2 API endpoints. Supports OAuth 2.0 authentication and provides comprehensive access to user profiles, physiological cycles, recovery metrics, sleep analysis, and workout data.
      16
      289 npm
      16
      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
      8 npm
      -
    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.3/5.0

    Scored across 5 tools

    Disambiguation4/5

    Tools are mostly distinct: cycles, recovery (two variants but scoped differently), sleep, and workouts. The two recovery tools could cause minor confusion, but descriptions clarify date range vs. cycle-specific.

    Naming Consistency5/5

    All tools follow a consistent 'whoop_get_<resource>' pattern with qualifiers like 'by_id' or 'for_cycle'. No mixed conventions or irregular verbs.

    Tool Count5/5

    With 5 tools covering core fitness metrics (cycles, recovery, sleep, workouts), the count is well-scoped and not excessive or sparse for the server's apparent purpose.

    Completeness3/5

    The set covers key read operations, but notably lacks a tool to list cycles (e.g., 'get_cycles'), which agents would need to obtain cycle IDs for other tools. This gap could hinder some workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources