Skip to main content
Glama
Sign In
Garmin Connect MCP

Garmin Connect MCP

by graiola
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Garmin Connect MCP

No user-submitted related servers found.

    Related Servers

    • garmin-mcp

      nbaradar
      F
      license
      A
      quality
      D
      maintenance
      Provides read-only access to your Garmin Connect health data, including sleep, HRV, body battery, stress, training readiness, and activities, through an MCP server.
      2
      14
      -

    • garmin-mcp

      barcia
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives MCP clients read-only access to Garmin Connect data through Garmin's official Personal API, exposing daily metrics, sleep, activities, body composition, and related wellness endpoints via OAuth-protected remote tools.
      MIT

    • ownmetrics-mcp

      badisbenhamida
      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

    • garmin-mcp

      Sinfjell
      A
      license
      A
      quality
      B
      maintenance
      Connects MCP clients to Garmin Connect data, enabling queries about activities, sleep, heart rate, body battery, and training status.
      16
      2
      MIT

    • garmin-mcp

      ronkatz29
      A
      license
      B
      quality
      B
      maintenance
      Enables retrieval of Garmin Connect data such as activities, sleep, heart rate, and body battery levels using unofficial API through MCP tools.
      4
      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

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools map to distinct resources/actions (list vs. get activity, workouts tied to an activity, connector status). The only real overlap is between garmin_get_health_range and garmin_get_day_detail, since both can return sleep/HRV data for a single day; the descriptions distinguish summaries from original per-date data, which mostly resolves it.

    Naming Consistency4/5

    All names share the garmin_ prefix and follow a verb_noun pattern (get_activity, list_activities, get_health_range, get_day_detail). garmin_connector_status is a minor deviation lacking a verb, but it is still clearly readable and predictable.

    Tool Count4/5

    Six tools is a lean, well-scoped surface for a read-only Garmin data connector, and each tool covers a distinct access pattern. Slightly thin, but no tool feels redundant.

    Completeness4/5

    The core read lifecycle is covered: status, activity listing/pagination, activity details, activity workouts, and ranged/per-day health metrics. Minor gaps exist (no explicit workout library, device/profile info, or dedicated splits/streams access), but agents can work around them via garmin_get_activity.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources