gym-ops MCP server
Related Servers
Alternatives to gym-ops MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables LLM clients to explore and query a local SQLite database through read-only, typed tools for table listing, schema inspection, ad-hoc SQL, customer lookup, and sales summaries.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Desktop or Cursor to inspect a coffee-shop sales database schema, validate SQL, and run guarded read-only queries. It supports natural-language questions by exposing tools for schema description, SQL checking, and safe query execution.MIT
- 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.1,339 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other MCP clients to inspect a local SQLite database's tables, columns, and schema, and run safe read-only SQL queries with capped JSON results.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude and other MCP clients to map a SQLite database's schema and run read-only SQL queries against it, with writes blocked at the SQLite level through multiple enforcement layers. Results come back as context-friendly Markdown tables with row caps and a query timeout.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to find gyms and studios, check schedules and prices, start trial classes, and, after OAuth sign-in, view, book, or cancel classes with a membership. Public tools require no account, while member tools enforce each gym's booking rules and never pass payment data to the assistant.MIT
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.