Skip to main content
Glama
marcelfortmann

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
      C
      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
      6
      MIT

    • garmin-mcp

      Bartolome69
      A
      license
      A
      quality
      B
      maintenance
      Connects Claude to your Garmin Connect account to read activities, health metrics, and sleep data, and to create and schedule structured workouts directly onto your watch, all locally without exposing credentials.
      8
      2
      MIT

    • garmin-mcp

      Lander-garmin
      A
      license
      B
      quality
      B
      maintenance
      Enables Claude to access and query your Garmin Connect data—sleep, training, heart rate, and more—through a suite of read-only tools, with an optional write path for creating strength workouts.
      63
      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.3/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct Garmin data domains with metric parameters that clarify scope. However, get_daily_health and get_steps_history overlap on step data, and get_training/get_fitness both cover performance metrics, so a few boundaries could still be confused.

    Naming Consistency4/5

    The set is almost entirely consistent snake_case with a get_* verb-noun pattern for 11 of 13 tools. list_activities and whoami are minor deviations, but overall the naming is predictable and readable.

    Tool Count5/5

    13 tools is well-scoped for a Garmin health/fitness server. Each tool maps to a clear category (health, training, fitness, weight, steps, activities, devices, profile, goals, workouts, scheduling) without excessive fragmentation.

    Completeness4/5

    The read-only surface covers the major Garmin data lifecycle: health, training, activities, workouts, goals, devices, profile, and scheduling. Minor gaps exist (no separate sleep endpoint, no write/delete operations), but these are likely API limitations and agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources