Skip to main content
Glama

Related Servers

Alternatives to OpenAthlete

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that mirrors your Garmin data into a personal database and exposes tools for health summaries, training load, muscle readiness, and race analysis, with optional chat-driven insights via stdio or HTTP.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that lets AI agents query a user's own Garmin Connect data via Garmin's official Personal API. It exposes activities, daily wellness metrics, sleep and recovery, and body/profile data as tools for natural-language analysis.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that connects AI agents to Intervals.icu, enabling access to training data such as activities, wellness metrics, calendar events, gear, power curves, and custom items. Includes a running coach AI template for automated post-session analysis.
      19
      16 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for TrainingPeaks that reads workouts, fitness metrics (CTL/ATL/TSB), and health data, and creates/updates/deletes planned workouts. Enables AI-powered training plan management and automated adjustment based on performance, fatigue, and injury.
      -
    • A
      license
      B
      quality
      A
      maintenance
      An MCP server that gives LLMs access to Garmin Connect data, including training, recovery, sleep, stress, VO2 Max, and running summaries for personalized fitness advice.
      24
      337 PyPI
      1
      MIT

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    The tools mostly target distinct resources and actions. The only overlap is get_overview, which summarizes training load/recovery and may trigger sync, versus the specialized get_training_load, get_recovery_status, and sync_now; descriptions make the summary-vs-detail boundary clear enough.

    Naming Consistency4/5

    All names use lowercase snake_case and are predominantly verb_noun patterns such as get_*, query_*, read_*, write_*, and create_*. sync_now is the only non-noun object but remains clear and consistent.

    Tool Count5/5

    Nine tools is a good fit for a focused athlete-assistant surface. Each tool covers a distinct workflow, and there is no obvious redundancy or missing low-level utility.

    Completeness4/5

    Core read, sync, memory, and workout-creation workflows are covered. Notable gaps remain around the workout lifecycle (no update/delete and no explicit list/get workout) and plan mutation, though these may be delegated to platform MCPs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues