Skip to main content
Glama

Related Servers

Alternatives to garmin-owl

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP-capable AI apps to query a user's own Garmin sleep, HRV, stress, Body Battery, heart-rate, activity, and body-metric data through Garmin's official Personal API in a read-only, locally run setup.
      14
      266 PyPI
      1
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Gives AI assistants local, read-only access to your Garmin Connect health and activity data using your normal account login. Enables querying and downloading roughly 260 kinds of data such as activities, sleep, heart rate, stress, body composition, and training metrics without ever modifying your account.
      62
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs and MCP clients to securely access your Garmin Connect health and running data, including daily wellness metrics, activity details, training status, and race predictions, for personalized coaching and analysis.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables local synchronization of Garmin activity and health data using a personal API key, then lets MCP-connected AI clients analyze training readiness and recovery with cited models and research. Supports viewing records, sleep/HRV, stress, Body Battery, and generating pre-run recommendations without hosting accounts or personal data.
      2
      MIT

    TDQS

    A4.4/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have distinct targets and the descriptions explicitly route between detail, aggregate, and trend views. There is still meaningful overlap among get_daily_summary/get_recovery/get_training_context, get_activities/get_recent_activities/get_training_week, and get_daily_series/get_period_summary/get_recovery_trend, so some careful tool selection is needed.

    Naming Consistency5/5

    Tool names consistently use snake_case and a predictable get_noun or verb_noun pattern, e.g. get_sleep, get_training_load, compare_activities. Minor variations like get_activities_detail are still clear and fit the overall convention.

    Tool Count3/5

    The 24 tools cover a broad Garmin analytics domain, and many earn their place, but the count is heavy and sits at the upper end of the borderline range. Several tools provide convenience or composite views that could be consolidated for easier selection.

    Completeness4/5

    The surface covers daily health, sleep, HRV, recovery, readiness, Body Battery, stress, activities, training load, trends, cycle, and coverage checks, with good lifecycle support for a read-only analytics server. Minor gaps remain for some Garmin data families such as workouts/gear/hydration or dedicated respiration/SpO2 detail, but core workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessNo issues