Skip to main content
Glama
obrien-matthew

mcp-garmin

by obrien-matthew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-garmin

No user-submitted related servers found.

    Related Servers

    • mcp-server-garmin

      borgels
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Garmin Connect that enables users to access and manage their personal health and fitness data, including daily summaries, heart rate, sleep, HRV, stress, body composition, activities, and training readiness, with secure per-user authentication.
      Apache 2.0

    • garmin-mcp

      nbaradar
      F
      license
      A
      quality
      C
      maintenance
      Provides read-only access to your Garmin Connect health data, including sleep, HRV, body battery, stress, training readiness, and activities, through an MCP server.
      14
      -

    • garmin-connect-mcp

      epodivilov
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides comprehensive access to Garmin Connect data including sleep analytics, health metrics, activities, and training volume analysis.
      16
      44 npm
      6
      MIT

    • Garmin MCP

      lokranjanp
      A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes Garmin Connect health and activity data (steps, sleep, stress, activities, etc.) via tools for querying, analysis, and visualization.
      17
      Apache 2.0
    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.5/5.0

    Scored across 32 tools

    Disambiguation5/5

    Each tool has a distinct and well-defined purpose, with clear differentiation among activity sub-tools (details, splits, gear, etc.) and between list/single retrieval functions. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools follow a consistent 'get_<specific_data>' pattern using snake_case, with no mixing of conventions or verb styles. This makes the tool set highly predictable.

    Tool Count4/5

    32 tools is on the higher side, but given the comprehensive nature of Garmin data (many distinct metrics like HRV, SpO2, body battery, etc.), the count is justifiable for a read-only data retrieval server. Slight over-scoping but not excessive.

    Completeness5/5

    The server covers virtually all major Garmin data categories: activities (with detailed breakdowns), daily summaries, body metrics, sleep, heart rate, stress, training readiness, and more. No obvious gaps for a read-only interface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources