Skip to main content
Glama
armonge

Wahoo MCP Server

by armonge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Wahoo MCP Server

No user-submitted related servers found.

    Related Servers

    • Wahoo MCP Server

      ClemensHar
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server for interacting with the Wahoo Cloud API, focusing on reading workout information.
      10
      GPL 3.0

    • mcp-whoop

      PilarJ
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes the WHOOP v2 API, enabling users to retrieve health data such as cycles, recovery, sleep, and workouts. It uses GitHub OAuth for authentication and is designed for remote use over HTTP.
      MIT

    • garmin-mcp

      aapiskotin
      A
      license
      A
      quality
      C
      maintenance
      Enables creating, previewing, scheduling, and managing Garmin Connect workouts, plus reading activities and health metrics, all through a local MCP server.
      11
      MIT

    • whoop-mcp

      AshwanthramKL
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server providing read-only access to WHOOP fitness data via direct OAuth, with a local SQLite cache for offline queries.
      51 PyPI
      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.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources (plans, power zones, routes, workouts) with clear action verbs (create, get, list). There is no ambiguity or overlap between tools, as each tool name precisely indicates what resource it operates on and what action it performs.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case throughout. The naming convention is perfectly predictable: create_plan, get_plan, list_plans, get_power_zone, list_power_zones, etc. There are no deviations or mixed styles.

    Tool Count5/5

    With 9 tools, this server is well-scoped for managing Wahoo fitness resources. Each tool earns its place by covering distinct operations (create, get, list) across four resource types (plans, power zones, routes, workouts), providing a balanced and focused toolset.

    Completeness3/5

    The server covers get and list operations comprehensively for all four resource types, plus create for plans. However, there are notable gaps: no update or delete operations for any resource, and create is missing for power zones, routes, and workouts. This limits full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources