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
      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 MCP clients to access a Garmin Connect account read-only, including activities, sleep, heart rate, and training metrics, with bearer-token or OAuth authentication.
      BSD Zero Clause
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides MCP clients with read-only access to a user's Garmin Connect health, activity, sleep, body, and profile data through Garmin's official Personal API, with shaped summaries, aggregations, and decoded FIT files.
      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
      A
      quality
      B
      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
      89 PyPI
      2
      MIT

    TDQS

    B3.1/5.0

    Scored across 157 tools

    Disambiguation3/5

    The set includes many near-duplicate pairs (e.g., get_sleep_summary vs get_sleep_data, get_stats vs get_user_summary vs get_stats_and_body, get_workouts vs get_scheduled_workouts vs get_garmin_coach_workouts), but most descriptions explicitly distinguish full-data vs summary and recommend one tool over another. However, with 157 tools, there are still multiple boundary cases an agent could easily misselect (e.g., the several workout-creation helpers, the two badge-challenge tools, and the get_activities variants).

    Naming Consistency4/5

    The dominant pattern is consistent snake_case verb_noun (get_*, set_*, add_*, delete_*, create_*, upload_*, download_*, schedule_*, unschedule_*). There are minor deviations such as get_userprofile_settings, get_activities_fordate, get_rhr_day, get_hrv_data, get_vo2max_trend, and the explicit get_training_plan_workouts alias, but these do not break readability.

    Tool Count1/5

    157 tools is far beyond a reasonable scoped surface, even for a broad health-and-fitness platform. Many domains (sleep, stress, activities, workouts, nutrition, devices, courses, gear, badges) are covered, but the sheer volume makes discovery and selection costly for an agent.

    Completeness4/5

    The surface is extremely comprehensive: CRUD for activities, workouts, nutrition, weight, courses, and many setters for activity metadata, plus extensive read coverage for devices, badges, goals, and trends. Minor gaps exist (e.g., no delete for body-composition/hydration/blood-pressure entries, no update-course, no gear creation), but agents can usually work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues