Skip to main content
Glama

Related Servers

Alternatives to garmin-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      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
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables read-only access to the official Garmin Connect Personal API so users can explore activities, workouts, and health metrics such as sleep, HRV, stress, and Body Battery through MCP clients over stdio or local Streamable HTTP.
      6
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides MCP clients with read-only access to a user's Garmin Connect health, activity, sleep, body, and profile data through Garmin's official Personal API, with shaped summaries, aggregations, and decoded FIT files.
      MIT

    TDQS

    A4.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct metric or resource (steps, sleep, HRV, stress, activities, etc.), with clear usage guidance in descriptions. Even overlapping tools like daily_summary and health_snapshot are differentiated by purpose (activity vs recovery), and the escape-hatch api_request is explicitly subordinated to dedicated tools.

    Naming Consistency4/5

    The vast majority follow a consistent garmin_ get_<noun> pattern, and list_activities is a natural exception. The only real outlier is garmin_api_request, which breaks the verb_noun convention but is a generic escape hatch rather than a resource-specific operation.

    Tool Count5/5

    14 tools is well within the ideal range. The set covers a broad health/fitness domain with dedicated tools for the most common queries, and the single escape hatch prevents the count from exploding into dozens of niche endpoints.

    Completeness5/5

    The dedicated tools cover all major data categories (daily summary, sleep, HRV, stress, heart rate, readiness, body battery, steps, body composition, activities), and the api_request tool provides access to the remaining ~130 endpoints. This ensures no dead ends while keeping the primary surface focused.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data