Skip to main content
Glama
DynamicsNinja

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to garminconnect-js

No user-submitted related servers found.

    Related Servers

    • GC-MCP

      macakdev
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to access and query Garmin Connect health and fitness data, including sleep, HRV, training load, and activities, with an optional coaching plugin for personalized training plans.
      4 npm
      4
      -

    • garmin-mcp

      shawnduggan
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query live Garmin Connect health and fitness data, including daily metrics, activities, sleep analysis, and trends via natural language.
      MIT

    • Slipstream Extended

      svein-vindler
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to privately explore personal Garmin history, including activities, health metrics, HRV, sleep, and strength training, through self-hosted infrastructure.
      MIT

    • garmin-givemydata

      nrvim
      A
      license
      B
      quality
      A
      maintenance
      Downloads all your Garmin health and fitness data into a local SQLite database and exposes 45 MCP tools for AI analysis, enabling assistants to query sleep, training load, HRV, and more.
      48
      183 PyPI
      158
      AGPL 3.0

    • garmin-mcp

      marcelohensantos
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Garmin Connect data and workout management to AI agents, supporting tools, resources, and prompts for health data, workout creation, and coaching workflows.
      1
      -
    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.5/5.0

    Scored across 190 tools

    Disambiguation2/5

    With 190 tools, several have overlapping or aliased purposes, such as get_stats/get_user_summary and get_stress_data/get_all_day_stress, which can confuse selection. Many descriptions are detailed, but the sheer breadth and near-duplicate activity/summary endpoints create unclear boundaries.

    Naming Consistency4/5

    Tool names are overwhelmingly snake_case with predictable verb_noun patterns like get_, create_, update_, delete_, and set_. Minor deviations exist, including noun-only accessors like display_name and user_name, plus state-style names like has_connect_plus.

    Tool Count1/5

    A 190-tool surface is far beyond a well-scoped MCP server and is extremely heavy for an agent to navigate. Even for a broad Garmin Connect API wrapper, this count creates severe selection and maintenance overhead.

    Completeness4/5

    The surface is remarkably complete across activities, wellness, nutrition, workouts, courses, gear, badges, challenges, menstrual data, devices, and calendar events. Minor gaps remain, such as no delete or update path for some read-only domains like hydration and goals.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources