Skip to main content
Glama
openGym MCP Bridge

openGym MCP Bridge

by Nirvana-Z777

Related Servers

Alternatives to openGym MCP Bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants and native clients to manage training plans, workout history, reusable recipes, meal records, and media through validated, versioned MCP and REST operations. It stores and validates structured fitness and nutrition data, including nutrition calculation, food catalog lookup, and Apple Health export status.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to read and modify a user's nutrition-tracking account: the full diary across foods, exercise, notes, biometrics and targets, plus coverage-aware nutrient totals that report unreported values as an "at least" floor instead of zero. Writes such as logging, editing, deleting or copying entries require per-action approval, with deletes needing explicit confirmation and an optional read-only mode that removes them entirely.
      68 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Codex and Claude Code to securely read and manage a personal Cronometer account, including food logs, nutrient summaries with missing-data awareness, food search, biometrics, and export analysis.
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables MCP clients to control playback and queues, search and discover tracks, manage saved items and followed artists, and perform bulk playlist edits, including dry-run previews for destructive operations.
      36
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables conversational logging and retrieval of workouts, sets, weigh-ins, meals, goals, plans, and progress photos through MCP-capable AI clients, with authenticated per-user storage and export/query capabilities.
      ISC

    TDQS

    B3.3/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target distinct resources or operations, and the preview_* tools are separated by domain. However, the generic fetch and search tools overlap conceptually with specialized tools such as get_plan, get_summary, get_recent_workouts, and list_workouts, so some misselection is possible.

    Naming Consistency4/5

    The set is overwhelmingly consistent snake_case with predictable verb_noun patterns such as get_plan, list_workouts, and preview_workout_edit. The standalone names fetch and search are generic exceptions, but the overall convention remains clear.

    Tool Count3/5

    The domain is broad, covering plans, workouts, drafts, custom exercises, history, and summaries, so 22 tools is not absurd. Still, it sits in the heavy/borderline range, and several read-only or preview variants could likely be consolidated.

    Completeness2/5

    Read coverage is extensive across plans, workouts, drafts, history, progress, and custom exercises. But the mutation lifecycle appears incomplete: plan changes, workout logging, custom exercise changes, workout edits, and draft finishing all exist only as dry-run previews with no apply/commit tool, creating dead ends for actual writes.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing