Skip to main content
Glama
garmin-connect-mcp

garmin-connect-mcp

by Samiu1

Related Servers

Alternatives to garmin-connect-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables access to Garmin Connect fitness data through 39 fine-grained tools covering body, heart, sleep, stress, activity, steps, hydration, devices, nutrition, goals, and user profile.
      40
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to read the user's own Garmin data—including activities, sleep, HRV, Body Battery, stress, steps, heart rate, and weight—through Garmin's official Personal API, with all 26 endpoints exposed as read-only tools.
      26
      51 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Provides local, Keychain-secured access to all 26 Garmin Connect Personal API GET endpoints plus 8 summary tools. Enables users to query sleep, HRV, Body Battery, activities, profile, weight, and other connected health data through their own Personal API key.
      34
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to read a user's own Garmin data—including activities, sleep, HRV, Body Battery, stress, steps, heart rate, weight, and more—through 26 read-only tools backed by Garmin's Personal API.
      26
      51 npm
      MIT

    TDQS

    A4.3/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool targets a distinct resource+action: searching activities, fetching one activity, downloading its file, daily multi-metric health, single-metric trends, cycle tracking, HR zones, profile, and auto-detected wellness activities. The only soft overlaps are garmin_get_daily_health vs garmin_get_health_trend (different axes, explicitly cross-referenced) and garmin_get_raw, which duplicates everything but is clearly framed as a last-resort escape hatch.

    Naming Consistency5/5

    All ten tools use the same garmin_ prefix with snake_case verb_noun structure (garmin_search_activities, garmin_get_activity, garmin_download_activity_file). Even the generic escape hatch follows the pattern as garmin_get_raw, so the convention is uniform throughout.

    Tool Count5/5

    Ten tools is squarely in the well-scoped range, and each covers a distinct slice of Garmin Connect data (activities, health, trends, cycle, zones, profile). Nothing feels redundant or padded; garmin_get_raw adds breadth without a proliferation of narrow tools.

    Completeness4/5

    The surface covers the read lifecycle well: discovery, detail, raw file download, per-day and cross-day health metrics, plus user context needed to interpret units. Gaps are mostly write-side (no weight/activity/food logging, no workout upload), which is a reasonable scope for a Garmin data reader but leaves some obvious operations unreachable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues