Skip to main content
Glama
Yadheedhya06

mcp-server-whoop

by Yadheedhya06
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-server-whoop

No user-submitted related servers found.

    Related Servers

    • whoop-mcp

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

    • whoop-mcp

      d00ennis
      F
      license
      B
      quality
      D
      maintenance
      Local MCP server for the WHOOP API v2 that provides tools to access recovery, sleep, strain, and workout data, with local history and JSON export.
      9
      -

    • whoop-mcp

      rishi-mittal-web
      A
      license
      Not graded
      quality
      D
      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.
      11 npm
      MIT

    • whoop-ai-mcp

      sakuralopes09594
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only WHOOP MCP server that lets AI assistants answer questions about your recovery, sleep, HRV, strain, and workouts against personal baselines, plus HYROX and triathlon readiness tracking with a local dashboard. It runs locally, exposes only read-only tools, and supports Claude Desktop, Claude Code, Codex, and GitHub Copilot.
      4 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

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct WHOOP data domain: overall overview, sleep history, cycle strain history, and workout history. There is no overlap in purpose, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tool names follow a consistent pattern: 'whoop_' followed by a descriptive noun phrase (e.g., latest_overview, sleep_history). The naming is uniform and predictable.

    Tool Count5/5

    With 4 tools, the server covers the core WHOOP data categories (overview, sleep, cycle strain, workouts) without unnecessary bloat. The count is well-scoped for a focused integration.

    Completeness4/5

    The tool set covers the most commonly accessed WHOOP data types. However, it lacks dedicated tools for specific metrics like HRV or recovery details, though the overview tool may subsume some of these. Minor gap for a comprehensive read-only surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources