gym-ops MCP server
Related Servers
Alternatives to gym-ops MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude to safely explore and query a SQLite database through natural language, including listing tables, inspecting schemas, and running read-only SELECT queries.488 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceProvides Claude with SQL access to Hevy workout history and personal training conventions stored in a SQLite database. It enables detailed analysis of exercise progress, volume trends, and muscle group mappings through natural language queries.MIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude to query a live MySQL database using natural language through read-only tools for listing tables, describing schemas, and running SELECT queries.-
- FlicenseNot gradedqualityCmaintenanceExposes any SQLite database as read-only MCP tools for AI assistants, enabling listing tables, describing schemas, and running SELECT queries with filtering, ordering, and pagination.-
- AlicenseNot gradedqualityBmaintenanceProvides tools for Claude to query local Claude Code token usage and cost data, enabling spend analysis and insights through natural language.11 npm1MIT
- FlicenseNot gradedqualityDmaintenanceExposes a SQLite database to AI assistants with structured, read-safe access. Includes five tools for schema exploration, querying, and sampling data.-
TDQS
Scored across 4 tools
get_class_occupancy and find_members are clearly distinct, and list_unpaid_members is a focused snapshot while reconcile_payments is the full matching/reconciliation workflow. The only real overlap is that both list_unpaid_members and reconcile_payments report unpaid/partial bills, so an agent could initially pick the wrong one, but the descriptions clarify the boundary.
Every tool uses a lowercase snake_case verb_noun form, so the set is predictable. However, the query verbs are inconsistent (get_class_occupancy vs find_members vs list_unpaid_members) and reconcile_payments is the only non-query action, so it is not as uniform as a list_/create_/update_ pattern.
Four tools is a reasonable, non-bloated count and each tool is substantive. The 'gym-ops' label is broad enough that one might expect additional tools, and list_unpaid_members partially overlaps with reconcile_payments, so the scope feels slightly under- or over-represented rather than perfectly curated.
The tools work well for historical class occupancy, member lookup, unpaid-bill reporting, and payment reconciliation. They do not cover future class schedules, member-specific payment histories, or any create/update/freeze/cancel operations, which are common gym operations workflows, so agents will hit dead ends for those requests.