Trainzilla MCP
OfficialRelated Servers
Alternatives to Trainzilla MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables workout tracking and coaching within Claude conversations, managing exercise configs, logs, streaks, and health metrics via an MCP server with PostgreSQL.-
- AlicenseNot gradedqualityBmaintenanceA personal remote MCP server that lets Claude read your Hevy workout data and MacroFactor nutrition data directly in conversation, with read-only tools for workouts, body measurements, macros, and weight trends.MIT
- FlicenseBqualityBmaintenanceIntegrates with the Boostcamp fitness platform to provide access to training history, workout programs, custom exercises, and analytics through Claude.127-
- AlicenseNot gradedqualityAmaintenanceConnect MyFitnessPal to Claude or any MCP client. Log meals, search food database with macros, track trends, and export nutrition history against your real MyFitnessPal diary.12MIT
- AlicenseAqualityDmaintenanceConnects Strava training data to Claude, enabling personalized coaching through analysis of training load, workout planning, gear maintenance, and power metrics.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables creating workout plans, tracking progress, suggesting exercises, and calculating training volume through natural language, compliant with MCP protocol.MIT
TDQS
Scored across 23 tools
Each tool targets a distinct resource and action. List tools differentiate by entity (clients, check-ins, habits, etc.), create tools are specific, and calc tools serve unique purposes. No two tools have overlapping functionality, making selection unambiguous.
Most tools follow a consistent verb_noun pattern (e.g., list_clients, create_habit). However, 'master_habits' and 'recent_habit_activity' deviate from the expected 'list_*' prefix, and 'whoami' is a single word, slightly breaking the pattern.
23 tools cover a wide range of coaching functionalities (clients, habits, plans, sessions, billing, calculations). While slightly above the typical 3-15 range, each tool serves a distinct purpose and contributes to the server's comprehensive scope.
The tool surface is heavily skewed toward creation and listing. There are no update or delete operations for any resource (e.g., diet plans, workout plans, habits, sessions), which leaves agents unable to modify or remove existing data, creating significant workflow gaps.