Skip to main content
Glama
NoaMatout

garmin-mcp

by NoaMatout
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to garmin-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • catence

      rifusaki
      A
      license
      B
      quality
      A
      maintenance
      MCP server for local fitness-data extraction and analysis from Garmin Connect, Intervals.icu, and Strava. Provides read-only analytical tools over DuckDB and targeted Strava enrichment.
      35
      271 npm
      AGPL 3.0

    • caddie-mcp

      mbrionesalvarez
      A
      license
      A
      quality
      C
      maintenance
      MCP server that connects Claude or any MCP-capable LLM to your Garmin golf data, enabling natural-language queries on rounds, shots, strokes gained, club distances, course intel, and health-performance correlations from a private local DuckDB cache.
      13
      MIT

    • 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

    • fitMCP

      gzarog
      F
      license
      Not graded
      quality
      D
      maintenance
      A multi-platform fitness MCP server that syncs data from Garmin, Strava, Google Fit, and Suunto into a local DuckDB database and provides analytics tools via MCP.
      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

    A4.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: activity retrieval, streams, weekly aggregation, comparison, workout creation/deletion, sync, and database status. No two tools overlap in functionality, so an agent can reliably select the correct one.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (list_activities, create_workout, get_activity_detail), but weekly_summary and database_status are noun phrases, and sync_now is verb+adverb. The mixed style is still readable and predictable, but not perfectly uniform.

    Tool Count5/5

    Nine tools is well within the ideal 3-15 range. Each tool covers a distinct operation needed for a Garmin data server, and none feel redundant or unnecessary.

    Completeness4/5

    Activity data is comprehensively covered: list, detail, streams, weekly summary, and comparison. Workout creation and deletion are present, but there is no way to list or update existing workouts, which is a minor gap for managing a workout library. Sync and status tools round out the surface well.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources