Skip to main content
Glama

Related Servers

Alternatives to garmin-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      A
      maintenance
      Enables an MCP client to read and write a personal Garmin Connect account: activities with per-set strength detail, daily health metrics (sleep, HRV, stress, steps, readiness), planned and completed workouts, and weigh-ins with body composition. It also logs finished strength sessions and body-composition readings as FIT files so they appear in Garmin Connect like natively recorded ones.
      38
      250 PyPI
      2
      MIT
    • 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
    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants and MCP clients to read and write Garmin China health, activity, and training data, including creating, scheduling, and pushing workouts to paired devices.
      2
      MIT
    • 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

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: library CRUD (list/get/create/update/delete), calendar operations (schedule/unschedule/upcoming), and separate read endpoints for activities, sleep, readiness, body metrics, race predictions and HR zones. The descriptions explicitly disambiguate the potentially confusable pairs (garmin_workouts_list vs garmin_upcoming_workouts, garmin_workout_delete vs garmin_workout_unschedule). No two tools appear to do the same thing.

    Naming Consistency4/5

    There is a clear, mostly consistent convention: a garmin_ prefix, bare noun phrases for read endpoints (garmin_sleep, garmin_activities, garmin_body_metrics) and garmin_workout_<verb> for mutations. The main wrinkle is the odd one-out garmin_workouts_list versus the singular garmin_workout_get/create/update, which breaks the pluralization pattern within the workout family.

    Tool Count5/5

    Fourteen tools sit comfortably in the well-scoped range, and every tool covers a distinct slice of the Garmin domain (workout lifecycle, calendar, and training/recovery reads). Nothing feels padded or redundant.

    Completeness4/5

    The workout lifecycle is fully covered — create, get, list, update, delete, schedule and unschedule — so there are no dead ends for the core workflow. Minor gaps remain: there is no single-activity detail tool (laps/splits/streams) and no way to duplicate a workout or manage courses/routes, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing