Skip to main content
Glama
konstantintutsch

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to garmin-mcp

No user-submitted related servers found.

    Related Servers

    • garmin-owl

      xichen-de
      A
      license
      A
      quality
      A
      maintenance
      Enables local, read-only access to Garmin Connect health and training data through MCP, letting assistants summarize recovery, sleep, activities, and more without uploading your data.
      24
      MIT

    • garmin-mcp

      shawnduggan
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query live Garmin Connect health and fitness data, including daily metrics, activities, sleep analysis, and trends via natural language.
      MIT

    • GC-MCP

      macakdev
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to access and query Garmin Connect health and fitness data, including sleep, HRV, training load, and activities, with an optional coaching plugin for personalized training plans.
      5 npm
      4
      -

    • garmin-mcp

      mskerwiderski
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables reading and analyzing Garmin Connect data—activities, health metrics, FIT files, and challenges—through natural language, for AI assistants like Claude and ChatGPT.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 62 tools

    Disambiguation2/5

    Many tools overlap heavily: get_daily_heart_rate_stats vs get_heart_rates vs get_rhr_day; get_daily_stress_stats vs get_stress_data; get_steps_data vs get_daily_steps; and several activity-detail variants (get_activity, get_activity_details, get_activity_splits, get_activity_typed_splits, get_activity_split_summaries). Descriptions help in places, but an agent can easily choose the wrong endpoint for the same underlying data.

    Naming Consistency3/5

    Most tools follow a get_<noun> snake_case pattern, but there are noticeable deviations: garmin_api_get, garmin_list_methods, garmin_call, download_activity, and get_today break the dominant convention. Minor inconsistencies like get_fitnessage_data and get_weigh_ins also reduce predictability.

    Tool Count2/5

    62 tools is excessive for a read-only data server, especially because many endpoints are near-duplicates and generic escape hatches (garmin_api_get, garmin_call, garmin_list_methods) already cover undocumented data. Consolidation would make the surface far easier to navigate.

    Completeness4/5

    For a read-only Garmin Connect surface, coverage is broad: daily metrics, activities, sleep, body composition, training status, devices, goals, badges, raw API access, and downloads are all present. Some niche domains rely on the generic fallback rather than dedicated tools, but there are few obvious hard dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources