Skip to main content
Glama
flyyata

garmin-china

by flyyata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to garmin-china

No user-submitted related servers found.

    Related Servers

    • mcp-garmin

      StefanOOE
      A
      license
      C
      quality
      B
      maintenance
      Enables access to Garmin Connect fitness data through 39 fine-grained tools covering body, heart, sleep, stress, activity, steps, hydration, devices, nutrition, goals, and user profile.
      40
      MIT

    • Garmin MCP Server

      JJRPF
      A
      license
      B
      quality
      B
      maintenance
      Connects to Garmin Connect and exposes fitness and health data via 110+ tools for activities, health metrics, workouts, training analytics, and more to MCP-compatible clients.
      138
      MIT

    • garmin-cn-mcp

      anthony11122
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read Garmin Connect China health and fitness data, including activities, sleep, HRV, stress, SpO2, respiration, badges, and gear, via the Model Context Protocol.
      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

    • garmin-mcp-triathlon

      pluton74mac
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables triathlon coaches and athletes to interact with Garmin Connect, including retrieving health/activity data, building and uploading structured workouts (cycling, running, swimming, brick), and accessing coaching analytics like readiness, load, and performance trends.
      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

    C2.3/5.0

    Scored across 55 tools

    Disambiguation3/5

    Many tools exist for activities (e.g., activities, last_activity, activity_detail, get_activity, get_activity_splits, etc.) and weather (weather_now, weather_forecast, weather_at, etc.), causing confusion. However, descriptions are detailed enough to distinguish most, though some overlap remains (e.g., steps_data vs daily_steps).

    Naming Consistency2/5

    Naming is inconsistent: some tools use plain nouns (sleep, stress, weight), others use snake_case with 'get_' prefix (get_hill_score, get_workout_templates), and a few use inconsistent patterns (garmin_weekly_health, garmin_run_conditions). No clear convention across the set.

    Tool Count3/5

    55 tools is high for a single server, but the domain is broad (health metrics, activities, weather, training). Some tools could be consolidated (e.g., multiple activity detail tools), but the count is borderline appropriate for a comprehensive Garmin data interface.

    Completeness4/5

    The server covers a wide range of health metrics, activities, workouts, weather, and training analysis. It lacks write/update tools (e.g., create activity, edit workout) but is thorough for read-only queries. Minor gaps like missing workout creation or editing are acceptable for a data retrieval-focused server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources