Skip to main content
Glama
garmin-connect-mcp

garmin-connect-mcp

by KaiTries

Related Servers

Alternatives to garmin-connect-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      B
      quality
      B
      maintenance
      Enables Claude or any MCP client to read your own Garmin Connect health data — sleep, HRV, heart rate, stress, Body Battery, weight, nutrition, and activities — through Garmin's official, key-based read-only Personal API with no password login or scraping. Activity tools pull the original FIT files to provide laps, computed splits, time in heart-rate zones, and session stats.
      25
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables ChatGPT and compatible AI clients to query read-only Garmin Connect data—including sleep, HRV, heart rate, Body Battery, wellness metrics, and activities—through a hosted OAuth-backed MCP connection using a personal API key.
      2
      15
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects Garmin Connect to AI assistants, answering questions about training, sleep, HRV and recovery with metrics computed in code rather than guessed from raw JSON. Queries daily readiness, training load, activity FIT analysis and personal records through a self-hosted Cloudflare Worker with OAuth.
      16 npm
      8
      MIT

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: list_activities vs get_activity, get_training_summary, get_body_composition, get_nutrition, and get_profile are easy to tell apart. The main overlap is get_recovery vs get_day_detail, since both surface sleep, HRV, and Body Battery data, though the range-vs-single-day distinction helps. garmin_api_get is an intentional escape hatch with explicit usage guidance.

    Naming Consistency4/5

    Eight of nine tools follow a consistent snake_case verb_noun pattern using get_ or list_ prefixes. garmin_api_get is a minor deviation, but it still uses snake_case and signals its special escape-hatch role. Overall naming is predictable and readable.

    Tool Count5/5

    Nine tools is well-scoped for a read-only Garmin Connect data server. Each tool covers a distinct data area—recovery, day detail, activities, training, body composition, nutrition, profile—and the escape hatch adds flexibility without bloating the set. No tool feels redundant or superfluous.

    Completeness4/5

    The surface covers the core health/fitness domains: recovery, sleep, HRV, activities, training load, body composition, nutrition, and profile. Minor gaps exist for less common metrics like SpO2, fitness age, and goals, but garmin_api_get provides a documented escape hatch for those cases. This is broadly complete for typical agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues