Skip to main content
Glama
Mason-Levyy

garmin-personal-mcp

by Mason-Levyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to garmin-personal-mcp

No user-submitted related servers found.

    Related Servers

    • Garmin MCP Server

      jbaker48
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects to Garmin Connect and exposes fitness and health data (activities, steps, heart rate, sleep, body composition) to MCP-compatible clients like Claude.
      MIT

    • Garmin MCP Worker

      wesleysui
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only remote MCP server that lets Claude query your own Garmin Connect data — sleep, HRV, Body Battery, stress, heart rate, and activities — through Garmin's official Personal API. It runs on Cloudflare Workers with OAuth sign-in, so it works from both the Claude mobile app and desktop.
      MIT

    • Garmin Connect MCP

      LePomas
      A
      license
      B
      quality
      D
      maintenance
      Exposes personal Garmin Connect data to MCP-capable clients like Claude and Gemini. Enables querying daily stats, heart rate, sleep, activities, and managing workouts.
      16
      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 26 tools

    Disambiguation4/5

    Most tools target a distinct metric or resource, and descriptions make boundaries explicit. The weakest points are the plural-pair patterns (garmin_get_daily_summary vs garmin_get_daily_summaries, garmin_get_sleep vs garmin_get_sleep_summaries) and garmin_get_day, which aggregates data that several dedicated tools also return, so an agent could misselect.

    Naming Consistency4/5

    Nearly all tools follow garmin_<verb>_<noun> with get_/search_/download_ prefixes, so the pattern is predictable. The only friction is that single-day vs range variants differ only by a trailing plural (get_daily_summary/get_daily_summaries), which is consistent but easy to overlook.

    Tool Count3/5

    26 tools is on the heavy side and each covers a separate Garmin metric. The domain is broad enough that most tools earn their place, but the range/single-day pairs and aggregate get_day add surface area that could be consolidated.

    Completeness4/5

    Coverage across wellness, sleep, activity, nutrition, cycle, and profile data is broad, with sensible read-only lifecycle (search then get detail). Gaps exist in areas like training readiness/VO2 max, workout library, and any write-back operations, but core agent workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources