Skip to main content
Glama
Sign In
finalsurge-mcp

finalsurge-mcp

by pavelzaitsau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to finalsurge-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.
      8
      72 npm
      MIT

    • apple-workouts-mcp

      yashhooda1
      A
      license
      A
      quality
      B
      maintenance
      Lets Claude build structured runs, strength sessions, and multi-week training plans — including race and high-school track blocks — and publish them through a feed that an iPhone app schedules onto the Apple Watch via WorkoutKit. It also reads recent Strava activities and sync status so plans can be sized to real fitness and confirmed as actually on the wrist.
      14
      1
      MIT

    • TriSync

      beburit
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to turn structured training plans into Garmin Connect workouts, schedule them, queue delivery to registered devices, and optionally coordinate timed Google Calendar events with workout summaries.
      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 8 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: list_workouts reads the calendar, get_structured_workout reads the builder, preview/save/restore form an unambiguous write pipeline. The only mild overlap is between get_parsing_rules and get_examples, which are both 'reference material to read before building,' though their descriptions clarify the difference (rules vs. concrete examples).

    Naming Consistency5/5

    All eight tools follow a strict snake_case verb_noun pattern: list_workouts, get_zones, get_parsing_rules, get_examples, get_structured_workout, preview_structured_workout, save_structured_workout, restore_backup. The shared 'structured_workout' stem across preview/save/get reinforces the pipeline.

    Tool Count5/5

    Eight tools is well-scoped for a focused workout-builder server, with no filler. Each tool earns its place: calendar read, three reference reads, builder read, validation, write, and undo.

    Completeness4/5

    The build → preview → save → restore lifecycle is fully covered, including safety nets like backups and overwrite protection. Minor gaps exist: there is no way to create a new planned workout or clear steps without overwriting with new ones, but these are workable around within the stated workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources