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
      Not graded
      quality
      B
      maintenance
      Connects Garmin Connect to AI assistants, answering questions about training, sleep, HRV and recovery with metrics computed in code rather than guessed from raw JSON. Queries daily readiness, training load, activity FIT analysis and personal records through a self-hosted Cloudflare Worker with OAuth.
      10
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables reading and analyzing Garmin Connect data—activities, health metrics, FIT files, and challenges—through natural language, for AI assistants like Claude and ChatGPT.
      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
      91 npm
      2
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target a distinct resource (heart rate, sleep, HRV, weight, body battery, activity laps/sets/workouts), and descriptions explicitly cross-reference each other to steer selection (e.g. 'for sleep use getSleep'). The main soft spot is the four-tool dashboard cluster (getDashboardData, writeDashboard with preview:true, showDashboard, editDashboard), which all return overlapping digests and require careful reading to tell apart, and garminGet intentionally overlaps everything as a fallback.

    Naming Consistency4/5

    Nearly all tools are camelCase verb_noun (getSleep, listActivities, downloadActivityFit, writeDashboard, scheduleDashboardRefresh), giving a predictable pattern. The outlier is garminGet, which uses an app-prefixed verb-last form that breaks the convention, but it is clearly the generic escape hatch.

    Tool Count4/5

    20 tools sits on the heavy side, but the domain genuinely spans many data sources (activities with laps/sets/plans, sleep, HRV, weight, Body Battery, HR zones, fitness age) plus a dashboard lifecycle and scheduler. Only the dashboard cluster (get/write/show/edit/schedule) feels like it could be consolidated, so it is slightly over-scoped rather than bloated.

    Completeness4/5

    Read coverage is excellent across health and activity domains, including deep activity detail (laps, strength sets, planned workouts, raw .FIT download) and a full local dashboard lifecycle with scheduling. The notable gap is that the surface is read-only against Garmin Connect (no logging weight/activities, no creating workouts); garminGet partially mitigates missing endpoints but is itself GET-only.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues