Skip to main content
Glama
yashhooda1

apple-workouts-mcp

by yashhooda1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to apple-workouts-mcp

No user-submitted related servers found.

    Related Servers

    • Garmin Claude MCP

      dxnielcr
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets Claude read a runner's recent activities and wellness signals — sleep, HRV, resting heart rate — and then design, schedule, edit, or delete structured workouts. Planned sessions are written to an intervals.icu calendar that syncs through Garmin Connect onto the user's watch, without exposing Garmin credentials.
      MIT

    • Garmin Claude MCP

      harryllamas
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets Claude read recent Garmin training activities and wellness signals such as sleep, HRV, and resting heart rate, then design and push structured workouts onto the user's calendar for syncing to their watch. Workouts can also be listed, edited, and deleted through natural language.
      MIT

    • tally-workout-mcp

      westvegh
      A
      license
      Not graded
      quality
      C
      maintenance
      Strength-training app Claude can write to: reads real workout history (planned vs actual) and writes planned workouts back into the Tally iOS app. First-party hosted remote MCP server secured with OAuth 2.1 (PKCE + dynamic client registration).
      MIT

    • garmin-claude-mcp

      freddosimooo
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets Claude read your recent Garmin activities and wellness data through intervals.icu, then design, create, update, or delete structured workouts that sync to your watch. Read tools cover training history, sleep, HRV, and upcoming calendar events.
      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.5/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: feed reads (list_scheduled, sync_status), feed mutations (unschedule_workout, clear_scheduled), and creation tools are well separated. The only real overlap is among the plan builders (create_training_plan vs create_marathon_plan vs create_hs_track_plan) — an agent could plausibly reach for the generic plan publisher when a marathon or track block is wanted, though the descriptions do clarify.

    Naming Consistency4/5

    Almost all names are snake_case verb_noun (create_workout, list_scheduled, preview_workout, clear_scheduled). Minor deviations: sync_status is noun-only and pick_random_marathon is verb_adj_noun, but overall the pattern is predictable.

    Tool Count5/5

    14 tools sit comfortably in the ideal band for a workout scheduling/generation server. Each tool covers a genuine capability — read feed, mutate feed, preview, sync, plan generation, catalogue — with no filler.

    Completeness4/5

    Lifecycle coverage is strong: create, preview/validate, list, unschedule single, clear range, plus sync status and plan publishing. Gaps are minor — no explicit get-by-id or update-existing-workout tool, though same-name/date overwrite and unschedule-then-recreate provide workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources