Skip to main content
Glama
cygnusb

coros-mcp

by cygnusb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to coros-mcp

No user-submitted related servers found.

    Related Servers

    • intervals-icu-mcp

      eddmann
      A
      license
      A
      quality
      F
      maintenance
      A Model Context Protocol (MCP) server for Intervals.icu integration. Access your training data, wellness metrics, and performance analysis through Claude and other LLMs.
      48
      36
      MIT

    • whoop-mcp

      souravpn
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that gives Claude access to your WHOOP biometric data — recovery, sleep, strain, and workouts.
      34 npm
      MIT

    • Withings MCP Server

      akutishevsky
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server that brings your Withings health data into Claude, allowing natural conversation access to sleep patterns, body measurements, workouts, heart data, and more.
      43
      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
    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

    A3.6/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and the descriptions are careful to distinguish one-off scheduling from reusable templates and raw from cleaned list variants. However, the cluster of scheduling tools (schedule_workout, schedule_strength_workout, schedule_workout_template, add_planned_workout) and the paired raw/non-raw list tools still create some potential for misselection.

    Naming Consistency4/5

    The vast majority of tools follow a clear verb_noun pattern (list_, get_, save_, schedule_, delete_, update_, remove_). Minor inconsistencies exist, such as add_planned_workout vs. schedule_workout and the raw suffix on only some list tools, but overall the naming is predictable and readable.

    Tool Count2/5

    With 26 tools, the server crosses the threshold where the surface feels too heavy for an agent to navigate comfortably. Many tools are individually justified, but the raw variants, cache management utilities, and multiple scheduling entry points add notable bulk.

    Completeness4/5

    The tool set covers the core Coros workflows well: authentication, metrics and sleep retrieval, activity listing/detail, workout template CRUD, scheduled workout create/update/remove, and cache syncing. Minor gaps exist, such as no dedicated create/delete training plan tools or a single planned-activity getter, but raw list and calculate tools provide workarounds.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources