Skip to main content
Glama
charlesfrisbee

Garmin Workouts MCP

by charlesfrisbee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Garmin Workouts MCP

No user-submitted related servers found.

    Related Servers

    • Garmin Connect Workouts MCP

      slaat
      A
      license
      A
      quality
      A
      maintenance
      Enables users to describe workouts in plain English and have them created as structured Garmin Connect workouts with pace, HR, power, cadence targets, and repeat blocks. Also provides full workout lifecycle management including listing, updating, deleting, and scheduling to the calendar.
      2
      8
      112 npm
      MIT

    • garmin-mcp

      yashhooda1
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read Garmin activities and create/schedule structured workouts and multi-week training plans directly on Garmin Connect, syncing to your watch with guided prompts.
      1
      MIT

    • garmin-mcp

      yashhooda1
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read Garmin activities and create/schedule structured workouts and multi-week training plans on Garmin Connect, syncing to the user's watch.
      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

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: authentication initiation, authentication status verification, and workout creation. There is no overlap in functionality, and an agent can easily differentiate between them based on their names and descriptions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with 'garmin' as a prefix: authenticate_garmin, check_garmin_auth, create_garmin_workout. The naming is uniform and predictable across the set.

    Tool Count3/5

    With only 3 tools, the set feels thin for a workout management server. While authentication and creation are covered, there are likely gaps such as retrieving, updating, or deleting workouts, which are common operations in this domain.

    Completeness2/5

    The tool surface is significantly incomplete for workout management. It lacks essential operations like getting existing workouts, updating workouts, deleting workouts, or listing workouts, which are critical for a full CRUD lifecycle. Agents will face dead ends when trying to manage workouts beyond creation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources