@trainheroic-unofficial/athlete-mcp 3.0.1 → 3.1.0

package/README.md

@@ -4,7 +4,7 @@ Local single-user [MCP](https://modelcontextprotocol.io) server for a TrainHeroi
 
 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. 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).
+It exposes the logged-in athlete's own training: scheduled and completed workouts, per-exercise history, PRs (personal records), working maxes, lifetime totals, and confirmation-gated training writes. 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).
 
 ---
 
@@ -48,8 +48,8 @@ A coach account works here too: a TrainHeroic coach account also has its own ath
 
 ## Tools
 
-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.
+The assistant fills in each tool's parameters (dates are `YYYY-MM-DD`); your MCP client shows the
+full schema for each. Writes are confirmation-gated.
 
 - `athlete_whoami`: identity (id, name, roles)
 - `athlete_profile`: lifetime totals + profile
@@ -67,6 +67,9 @@ are `YYYY-MM-DD`); your MCP client shows the full schema for each.
 - `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.
+- `athlete_prescribe_set`: sets your planned reps and/or weight without recording the set as
+  completed. It replaces the selected exercise's whole prescription, so every planned set and
+  value to keep must be included.
 
 ---
 

package/dist/server.mjs

@@ -203,12 +203,18 @@ const logSetArgsSchema = z.object({
 	results: loggedExerciseResultsSchema
 });
 logSetArgsSchema.extend({ athleteId: idArgSchema });
-z.object({
+/**
+* Args for changing the logged-in athlete's prescribed targets without marking the set performed.
+* The write replaces the exercise's whole prescription, so its sets are positional and sequential
+* by definition: it deliberately omits the log path's `slot` field because a sparse prescription
+* has no meaning here.
+*/
+const athletePrescribeSetArgsSchema = z.object({
 	date: dateString,
 	savedWorkoutSetId: idArgSchema,
-	athleteId: idArgSchema,
 	results: prescribedExerciseResultsSchema
 });
+athletePrescribeSetArgsSchema.extend({ athleteId: idArgSchema });
 /**
 * Args for the coach per-athlete exercise swap: replace the exercise prescribed in one of a
 * roster athlete's saved-workout slots with a different exercise, the API equivalent of the
@@ -1427,6 +1433,21 @@ async function logAthleteSet(client, args) {
 	};
 }
 /**
+* Set the logged-in athlete's prescribed reps/weight for one saved workout set WITHOUT marking it
+* performed. This is the athlete-side equivalent of editing target values in the app: it writes
+* `param_N_data_M` with every made/completed flag cleared and skips the set-completion PUT.
+*
+* The write replaces the selected exercise's whole prescription, so callers must pass every set
+* they want to keep. An omitted param is cleared rather than preserved.
+*/
+async function prescribeAthleteSet(client, args) {
+	const r = await writeSetResults(client, { role: "athlete" }, await fetchAthleteWorkouts(client, args.date, args.date), args.savedWorkoutSetId, args.results, "prescribe");
+	return {
+		savedWorkoutSetId: r.savedWorkoutSetId,
+		exercisesPrescribed: r.exercisesWritten
+	};
+}
+/**
 * Swap the exercise prescribed in one of an athlete's saved-workout slots for a different
 * exercise — the API equivalent of the app's per-athlete "swap exercise":
 * `PUT /v5/savedWorkoutSetExercises/{savedWorkoutSetExerciseId}?exerciseId={exerciseId}` with an
@@ -1462,9 +1483,10 @@ async function swapAthleteExercise(client, args) {
 	};
 }
 /**
-* 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.
+* Shared set-write behind {@link logAthleteSet}, {@link prescribeAthleteSet},
+* {@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
@@ -2047,6 +2069,24 @@ function registerLogTool(server, ctx) {
 			results: toSetResults(results)
 		}));
 	}));
+	server.registerTool("athlete_prescribe_set", {
+		title: "Set your prescribed reps/weight without logging",
+		description: "Athlete-facing write: set the planned reps and/or weight for one of your scheduled workout sets WITHOUT recording it as performed. Use this when you know the target load before training but have not completed the set yet. The set stays open and nothing is added to exercise history. param1 is reps and param2 is weight; pass one sets[] entry per planned set. This write REPLACES the selected exercise's whole prescription, so include every planned set and every value you want to keep; an omitted param is cleared. Get savedWorkoutSetId + savedWorkoutSetExerciseId from athlete_log_targets. To record actual completed results, use athlete_log_set instead. Requires confirmation (elicitation or confirm:true).",
+		inputSchema: {
+			...athletePrescribeSetArgsSchema.shape,
+			confirm: z.boolean().optional()
+		},
+		annotations: DESTRUCTIVE
+	}, ({ date, savedWorkoutSetId, results, confirm }, extra) => attempt(async () => {
+		const id = toId(savedWorkoutSetId);
+		const blocked = confirmGate(extra, `Set prescribed values on your saved workout set ${id} on ${date}? This changes your planned reps/weight but does not log the set as completed.`, confirm);
+		if (blocked) return blocked;
+		return jsonResult(await prescribeAthleteSet(ctx.client, {
+			date,
+			savedWorkoutSetId: id,
+			results: toSetResults(results)
+		}));
+	}));
 }
 /**
 * The athlete's own per-exercise swap, in its own function so registerLogTool/registerSessionTools
@@ -2103,7 +2143,7 @@ function registerAthleteTrainingTools(server, ctx) {
 }
 //#endregion
 //#region package.json
-var version = "3.0.1";
+var version = "3.1.0";
 //#endregion
 //#region src/server.ts
 function main() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trainheroic-unofficial/athlete-mcp",
-  "version": "3.0.1",
+  "version": "3.1.0",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -21,8 +21,8 @@
   "dependencies": {
     "@modelcontextprotocol/server": "2.0.0",
     "zod": "^4.4.3",
-    "@trainheroic-unofficial/core": "3.0.1",
-    "@trainheroic-unofficial/js": "3.0.1"
+    "@trainheroic-unofficial/core": "3.1.0",
+    "@trainheroic-unofficial/js": "3.1.0"
   },
   "devDependencies": {
     "@types/node": "^26.2.0",