Skip to main content
Glama
Morozov90

Garmin Training MCP

by Morozov90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Garmin Training MCP

No user-submitted related servers found.

    Related Servers

    • garmin-mcp

      AbhimanyuV04
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides read access to Garmin Connect health and training data (sleep, heart rate, stress, HRV, activities) and supports writes like creating workouts, editing activities, and exporting files.
      -

    • GARMIN Connect MCP

      sheloab
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives any MCP client local access to Garmin Connect sleep and nap data, recovery and Body Battery, training readiness and load, running tolerance, VO2 Max, race predictions, gear mileage and running summaries. It runs over stdio or Streamable HTTP and includes a credential-free demo mode with fictional sample data.
      2
      MIT

    • garmin-mcp

      ronkatz29
      A
      license
      B
      quality
      B
      maintenance
      Enables retrieval of Garmin Connect data such as activities, sleep, heart rate, and body battery levels using unofficial API through MCP tools.
      4
      MIT

    • garmin-mcp

      konstantintutsch
      A
      license
      C
      quality
      B
      maintenance
      Gives AI assistants local, read-only access to your Garmin Connect health and activity data using your normal account login. Enables querying and downloading roughly 260 kinds of data such as activities, sleep, heart rate, stress, body composition, and training metrics without ever modifying your account.
      62
      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

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool maps to a distinct resource: activity listing, single-activity detail, sleep, HRV, and daily summary. The only mild overlap is that get_daily_summary, get_sleep, and get_hrv all return daily wellness data, but the descriptions make the boundaries clear (steps/stress vs. sleep stages vs. HRV averages). list_activities vs. get_activity is a standard, unambiguous list/detail pair.

    Naming Consistency5/5

    All five names follow the same snake_case verb_noun pattern (list_activities, get_activity, get_sleep, get_hrv, get_daily_summary). The singular/plural distinction (list_activities vs. get_activity) matches the collection-vs-single semantics rather than breaking the convention.

    Tool Count4/5

    Five focused read-only tools is a lean but defensible scope for a Garmin data server, and each tool earns its place. It sits at the thin end of the ideal 3-15 range given the breadth of the Garmin domain, but nothing is redundant or filler.

    Completeness3/5

    The read surface covers activities, sleep, HRV, and daily wellness, but notable gaps remain: workout/course data, training status/readiness, stress-only detail, body composition, and device info are absent. Activity samples/GPS are explicitly unsupported and lap retrieval is not guaranteed, creating potential dead ends for agents wanting intra-activity detail.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources