formtrace-mcp
Related Servers
Alternatives to formtrace-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
- AlicenseBqualityCmaintenanceEnables access to Hevy strength-training data—workouts, routines, exercise history, and progression—via an MCP server with per-user credential encryption and optional write support.16Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for Hevy that fetches live workout data and computes analytics like e1RM, PRs, volume, and consistency, while enabling writes for routines, folders, and body measurements without modifying workout history.46 npmMIT
- AlicenseBqualityDmaintenanceMCP server for the Hevy workout tracker API that allows reading and writing workouts, routines, exercise templates, and body measurements.2211 npm1MIT
- AlicenseNot gradedqualityCmaintenanceProvides full access to the Hevy public API, enabling users to manage workouts, routines, routine folders, exercise templates, exercise history, and body measurements through natural language. Supports both local stdio and remote HTTP MCP deployments.15 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT to read and manage one Hevy account's workouts, routines, exercise history, body measurements, and active workout drafts, including previewing and applying routine or workout changes with revision checks.2,615 npm1Apache 2.0
TDQS
Scored across 22 tools
Most tools target a distinct resource+action (workouts, routines, folders, exercise templates) and descriptions clarify the differences. There is minor overlap between get_hevy_workout vs get_workout_details, get_exercise_progression vs get_hevy_exercise_history, and search_exercises vs list_hevy_exercise_templates, but the descriptions give enough signal to choose correctly.
The dominant pattern is a consistent verb_noun with a hevy_ resource prefix (get_hevy_*, list_hevy_*, create_hevy_*, update_hevy_*). A handful of tools drop the prefix (get_workout_details, get_training_report, search_exercises, get_exercise_progression), which is a minor inconsistency but still readable.
At 22 tools this is on the heavy side for a single-domain fitness API wrapper, and the create/update tools are doubled by dry-run semantics. The tools are well-organized and mostly earn their place across four resource types, but the surface is borderline bloated.
Read and write coverage is strong (list/get/create/update for workouts, routines, folders, templates, plus analytics and events), but delete operations are entirely absent and exercise-template/folder updates are missing. These gaps mean the CRUD lifecycle is not fully closed, though agents can accomplish most core workflows.