aimharder-mcp
Related Servers
Alternatives to aimharder-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables MCP clients to read account status, plans, and recent workouts, search official exercise names, and, when writes are enabled, apply confirmed preview-first plan changes and historical workout logs.22MIT
- 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
- AlicenseAqualityBmaintenanceEnables an AI client to query one AimHarder account for classes, participants, workouts, bookings, personal activity, and strength records, and to make or cancel bookings and save or delete PRs after explicit confirmation.21MIT
- AlicenseBqualityBmaintenanceEnables MCP clients to read and write Hevy workouts, routines, exercise templates, and folders, and to generate training-period summaries, exercise progression, and workout details with dry-run previews for writes.22MIT
- 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
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to connect to a privacy-first, self-hostable workout planning and training log, allowing coaching agents to preview and apply program changes while accessing training data through OAuth-protected endpoints.AGPL 3.0
TDQS
Scored across 18 tools
The prepare/execute pairing and resource naming make most tools clearly distinct (prepare_booking_creation vs execute_booking_creation vs execute_late_booking_cancellation). The closest overlap is among the RM tools — get_exercise_1rm, find_exercise_1rm, and get_exercise_rm_progression — where an agent could momentarily confuse the single-latest-1RM read with the multi-series progression read, though the descriptions do clarify intent.
Every tool follows a consistent snake_case verb_noun pattern using a small set of verbs (get_, prepare_, execute_, find_): get_class_sessions, prepare_activity_publication, execute_activity_deletion, find_exercise_1rm. No mixed conventions or casing inconsistencies.
18 tools is slightly above the ideal range, but the count is justified by the domain's breadth (bookings, activities, RM tracking) and the deliberate prepare/execute safety split, which effectively collapses to ~9 real operations. Each tool maps to a distinct action rather than duplicating functionality.
Booking lifecycle (create, cancel, late cancel, upcoming, history) and activity lifecycle (publish, delete, personal activity, published workouts) are well covered, along with RM reads. Minor gaps exist — no update/edit of an existing activity, no single-booking-by-ID read, and no explicit gym enumeration beyond get_account_context — but these are work-aroundable.