Skip to main content
Glama
Sign In
garmin-connect-api

garmin-connect-api

by happyc0der
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to garmin-connect-api

No user-submitted related servers found.

    Related Servers

    • Garmin MCP

      shyim
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to read and update Garmin Connect data, including activities, health metrics, training status, and more, with per-account multi-tenant authentication.
      3
      MIT

    • Garmin MCP Server

      OJHela
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects to Garmin Connect and exposes fitness and health data to MCP-compatible clients, enabling activity management, health metrics, training and performance analytics, workout creation/scheduling, gear, nutrition, and related data access.
      MIT

    • 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

    • Garmin MCP Server

      jaounial
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects to Garmin Connect to expose fitness and health data to MCP-compatible clients, enabling activity management, health metrics, training analytics, workout creation, and more via natural language.
      MIT

    • Garmin Connect MCP

      LePomas
      A
      license
      B
      quality
      D
      maintenance
      Exposes personal Garmin Connect data to MCP-capable clients like Claude and Gemini. Enables querying daily stats, heart rate, sleep, activities, and managing workouts.
      16
      MIT

    • mcp-garmin

      PilarJ
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Garmin Connect data through MCP, enabling retrieval of activities, health metrics, training status, and workouts, with OAuth authentication and confirmed write operations.
      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

    A4.4/5.0

    Scored across 38 tools

    Disambiguation4/5

    Tools like get_day_summary, week_summary, get_trend, and the individual metric tools (get_sleep, get_hrv, get_stress, get_steps) all touch overlapping wellness data, which creates real selection ambiguity. However, descriptions exhaustively cross-reference each other and state exactly when to use one over the other, so an agent can resolve the choice reliably.

    Naming Consistency4/5

    The dominant pattern is verb_noun (list_activities, get_activity, delete_workout, add_weigh_in) or noun_action, but there are deviations: 'garmin_status' has an odd server prefix, and 'week_summary'/'recent_strength_sessions' are bare nouns while 'log_strength_session'/'match_exercise' use different verb styles. Still largely predictable and readable.

    Tool Count3/5

    38 tools is well into heavy territory and pushes against easy navigation, though the breadth reflects a genuinely large domain (activities, workouts, wellness metrics, devices, exercise catalogue). Each tool appears to earn its place, avoiding redundancy, but the set is large enough to burden an agent's selection.

    Completeness5/5

    Coverage is thorough: full CRUD for activities, sets, weigh-ins, and workouts, plus scheduling, device push, exercise lookup, personal records, and a comprehensive range of wellness reads. No obvious dead ends for the domain's core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources