Skip to main content
Glama

Related Servers

Alternatives to speediance-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to securely read your own WHOOP account data — recovery, HRV, resting heart rate, sleep, strain, workouts and body profile — through the official WHOOP developer API on a self-hosted server. Supports natural-language questions such as whether you are ready to train hard today.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A personal remote MCP server that lets Claude read your Hevy workout data and MacroFactor nutrition data directly in conversation, with read-only tools for workouts, body measurements, macros, and weight trends.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude to a Hevy account so it can analyze synced workout history, volume, personal records, and muscle balance, then draft and save routines and multi-week programs back into Hevy with confirmation. Runs as a free Cloudflare Worker custom connector, with read-only workout access and previews before any routine change is written.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides Claude with real-time access to local health data including sleep, recovery, strain, and workouts from WHOOP and Apple Health, enabling informed context-aware interactions.
      6
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Connect Garmin to Claude or ChatGPT. Ask about your runs, sleep and recovery, and put structured workouts and whole training plans on your watch. Run it locally, or use Daash's hosted server with OAuth: no install.
      8
      3
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to read Hevy training data—workouts, routines, exercise templates, and history—and create or update routines through a self-hosted custom connector.
      3,849 npm
      -

    TDQS

    A3.6/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (workout CRUD, calendar, analytics, library, fact management). Minor overlaps exist: schedule_workout with add=false duplicates unschedule_workout, and get_athlete_snapshot overlaps get_preferences/get_training_stats, but descriptions explicitly clarify the boundaries. An agent can reliably tell tools apart.

    Naming Consistency5/5

    All 29 tools use a consistent snake_case verb_noun pattern (list_my_workouts, get_session_detail, create_workout, remember_fact, etc.). No camelCase or mixed-convention outliers. Predictable and readable throughout.

    Tool Count3/5

    29 tools is heavy for the rubric's ideal range, though the server spans several genuinely broad domains (workout CRUD, calendar/sessions, analytics, exercise library, and a full fact/memory subsystem). Each tool is defensible, but the surface is large enough to feel sprawling, and the fact subsystem alone consumes five tools.

    Completeness5/5

    Coverage is exceptional: full workout CRUD plus scheduling, calendar and session detail, heart rate, multiple analytics tools, complete exercise-library browse/detail/mark/history, accessories, preferences get/set, and a full fact lifecycle (remember/forget/list/import with audit and supersede chains). No obvious dead ends for the stated coaching purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues