Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by marcelfortmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to garmin-mcp

No user-submitted related servers found.

    Related Servers

    • garmin-mcp

      cadencheng888
      F
      license
      Not graded
      quality
      D
      maintenance
      Connects Garmin watch data to Claude Desktop, allowing users to ask natural language questions about their health and activity data from Garmin Connect.
      -

    • Garmin Health MCP Server

      eversonl
      A
      license
      A
      quality
      D
      maintenance
      Enables Claude Desktop to access and analyze Garmin wearable health data including sleep, HRV, Body Battery, and activity metrics. Users can query their health trends, track recovery, and generate interactive HTML dashboards using natural language.
      9
      7
      MIT

    • garmin-personal-api-mcp

      aaronhaddad
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude to read your own Garmin Connect data—activities and exact pace splits, VO2 max and training effect, sleep, HRV, Body Battery, stress, weight and more—through Garmin's official Personal API, with no password or scraping. Access is read-only and runs entirely on your machine, so you can ask natural-language questions about training and recovery.
      23
      222 npm
      MIT

    • Daash

      Bartolome69
      A
      license
      A
      quality
      B
      maintenance
      Daash connects Garmin Connect to ChatGPT and Claude. Your assistant reads your runs, splits, sleep, HRV, Body Battery and recovery, and writes structured workouts and whole training plans to your Garmin calendar, so they're on your watch at the next sync. Free, hosted, open source. Works on free Claude.
      26
      5
      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

    B3.4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools are clearly separated by domain (daily health, training, fitness, weight, steps, activities, workouts, devices). Some overlap exists, such as steps and heart-rate metrics appearing in both get_daily_health and related history/fitness tools, and whoami vs get_user_profile could be slightly confusing, but the descriptions make the intended boundaries mostly clear.

    Naming Consistency4/5

    The tool names are consistently snake_case and nearly all use a get_ verb prefix, with list_activities as a sensible variant. whoami is the only clear naming outlier, but it is a conventional and readable exception.

    Tool Count5/5

    With 13 tools, the server is well within a reasonable range and each tool maps to a distinct Garmin data area. The grouping is not bloated, and no tool feels redundant purely from a count perspective.

    Completeness4/5

    The surface covers the main read-only Garmin domains: health, training, fitness, body composition, steps, activities, goals, workouts, scheduled workouts, devices, and profile. Minor gaps such as retrieving individual workout or goal details may exist, but core workflows appear covered and agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources