Skip to main content
Glama
JJRPF

Garmin MCP Server

by JJRPF
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Garmin MCP Server

No user-submitted related servers found.

    Related Servers

    • garmin-mcp

      zwisler-a
      F
      license
      Not graded
      quality
      B
      maintenance
      Exposes Garmin Connect health and activity data (steps, sleep, heart rate, etc.) via MCP tools, with built-in login and MFA support.
      -

    • health-mcp

      jonathan249
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes personal Garmin wellness data through MCP tools for accessing summary, sleep, HRV, heart rate, stress, body battery, and historical data.
      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

      gabecorsini
      A
      license
      Not graded
      quality
      C
      maintenance
      Personal MCP server for interacting with your Garmin Connect data. Exposes 62 tools across 11 domains including activities, health, training, and workouts.
      1
      MIT

    • Garmin MCP Server

      jaounial
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects to Garmin Connect to expose fitness and health data to MCP-compatible clients, enabling activity management, health metrics, training analytics, workout creation, and more via natural language.
      MIT

    • garmin-mcp

      Sinfjell
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects MCP clients to Garmin Connect data, enabling queries about activities, sleep, heart rate, body battery, and training status.
      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.1/5.0

    Scored across 138 tools

    Disambiguation2/5

    The set contains multiple overlapping clusters: get_activities/get_activities_by_date/get_activities_fordate, get_stats/get_user_summary/get_stats_and_body, several full-vs-summary metric pairs, and an explicit duplicate alias in get_training_plan_workouts vs get_garmin_coach_workouts. Detailed descriptions help, but agents will often have to guess which of several near-synonymous getters returns the data they need.

    Naming Consistency2/5

    Most tools follow a get_* pattern, but consistency breaks down with names like get_activities_fordate, get_userprofile_settings, set_perceived_effort vs set_activity_feel, and get_weigh_ins vs add_weigh_in. The mix of get/add/set/create/upload/log/upsert verbs across related operations makes the naming convention unpredictable.

    Tool Count1/5

    138 tools is an extreme count, well beyond the 50+ threshold for a low score. While Garmin's API surface is broad, this many tools could be consolidated into domain-focused tools with parameters instead of exposing one tool per endpoint variant.

    Completeness4/5

    The tool surface covers virtually all Garmin Connect domains: activities, health metrics, devices, workouts, nutrition, courses, challenges, body composition, and more, with CRUD coverage for most areas. Minor gaps exist such as no delete-activity tool and no course update, but core workflows do not hit dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources