@trainheroic-unofficial/athlete-mcp 1.1.0 → 1.2.0

package/README.md

@@ -1,10 +1,10 @@
 # @trainheroic-unofficial/athlete-mcp
 
-Local single-user [MCP](https://modelcontextprotocol.io) server for a TrainHeroic **athlete** — it exposes one [TrainHeroic](https://www.trainheroic.com) athlete's own training to an AI assistant (Claude Code, Claude Desktop, or any MCP client) as callable tools. It runs on your machine and speaks the MCP stdio transport, so the assistant launches it as a subprocess.
+Local single-user [MCP](https://modelcontextprotocol.io) server for a TrainHeroic **athlete**, exposing one [TrainHeroic](https://www.trainheroic.com) athlete's own training to any MCP-capable AI assistant as callable tools. It runs on your machine and speaks the MCP stdio transport, so the assistant launches it as a subprocess.
 
-It reads two required environment variables, `TRAINHEROIC_EMAIL` and `TRAINHEROIC_PASSWORD` — your existing TrainHeroic login. These are your real credentials in plaintext; the config below puts them in a file or shell history, so treat them as secrets.
+It reads two required environment variables, `TRAINHEROIC_EMAIL` and `TRAINHEROIC_PASSWORD` (your existing TrainHeroic login). These are real credentials in plaintext; the config below puts them in a file or shell history, so treat them as secrets.
 
-It exposes the logged-in athlete's own training — scheduled and completed workouts, per-exercise history, PRs (personal records), working maxes, and lifetime totals — plus one confirmation-gated write that logs a completed set. For coaching (rosters, teams, programs, messaging), use [`@trainheroic-unofficial/coach-mcp`](../coach-mcp). For a hosted version that holds credentials server-side behind OAuth and gives a coach login both the athlete and coaching tools, see the [root README](../../README.md).
+It exposes the logged-in athlete's own training: scheduled and completed workouts, per-exercise history, PRs (personal records), working maxes, and lifetime totals, plus one confirmation-gated write that logs a completed set. Coaching capabilities (rosters, teams, programs, messaging) are available through [`@trainheroic-unofficial/coach-mcp`](../coach-mcp). A hosted version that holds credentials server-side behind OAuth and gives a coach login both the athlete and coaching tools is described in the [root README](../../README.md).
 
 ---
 
@@ -23,7 +23,7 @@ claude mcp add trainheroic-athlete \
 
 ### Claude Desktop / `.mcp.json` / other stdio clients
 
-Put this in your client's MCP config — for Claude Desktop that's `claude_desktop_config.json`
+Put this in your client's MCP config. For Claude Desktop that's `claude_desktop_config.json`
 (macOS: `~/Library/Application Support/Claude/`; Windows: `%APPDATA%\Claude\`); for a
 project-scoped Claude Code setup it's `.mcp.json` at the repo root.
 
@@ -51,20 +51,20 @@ A coach account works here too: a TrainHeroic coach account also has its own ath
 All read-only except `athlete_log_set`. The assistant fills in each tool's parameters (dates
 are `YYYY-MM-DD`); your MCP client shows the full schema for each.
 
-- `athlete_whoami` — identity (id, name, roles)
-- `athlete_profile` — lifetime totals + profile
-- `athlete_prefs` — notification/display preferences
-- `athlete_workouts` — scheduled + completed workouts in a date range, flattened into one list
-- `athlete_exercises` — search the exercises you've logged
-- `athlete_exercise_history` — per-exercise PRs + dated session history
-- `athlete_personal_records` — exercise personal records
-- `athlete_exercise_stats` — last performance + PR as of a date
-- `athlete_working_maxes` — working max per exercise
-- `athlete_leaderboard` — benchmark/test workout leaderboard
+- `athlete_whoami`: identity (id, name, roles)
+- `athlete_profile`: lifetime totals + profile
+- `athlete_prefs`: notification/display preferences
+- `athlete_workouts`: scheduled + completed workouts in a date range, flattened into one list
+- `athlete_exercises`: search the exercises you've logged
+- `athlete_exercise_history`: per-exercise PRs + dated session history
+- `athlete_personal_records`: exercise personal records
+- `athlete_exercise_stats`: last performance + PR as of a date
+- `athlete_working_maxes`: working max per exercise
+- `athlete_leaderboard`: benchmark/test workout leaderboard
 
 **Write (confirmation-gated):**
 
-- `athlete_log_set` — logs completed set results to your training log. This is a real write
+- `athlete_log_set`: logs completed set results to your training log. This is a real write
   that your coach can see. It confirms before running: the server asks the client to confirm,
   falling back to an explicit `confirm: true` argument when the client can't prompt.
 

package/dist/server.mjs

@@ -173,6 +173,11 @@ const logSetArgsSchema = z.object({
 	})).min(1)
 });
 logSetArgsSchema.extend({ athleteId: idArgSchema });
+logSetArgsSchema.extend({ athleteId: idArgSchema });
+z.object({
+	savedWorkoutSetExerciseId: idArgSchema,
+	exerciseId: idArgSchema
+});
 /**
 * Args for logging a whole session by exercise (rather than by saved-workout-set id). Each
 * exercise carries its entered sets and an optional 1-based `order`. The athlete path creates
@@ -891,29 +896,37 @@ function summarizeAthleteWorkouts(list) {
 }
 const MAX_PARAM_SLOTS = 10;
 /**
-* Build the body for `PUT /1.0/athlete/savedworkoutsetexercise/{id}`. The body uses
-* snake_case keys matching the live API response shape. Each set slot (1-10) gets a
-* `param_N_made` flag (1 if data is present, 0 otherwise) and `param_1_data_N` /
-* `param_2_data_N` string values.
+* Build the body for `PUT /1.0/{role}/savedworkoutsetexercise/{id}`. The body uses snake_case
+* keys matching the live API response shape. Each set slot (1-10) carries `param_1_data_N` /
+* `param_2_data_N` string values plus a `param_N_made` flag.
+*
+* `mode` selects which write this is — the same endpoint serves both:
+*   - `"log"`: the values ARE a performed result, so `param_N_made` is 1 where the slot has data
+*     and the exercise `completed` flag is 1 when any set has data.
+*   - `"prescribe"`: the values are prescribed targets, written with every `param_N_made` and
+*     `completed` left at 0 so the set is not marked done. This matches what the app sends when a
+*     coach edits an athlete's prescribed reps/weight.
 *
 * Only `savedWorkoutSetExerciseId`, `savedWorkoutSetId`, and `workoutSetExerciseId` are
 * required from the live exercise record; everything else is derived from `results`.
 *
-* Exported for unit testing — callers should use `logAthleteSet` instead.
+* Exported for unit testing — callers should use `logAthleteSet` / `prescribeForAthlete` instead.
 */
-function buildExerciseLogPayload(savedWorkoutSetExerciseId, savedWorkoutSetId, workoutSetExerciseId, results) {
+function buildExerciseSetPayload(savedWorkoutSetExerciseId, savedWorkoutSetId, workoutSetExerciseId, results, mode) {
 	if (results.length > MAX_PARAM_SLOTS) throw new Error(`At most ${MAX_PARAM_SLOTS} sets are supported per exercise; got ${results.length}.`);
+	const performed = mode === "log";
+	const hasData = results.some((s) => s.param1 !== void 0 || s.param2 !== void 0);
 	const body = {
 		id: savedWorkoutSetExerciseId,
 		saved_workout_set_id: savedWorkoutSetId,
 		workout_set_exercise_id: workoutSetExerciseId,
-		completed: results.some((s) => s.param1 !== void 0 || s.param2 !== void 0) ? 1 : 0
+		completed: performed && hasData ? 1 : 0
 	};
 	for (let i = 1; i <= MAX_PARAM_SLOTS; i += 1) {
 		const slot = results[i - 1];
 		const p1 = slot?.param1 !== void 0 ? String(slot.param1) : "";
 		const p2 = slot?.param2 !== void 0 ? String(slot.param2) : "";
-		body[`param_${i}_made`] = p1 !== "" || p2 !== "" ? 1 : 0;
+		body[`param_${i}_made`] = performed && (p1 !== "" || p2 !== "") ? 1 : 0;
 		body[`param_1_data_${i}`] = p1;
 		body[`param_2_data_${i}`] = p2;
 	}
@@ -1014,7 +1027,11 @@ function buildSetCompletePayload(rawSet, exerciseIds, complete) {
 * by the respective PUT bodies.
 */
 async function logAthleteSet(client, args) {
-	return writeSetResults(client, { role: "athlete" }, await fetchAthleteWorkouts(client, args.date, args.date), args.savedWorkoutSetId, args.results);
+	const r = await writeSetResults(client, { role: "athlete" }, await fetchAthleteWorkouts(client, args.date, args.date), args.savedWorkoutSetId, args.results, "log");
+	return {
+		savedWorkoutSetId: r.savedWorkoutSetId,
+		exercisesLogged: r.exercisesWritten
+	};
 }
 /**
 * Coach "Log for Athlete": record set results for a roster athlete on their behalf, via the
@@ -1028,24 +1045,32 @@ async function logAthleteSet(client, args) {
 */
 async function logForAthlete(client, args) {
 	const workouts = await fetchCoachAthleteWorkouts(client, args.athleteId, args.date, args.date);
-	return writeSetResults(client, {
+	const r = await writeSetResults(client, {
 		role: "coach",
 		athleteId: args.athleteId
-	}, workouts, args.savedWorkoutSetId, args.results);
+	}, workouts, args.savedWorkoutSetId, args.results, "log");
+	return {
+		savedWorkoutSetId: r.savedWorkoutSetId,
+		exercisesLogged: r.exercisesWritten
+	};
 }
 /**
-* Shared two-step set-log write behind {@link logAthleteSet} and {@link logForAthlete}.
-* `target` selects the surface: `athlete` writes `/1.0/athlete/...`; `coach` writes
-* `/1.0/coach/...{athleteId}` and stamps `athleteId` into each body. Step 1 PUTs each
-* exercise's entered data to its own endpoint (the only path that actually stores reps and
-* weight). Step 2 marks the set completed; that body needs the app's camelCase in-memory
-* shape and the full list of savedWorkoutSetExercise IDs in the set (not only the logged ones).
+* Shared set-write behind {@link logAthleteSet}, {@link logForAthlete}, and
+* {@link prescribeForAthlete}. `target` selects the surface: `athlete` writes `/1.0/athlete/...`;
+* `coach` writes `/1.0/coach/...{athleteId}` and stamps `athleteId` into each body.
+*
+* Step 1 PUTs each exercise's per-set values to its own endpoint (the only path that actually
+* stores reps and weight). `mode` decides what those values mean: `"log"` records them as a
+* performed result and runs Step 2, which marks the set completed (that body needs the app's
+* camelCase in-memory shape and the full list of savedWorkoutSetExercise IDs in the set, not only
+* the written ones); `"prescribe"` writes them as a prescription and skips Step 2, leaving the set
+* open.
 */
-async function writeSetResults(client, target, workouts, savedWorkoutSetId, results) {
+async function writeSetResults(client, target, workouts, savedWorkoutSetId, results, mode) {
 	const { exercises, rawSet } = findSavedWorkoutSet(workouts, savedWorkoutSetId);
 	const suffix = target.role === "coach" ? `/${target.athleteId}` : "";
 	const extra = target.role === "coach" ? { athleteId: target.athleteId } : {};
-	let exercisesLogged = 0;
+	let exercisesWritten = 0;
 	for (const result of results) {
 		const ex = exercises.find((e) => coerceInt(e.id) === result.savedWorkoutSetExerciseId);
 		if (!ex) {
@@ -1059,25 +1084,27 @@ async function writeSetResults(client, target, workouts, savedWorkoutSetId, resu
 		const workoutSetExerciseId = coerceInt(ex.workout_set_exercise_id);
 		if (!workoutSetExerciseId) throw new Error(`Could not resolve workout_set_exercise_id for exercise ${result.savedWorkoutSetExerciseId}.`);
 		const body = {
-			...buildExerciseLogPayload(result.savedWorkoutSetExerciseId, savedWorkoutSetId, workoutSetExerciseId, result.sets),
+			...buildExerciseSetPayload(result.savedWorkoutSetExerciseId, savedWorkoutSetId, workoutSetExerciseId, result.sets, mode),
 			...extra
 		};
 		const res = await client.request("PUT", `/1.0/${target.role}/savedworkoutsetexercise/${result.savedWorkoutSetExerciseId}${suffix}`, { body });
 		if (!res.ok) {
-			const readOnly = target.role === "coach" && (res.status === 401 || res.status === 403) ? ` Athlete ${target.athleteId} appears to be read-only for results — TrainHeroic's seeded demo/sample athletes return ${res.status} here; results only persist for real (invited) athletes.` : "";
-			throw new Error(`Failed to log exercise ${result.savedWorkoutSetExerciseId} (HTTP ${res.status}).${readOnly}`);
+			const readOnly = target.role === "coach" && (res.status === 401 || res.status === 403) ? ` Athlete ${target.athleteId} appears to be read-only for changes — TrainHeroic's seeded demo/sample athletes return ${res.status} here; writes only persist for real (invited) athletes.` : "";
+			throw new Error(`Failed to write exercise ${result.savedWorkoutSetExerciseId} (HTTP ${res.status}).${readOnly}`);
 		}
-		exercisesLogged += 1;
+		exercisesWritten += 1;
+	}
+	if (mode === "log") {
+		const setBody = {
+			...buildSetCompletePayload(rawSet, exercises.map((e) => coerceInt(e.id)).filter((n) => n !== null), true),
+			...extra
+		};
+		const setRes = await client.request("PUT", `/1.0/${target.role}/savedworkoutset/${savedWorkoutSetId}${suffix}`, { body: setBody });
+		if (!setRes.ok) throw new Error(`Failed to mark workout set ${savedWorkoutSetId} completed (HTTP ${setRes.status}).`);
 	}
-	const setBody = {
-		...buildSetCompletePayload(rawSet, exercises.map((e) => coerceInt(e.id)).filter((n) => n !== null), true),
-		...extra
-	};
-	const setRes = await client.request("PUT", `/1.0/${target.role}/savedworkoutset/${savedWorkoutSetId}${suffix}`, { body: setBody });
-	if (!setRes.ok) throw new Error(`Failed to mark workout set ${savedWorkoutSetId} completed (HTTP ${setRes.status}).`);
 	return {
 		savedWorkoutSetId,
-		exercisesLogged
+		exercisesWritten
 	};
 }
 /**
@@ -1521,7 +1548,7 @@ function registerAthleteTrainingTools(server, ctx) {
 }
 //#endregion
 //#region package.json
-var version = "1.1.0";
+var version = "1.2.0";
 //#endregion
 //#region src/server.ts
 async function main() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trainheroic-unofficial/athlete-mcp",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -21,8 +21,8 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^4.4.3",
-    "@trainheroic-unofficial/core": "1.1.0",
-    "@trainheroic-unofficial/js": "1.1.0"
+    "@trainheroic-unofficial/core": "1.2.0",
+    "@trainheroic-unofficial/js": "1.2.0"
   },
   "devDependencies": {
     "@types/node": "^26.0.0",