Skip to main content
Glama
limited

Garmin Open MCP

by limited
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to Garmin Open MCP

No user-submitted related servers found.

    Related Servers

    • garmin-mcp

      aayush-lunawat
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that exposes your Garmin Connect data—sleep, HRV, training readiness, workouts, and more—to any MCP-compatible AI assistant. Runs entirely on your machine and keeps your Garmin credentials private.
      MIT

    • hybridlog

      Imgrund
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that mirrors your Garmin data into a personal database and exposes tools for health summaries, training load, muscle readiness, and race analysis, with optional chat-driven insights via stdio or HTTP.
      1
      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.9/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource or operation: connection status, sync, day summary, sleep, activities list/get, training status, body metrics, trends, period comparison, and recent overview. Even the cached-data tools are clearly separated by their analytical purpose.

    Naming Consistency5/5

    All tools follow a consistent garmin_ prefix with a verb_noun structure (check, sync, get, list). The naming pattern is uniform and predictable, making it easy to infer what each tool does.

    Tool Count5/5

    At 11 tools, the server is well-scoped for a health-data integration. It covers core data access, activity management, analytics, and connection handling without unnecessary bloat or gaps.

    Completeness4/5

    The surface covers major Garmin data domains: daily summary, sleep, activities, body metrics, training status, and cached data analysis. Minor gaps exist (e.g., no explicit hydration or intraday detail endpoints), but the core workflows are complete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources