Skip to main content
Glama
davidmosiah

WHOOP MCP

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to WHOOP MCP

No user-submitted related servers found.

    Related Servers

    • mcp-server-whoop

      Yadheedhya06
      A
      license
      A
      quality
      C
      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
      77 npm
      1
      MIT

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

    • whoop-mcp

      swapnilbhalgat
      A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted MCP server connecting Claude to your WHOOP data via the official API, enabling queries for recovery, sleep, cycles, workouts, and profile.
      11 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

    B3.4/5.0

    Scored across 30 tools

    Disambiguation3/5

    Core data-fetching tools (get_profile, list_cycles, list_recoveries, etc.) are distinct, but several meta/guidance tools overlap heavily: whoop_data_inventory, whoop_capabilities, whoop_agent_manifest, whoop_connection_status, whoop_privacy_audit, and whoop_demo all provide guidance or status without fetching WHOOP data, making boundaries fuzzy. whoop_quickstart and whoop_onboarding are also easily confused.

    Naming Consistency4/5

    Strong verb_noun convention (whoop_get_profile, whoop_list_sleeps) with the consistent whoop_ prefix. Minor deviations like whoop_capabilities and whoop_demo use no verb but remain clear.

    Tool Count2/5

    30 tools is heavy for a single-domain wellness connector, and several (data_inventory, capabilities, agent_manifest, demo, privacy_audit, connection_status, cache_status) are meta/guidance rather than core data access, suggesting the surface is over-expanded.

    Completeness4/5

    Good lifecycle coverage across profile, cycles, sleeps, recoveries, and workouts with get/list access plus aggregate trend tools. Missing create/update for WHOOP data is appropriate (read-only domain), though write/update operations for workouts or notes are absent.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources