openGym MCP Bridge
Related Servers
Alternatives to openGym MCP Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables querying a Tonal fitness account for workout history with per-set weights, muscle readiness, strength scores, and lifetime stats through a remote MCP endpoint.MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseCqualityCmaintenanceEnables 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.36MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
Scored across 22 tools
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.
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.
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.
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.