Skip to main content
Glama
rudeayelo

aimharder-mcp

by rudeayelo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to aimharder-mcp

No user-submitted related servers found.

    Related Servers

    • set-and-signal

      aranlucas
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to connect to a privacy-first, self-hostable workout planning and training log, allowing coaching agents to preview and apply program changes while accessing training data through OAuth-protected endpoints.
      AGPL 3.0

    • garmin-mcp

      Sinfjell
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects MCP clients to Garmin Connect data, enabling queries about activities, sleep, heart rate, body battery, and training status.
      1
      MIT

    • intervals-mcp-server

      HduSy
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to access and manage Intervals.icu training data, including activities, calendar events, wellness metrics, power curves, gear, and custom items, with zero-config interactive authentication.
      26 npm
      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

    A4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and the prepare/execute pairs for bookings and activities are well separated by intent. The main risk is the cluster of find_exercise_1rm, get_exercise_1rm, and get_exercise_rm_progression, which all touch 1RM data and could be confused despite differing scopes (search vs known ID vs progression series).

    Naming Consistency4/5

    Names follow a predictable verb_noun snake_case convention (get_*, prepare_*, execute_*, find_*), with the prepare/execute two-phase pattern applied consistently across bookings and activities. Minor deviation: 'find_exercise_1rm' uses a different verb than the otherwise dominant get_* reads, creating a slight inconsistency.

    Tool Count4/5

    18 tools is on the heavier side but each appears to earn its place across distinct domains (bookings, activities, workouts, 1RM reads). The count is justified by the two-phase prepare/execute plus late-cancellation flow, though it sits just above the ideal 3-15 range.

    Completeness4/5

    The surface covers booking creation, cancellation, late cancellation, upcoming/history reads, activity publication/deletion, and personal activity and 1RM retrieval. Coverage is broad and lifecycle-complete for core workflows; minor gaps exist (no explicit waitlist join, no profile/account mutation), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources