Skip to main content
Glama
Tyler-Irving

garmin-mcp

by Tyler-Irving
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to garmin-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • garmin-mcp

      holdenstirling
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to read Garmin Connect data such as activities, sleep, HRV, VO2 max and training readiness, and optionally view or manage TrainingPeaks workouts and sync them to a watch, over streamable HTTP secured with MCP OAuth 2.1 and GitHub login.
      MIT

    • garmin-mcp

      wiande00
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude and other MCP clients to query Garmin Connect health, training, activity, and body data, analyze FIT files, and create structured workouts that sync to a Garmin watch.
      MIT

    • garmin-mcp

      alyssindewonderland
      A
      license
      B
      quality
      B
      maintenance
      Connects Claude to a personal Garmin Connect account so users can ask natural-language questions about sleep, HRV, body battery, stress, heart rate, training readiness and activities, and optionally create or schedule workouts and log weigh-ins. Reads are returned as trimmed summaries with optional full JSON, and writes stay disabled unless explicitly enabled.
      24
      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.7/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most get_* tools target distinct metrics (sleep, HRV, body battery, stress, etc.), but some overlap exists: get_sleep includes overnight HRV, and get_daily_briefing explicitly fuses six other tools. Descriptions are detailed enough to disambiguate, but an agent could hesitate between the composite and individual tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case: get_* for read operations, preview_*/create_* for workout creation, delete_workout, schedule_workout/unschedule_workout. Nearly every tool name clearly indicates its action and resource, with no mixed conventions.

    Tool Count2/5

    With 28 tools, the server exceeds the 25+ threshold for 'too many'. While the Garmin domain is broad, many tools could be consolidated (e.g., get_daily_briefing already combines six), and the count feels heavy for an agent to navigate efficiently.

    Completeness4/5

    The surface covers a wide range of health metrics and workout CRUD (preview, create, list, delete, schedule/unschedule). Minor gaps exist: no workout update (only delete and recreate) and no detailed view of a single workout template's steps, but core workflows are well-supported.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources