Skip to main content
Glama
elias-ramzi

ClaudeCyclingMCP

by elias-ramzi

Related Servers

Alternatives to ClaudeCyclingMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for intervals.icu that reads training data (activities, wellness, calendar) and creates structured workouts on the calendar, which are pushed to devices like Garmin, Wahoo, Zwift, Coros, Suunto via the official API.
      19 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables creating, previewing, scheduling, and managing Garmin Connect workouts, plus reading activities and health metrics, all through a local MCP server.
      11
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for Intervals.icu that enables AI assistants to manage athletic training data, including activities, calendar events, wellness metrics, and workout libraries.
      19
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for TrainingPeaks that reads workouts, fitness metrics (CTL/ATL/TSB), and health data, and creates/updates/deletes planned workouts. Enables AI-powered training plan management and automated adjustment based on performance, fatigue, and injury.
      -
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server for interacting with the Wahoo Cloud API to manage workouts, routes, training plans, and power zones. It enables users to list, retrieve, and create fitness data through secure OAuth 2.0 authentication.
      9
      7
      GPL 3.0
    • A
      license
      B
      quality
      B
      maintenance
      Local MCP server for analyzing Intervals.icu accounts, creating AI-assisted training plans, and applying managed drafts to the calendar after explicit confirmation.
      14
      AGPL 3.0

    TDQS

    A4.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: validation, human-readable description, ZWO rendering, Garmin rendering, upload verification, and schema retrieval. The two render tools differ by target format, and validate_spec vs describe_spec are complementary (errors vs computed values), leaving no ambiguity.

    Naming Consistency4/5

    All tool names use lowercase with underscores and mostly follow a verb_noun pattern (validate_spec, describe_spec, render_zwo, render_garmin, verify_garmin_upload). The only exception is spec_schema, a noun phrase rather than an imperative verb, which is a minor deviation from the otherwise consistent pattern.

    Tool Count5/5

    Six tools is well-scoped for a workout spec server. Each tool earns its place, covering the full authoring workflow without redundancy or bloat.

    Completeness5/5

    The surface covers the complete lifecycle: schema reference (spec_schema), validation (validate_spec), visualization (describe_spec), rendering to two target formats, and post-upload verification. There are no obvious gaps for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues