Skip to main content
Glama

Related Servers

Alternatives to garmin-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude and other MCP-compatible clients to access and manage Garmin Connect fitness, health, training, nutrition, workout, gear, and device data through 110+ tools. Supports activity editing, workout creation and scheduling, health metrics, and advanced analytics.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to read Garmin Connect data such as activities, sleep, HRV, VO2 max and training readiness, and optionally view or manage TrainingPeaks workouts and sync them to a watch, over streamable HTTP secured with MCP OAuth 2.1 and GitHub login.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude to access and query your Garmin Connect data—sleep, training, heart rate, and more—through a suite of read-only tools, with an optional write path for creating strength workouts.
      63
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude to access and query your Garmin Connect data, including sleep, activities, training load, and health metrics, through a set of read-only MCP tools.
      28
      154 PyPI
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to read recent Garmin activities and wellness/recovery data and to create, update, or delete structured workouts that sync through intervals.icu to Garmin Connect and the user's watch.
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Connects Garmin training data to Claude so it can read recent activities, wellness and recovery signals, and upcoming calendar events. It also lets Claude create, update, and delete structured workouts that sync through intervals.icu to Garmin Connect and onto the user's watch.
      MIT

    TDQS

    B3.3/5.0

    Scored across 39 tools

    Disambiguation4/5

    Tools are organized around distinct Garmin domains (activities, wellness, training, nutrition, body, devices), and paired tools like garmin_activities/garmin_activity are clearly list-vs-detail. A few boundaries blur: garmin_add_weigh_in vs garmin_add_body_composition, garmin_create_workout vs garmin_upload_workouts, and the three 'escape hatch' tools (garmin_api_get, garmin_fit_messages, garmin_activity_analysis) all claim to be for cases no other tool covers.

    Naming Consistency4/5

    All names use a uniform garmin_ prefix and snake_case, with predictable verb_noun forms for mutations (add_, create_, set_, log_, delete_) and noun forms for readers. The mix of noun-only readers (garmin_profile, garmin_gear) and verb_noun tools (garmin_add_weigh_in) is a minor inconsistency but internally readable.

    Tool Count3/5

    39 tools exceeds the comfortable 3-15 range and lands in heavy territory. The Garmin Connect domain is genuinely broad enough to justify many of them, but multiple escape-hatch/analysis tools and a few overlapping add_ tools push it past what most agents can navigate efficiently.

    Completeness5/5

    Coverage spans read, create, update, schedule, upload, download, and delete across activities, wellness, training, nutrition, body, devices, gear, workouts, calendar, courses, achievements, and women's health. Every apparent data domain has a corresponding mutation or lifecycle operation, and the preview-then-confirm delete pattern closes the loop for destructive actions.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data