Skip to main content
Glama
nrvim

garmin-givemydata

by nrvim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to garmin-givemydata

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

    • GarminSynapse

      kaivyy
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to retrieve and analyze Garmin Connect health data, including daily summaries, sleep, HRV, workouts, and raw FIT files, while also supporting SQL queries on the underlying database.
      8
      -

    • Garmin Local Archive

      Wewoc
      A
      license
      A
      quality
      A
      maintenance
      Archives Garmin Connect health data locally (steps, HR, sleep, body battery) as JSON, no cloud, and also pulls context data (weather, pollen, air quality). Built-in MCP server (with SQLite cache) exposes the archive for querying via LLM tool calls.
      7
      22
      GPL 3.0

    • 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

    • health-mcp

      jonathan249
      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
    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

    B3.1/5.0

    Scored across 48 tools

    Disambiguation3/5

    Many tools have clearly distinct purposes, but significant overlap exists among metric-specific tools (e.g., garmin_heart_rate vs garmin_hrv vs garmin_hr_zones; garmin_body_battery vs garmin_stress vs garmin_respiration). The presence of catch-all tools like garmin_query and garmin_health_summary alongside specialized ones increases ambiguity about when to use which.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with the 'garmin_' prefix, making names predictable and easy to recognize as a cohesive set.

    Tool Count2/5

    48 tools is excessive for a personal health data server, likely overwhelming an agent and causing selection confusion. While the domain is broad, the surface is bloated with many highly specific metrics that could be consolidated.

    Completeness4/5

    The toolset covers nearly every Garmin Connect data type: activities, sleep, stress, body battery, training metrics, nutrition, gear, and more. Some gaps remain (e.g., no explicit write/update operations, but those may be out of scope for a read-only client), but overall coverage is extensive.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources