Skip to main content
Glama

Related Servers

Alternatives to garmin-personal-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to query Garmin training and recovery data—including activities, laps, strength sets, sleep, HRV, stress, and Body Battery—through the official read-only Garmin Connect Personal API. It also enables generating training dashboards and reviewing workouts, recovery, and readiness inside the chat.
      20
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to query a user's own Garmin Connect training, health, and recovery history through Garmin's official Personal API, backed by a local cache and built-in analysis tools.
      21
      117 npm
      2
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to access and query Garmin Connect health and fitness data, including sleep, HRV, training load, and activities, with an optional coaching plugin for personalized training plans.
      4
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read Garmin activities and create/schedule structured workouts and multi-week training plans directly on Garmin Connect, syncing to your watch with guided prompts.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read Garmin activities and create/schedule structured workouts and multi-week training plans on Garmin Connect, syncing to the user's watch.
      1
      MIT

    TDQS

    A4.1/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target clearly distinct Garmin resources or actions: weight, sleep, HRV, activities, laps, sets, workouts, and FIT download are well separated. The main ambiguity is the dashboard cluster: getDashboardData, writeDashboard, showDashboard, editDashboard, and scheduleDashboardRefresh overlap in purpose, though their descriptions clarify the boundaries. garminGet is intentionally a fallback and could be confused with covered endpoints, but its generic nature is explicit.

    Naming Consistency4/5

    All tool names use camelCase, which is consistent, and most follow a verb_noun pattern such as getSleep, listActivities, downloadActivityFit, and scheduleDashboardRefresh. There are minor deviations: garminGet is an odd prefix/verb construction, and the dashboard tools use write/edit/show rather than a uniform get/manage pattern. Overall the naming is predictable and readable.

    Tool Count4/5

    Twenty tools is slightly heavy but appropriate for a Garmin personal data server that spans health metrics, activities, .FIT-derived detail, dashboard generation, and dashboard scheduling. Each tool generally earns its place by covering a specific data source or workflow. It is near the upper end of comfortable scope but not excessive for the domain.

    Completeness4/5

    The surface is broad for read-oriented Garmin analytics: daily summaries, sleep, HRV, heart rate, body battery, weight, fitness age, activities, activity laps/sets/workouts, and dashboard management. Minor gaps exist for some standalone metrics and profile/settings actions, but garminGet provides a generic fallback. Core lifecycle coverage for the dashboard is present, including write, edit, show, and scheduled refresh.