btwb-mcp
Related Servers
Alternatives to btwb-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to plan, build, and log calisthenics workouts in a user's own account, including searching exercises, managing custom workouts and plans, reading progress and coaching data, and logging completed sessions. Account mutations require explicit confirmation, and workouts can be displayed as interactive cards in the chat.MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLMs to read and write Hevy workout tracking data, including workouts, routines, exercise templates, per-exercise history, and body measurements through all 15 Hevy public API endpoints.7 npmMIT
- AlicenseBqualityDmaintenanceIntegrates with the Boostcamp fitness platform to provide workout history, programs, exercises, and analytics via natural language.12MIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude and other AI assistants to query workouts, build structured intervals, manage calendars, track fitness trends, and control training through natural conversation without official API approval.-
- FlicenseNot gradedqualityAmaintenanceConnects AI assistants to a TrainingPeaks account via secure cookie authentication—no API approval required—so users can query and build workouts, schedule and copy sessions, manage calendar events and notes, log health metrics, and review CTL/ATL/TSB fitness trends, power PRs and zone settings through natural language. It also covers strength workouts, equipment, workout libraries, multi-week training plans, and coach features such as athlete groups.-
- FlicenseNot gradedqualityAmaintenanceEnables Claude, Code, Cowork, and other AI assistants to query workouts, build structured intervals, manage calendars, log health metrics, track CTL/ATL/TSB fitness trends and power PRs, and control training data through natural language. Uses secure cookie authentication so any account can connect without official API approval.-
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: search_movement (library lookup) vs get_movement_history (per-set history), log_workout (single movement) vs log_rounds_workout (multi-movement rounds), get_workout_session (read) vs delete_workout_session (remove), plus a standalone auth utility. Descriptions proactively clarify overlaps, e.g. log_rounds_workout explicitly contrasts itself with log_workout.
All seven tools use consistent snake_case verb_noun phrasing (search_movement, log_workout, get_workout_session, delete_workout_session, refresh_session_cookie). No style mixing or vague verb-only names.
Seven tools is well-scoped for a workout-logging and movement-data integration; each tool earns its place with a clear role and no redundant entries.
The surface covers search, log (two variants), read, and delete, but has no update/edit for an already-logged result, and get_workout_session requires a known session ID with no search-by-date or list-sessions tool. Discovery of existing sessions/workouts is thus a notable gap.