Skip to main content
Glama
sovnheim

garmin-mcp

by sovnheim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to garmin-mcp

No user-submitted related servers found.

    Related Servers

    • garmin-unofficial-mcp

      Danielsuri
      A
      license
      Not graded
      quality
      B
      maintenance
      A local, read-only MCP server that gives Claude access to your Garmin health and training data, exposing tools for health snapshots, training status, run details, body metrics, and training analysis.
      MIT

    • garmin-connect-mcp

      jharkebusch
      A
      license
      A
      quality
      C
      maintenance
      MCP server that connects Garmin Connect to Claude Desktop, allowing users to query health and fitness data (sleep, workouts, heart rate, HRV, stress, Body Battery, etc.) in plain English and also log weight, hydration, and schedule workouts.
      25
      MIT

    • garmin-mcp

      Danielsuri
      A
      license
      Not graded
      quality
      B
      maintenance
      A local, single-user, read-only MCP server that gives Claude Code access to your Garmin health and training data, exposing tools for health snapshots, training status, run details, body metrics, and training analysis.
      1
      MIT

    • garmin-mcp

      TeoFil795
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server exposes Garmin Connect health data—sleep, heart rate, HRV, stress, VO2max, and activities—to Claude through local tools, enabling natural language queries, data syncing, and statistical analysis like correlations and night-out detection.
      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.6/5.0

    Scored across 25 tools

    Disambiguation4/5

    Each tool targets a distinct Garmin data resource (activities, sleep, HRV, workouts, plans). A few metrics overlap—get_heart_rate vs get_resting_heart_rate and daily stats including resting HR—but descriptions clarify the unit (intraday day vs range trend). No two tools are truly interchangeable.

    Naming Consistency5/5

    All tools follow a consistent get_/list_ + noun pattern, with clear singular/plural distinctions like get_scheduled_workout vs get_scheduled_workouts. The few compound names (get_cycling_ftp, get_lactate_threshold) are readable and fit the pattern.

    Tool Count3/5

    25 tools is at the heavy end of the range; each represents a specific endpoint but the set could be streamlined (e.g., range-based metrics could share a generic pattern). Still, the count is justified by Garmin's many distinct data categories and remains navigable.

    Completeness4/5

    The read-side surface is broad: activities, daily wellness, training metrics, workouts, scheduled workouts, and training plans are all covered. Missing write/management operations (activity uploads, workout creation, plan enrollment) and some niche metrics keep it from a 5.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources