Skip to main content
Glama

Related Servers

Alternatives to whoop-postgres-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server that gives AI assistants like Claude, Codex, and GitHub Copilot access to your WHOOP recovery, sleep, HRV, strain, and workout data. It enables natural-language queries about daily readiness, personal baselines, trends across periods, sleep debt, and HYROX or triathlon performance, all without manually exporting data.
      17 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server that connects WHOOP data to AI assistants like Claude, Codex, and GitHub Copilot, enabling natural-language queries about recovery, sleep, HRV, strain, workouts, and personal health trends against your own baselines, plus HYROX and triathlon analytics. It runs locally, offers aggregate mode, and includes an interactive chart-first dashboard.
      17 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to query a user's WHOOP recovery, sleep, HRV, strain, workouts and body measurements through 16 read-only tools, including today's status, personal baselines, sleep debt, trends and period comparisons. Runs locally, requires no data exports, and supports aggregate mode that limits responses to high-level summaries.
      17 npm
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to query WHOOP recovery, sleep, HRV, strain, workouts, and personal health analytics in natural language through MCP clients such as Claude, Codex, and GitHub Copilot. It also provides read-only tools, resources, prompts, and local performance dashboards for reviewing trends and readiness evidence.
      17 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool targets a distinct data type (recovery, sleep, workouts, cycles) or action (auth, connect, sync, status), so boundaries are mostly clear. whoop_overview aggregates recovery/sleep/workouts/strain and thus overlaps with the individual read tools and whoop_baseline, but its 'one-call snapshot' description mostly disambiguates it.

    Naming Consistency5/5

    Every tool uses the same whoop_<noun> snake_case prefix with no mixing of conventions. The pattern is predictable and readable throughout.

    Tool Count5/5

    Ten tools is a well-scoped set: two auth tools, one sync, one status, one baseline, and six read tools. Each earns its place with no obvious redundancy.

    Completeness4/5

    The surface covers the full lifecycle: OAuth connect, sync, sync health, and reads across recovery, sleep, workouts, cycles, baseline, and overview. Minor gaps like token revocation/disconnect or delete operations are absent but not blocking for the read-oriented purpose.