hevy-mcp 4.1.2 → 5.0.0

package/README.md

@@ -12,7 +12,7 @@
 [![Hosted on Cloudflare](https://img.shields.io/badge/Hosted_on-Cloudflare-F38020?logo=cloudflare&logoColor=white)](#hosted-cloudflare-endpoint)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](./LICENSE)
 
-[Connect to the hosted MCP](#connect-to-the-hosted-endpoint) · [Watch the 18-second demo](https://raw.githubusercontent.com/chrisdoc/hevy-mcp/main/docs/assets/hevy-mcp-demo.mp4) · [Explore all 25 tools](#tools)
+[Connect to the hosted MCP](#connect-to-the-hosted-endpoint) · [Watch the 18-second demo](https://raw.githubusercontent.com/chrisdoc/hevy-mcp/main/docs/assets/hevy-mcp-demo.mp4) · [Explore all 26 tools](#tools)
 
 </div>
 
@@ -295,10 +295,10 @@ only when your assistant calls them.
 
 These server-provided MCP prompts coordinate common multi-step workflows:
 
-| Prompt                        | Arguments                                | Workflow                                                                                                               |
-| ----------------------------- | ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| `analyze-workout-progress`    | Optional `weeks` from 1-12; default `4`  | Calls `get-training-summary`, then analyzes workout activity and body-measurement trends from the returned evidence.   |
-| `create-workout-from-routine` | Required `routineId` and UTC `startTime` | Loads a routine, collects actual completed-set data and an end time, then creates a workout without inventing results. |
+| Prompt                        | Arguments                                  | Workflow                                                                                                               |
+| ----------------------------- | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
+| `analyze-workout-progress`    | Optional `weeks` from 1-12; default `4`    | Calls `get-training-summary`, then analyzes workout activity and body-measurement trends from the returned evidence.   |
+| `create-workout-from-routine` | Required `routine_id` and UTC `start_time` | Loads a routine, collects actual completed-set data and an end time, then creates a workout without inventing results. |
 
 > [!NOTE]
 > With MCP SDK v1.29.0, clients invoking `analyze-workout-progress` with its
@@ -307,7 +307,7 @@ These server-provided MCP prompts coordinate common multi-step workflows:
 
 ## Tools
 
-`hevy-mcp` registers 25 tools. Read-only tools are safe for exploration; create
+`hevy-mcp` registers 26 tools. Read-only tools are safe for exploration; create
 and update tools are exposed with MCP mutation annotations so compatible clients
 can request confirmation.
 
@@ -319,7 +319,8 @@ can request confirmation.
 | Workouts           | `get-workout-count`         | Return the account's total workout count.                                         |
 | Workouts           | `get-workout-events`        | List workout update and delete events since a timestamp.                          |
 | Workouts           | `create-workout`            | Create a completed workout in Hevy.                                               |
-| Workouts           | `update-workout`            | Replace an existing workout by ID.                                                |
+| Workouts           | `update-workout`            | Patch workout metadata by ID; omitted fields and all exercises remain unchanged.  |
+| Workouts           | `replace-workout-exercises` | Replace all exercises and sets while preserving workout metadata.                 |
 | Routines           | `search-routines`           | Search routine titles and return compact metadata for discovery.                  |
 | Routines           | `get-routines`              | List custom and default workout routines.                                         |
 | Routines           | `get-routine`               | Get one routine and its exercise configuration by ID.                             |
@@ -361,7 +362,7 @@ https://hevy.chrisdoc.dev/mcp
 ```
 
 It is the quickest way to use `hevy-mcp`: there is nothing to install or keep
-running locally, and it exposes the same 25 tools as the npm package and Docker
+running locally, and it exposes the same 26 tools as the npm package and Docker
 image.
 
 The Cloudflare Worker uses stateless **Streamable HTTP** at `POST /mcp`.

package/dist/cli.mjs

@@ -4,12 +4,12 @@
 (function() {
 	try {
 		var e = "undefined" != typeof window ? window : "undefined" != typeof global ? global : "undefined" != typeof globalThis ? globalThis : "undefined" != typeof self ? self : {};
-		e.SENTRY_RELEASE = { id: "hevy-mcp@4.1.2" };
+		e.SENTRY_RELEASE = { id: "hevy-mcp@5.0.0" };
 		var n = new e.Error().stack;
 		n && (e._sentryDebugIds = e._sentryDebugIds || {}, e._sentryDebugIds[n] = "625c4c9c-e20d-40b3-96b1-4e799ef130f3", e._sentryDebugIdIdentifier = "sentry-dbid-625c4c9c-e20d-40b3-96b1-4e799ef130f3");
 	} catch (e) {}
 })();
-import { a as createSafeErrorDiagnostic, i as MissingHevyApiKeyError, n as runServer, o as flushTelemetry } from "./src-Wa4VP4Na.mjs";
+import { a as createSafeErrorDiagnostic, i as MissingHevyApiKeyError, n as runServer, o as flushTelemetry } from "./src-BUmpaxmH.mjs";
 //#region src/cli.ts
 runServer().catch(async (error) => {
 	if (error instanceof MissingHevyApiKeyError) console.error(error.message);

package/dist/index.d.mts

@@ -5,7 +5,7 @@ type NodeTransport = "stdio" | "http";
 //#region src/index.d.ts
 declare function createNodeMcpServer({ apiKey }: {
   apiKey: string;
-}, transport?: NodeTransport): Promise<import("@modelcontextprotocol/sdk/server/mcp").McpServer>;
+}, transport?: NodeTransport): Promise<import("@modelcontextprotocol/server").McpServer>;
 declare function runStdioServer(): Promise<void>;
 declare function runServer(): Promise<void>;
 //#endregion

package/dist/index.mjs

@@ -4,10 +4,10 @@
 (function() {
 	try {
 		var e = "undefined" != typeof window ? window : "undefined" != typeof global ? global : "undefined" != typeof globalThis ? globalThis : "undefined" != typeof self ? self : {};
-		e.SENTRY_RELEASE = { id: "hevy-mcp@4.1.2" };
+		e.SENTRY_RELEASE = { id: "hevy-mcp@5.0.0" };
 		var n = new e.Error().stack;
 		n && (e._sentryDebugIds = e._sentryDebugIds || {}, e._sentryDebugIds[n] = "e9496b31-626b-4ad1-9416-47ba4ffd2995", e._sentryDebugIdIdentifier = "sentry-dbid-e9496b31-626b-4ad1-9416-47ba4ffd2995");
 	} catch (e) {}
 })();
-import { n as runServer, r as runStdioServer, t as createNodeMcpServer } from "./src-Wa4VP4Na.mjs";
+import { n as runServer, r as runStdioServer, t as createNodeMcpServer } from "./src-BUmpaxmH.mjs";
 export { createNodeMcpServer, runServer, runStdioServer };