hevy-mcp 1.25.17 → 1.26.1

package/README.md

@@ -38,10 +38,10 @@ A Model Context Protocol (MCP) server implementation that interfaces with the [H
 
 Pick the workflow that fits your setup:
 
-| Scenario              | Command                                     | Requirements               |
-| :-------------------- | :------------------------------------------ | :------------------------- |
-| **One-off stdio run** | `HEVY_API_KEY=sk_live... npx -y hevy-mcp`   | Node.js ≥ 26, Hevy API key |
-| **Local development** | `npm install && npm run build && npm start` | `.env` with `HEVY_API_KEY` |
+| Scenario              | Command                                                                                     | Requirements               |
+| :-------------------- | :------------------------------------------------------------------------------------------ | :------------------------- |
+| **One-off stdio run** | `HEVY_API_KEY=sk_live... npx -y hevy-mcp` or `HEVY_API_KEY=sk_live... bunx hevy-mcp@latest` | Node.js ≥ 26, Hevy API key |
+| **Local development** | `npm install && npm run build && npm start`                                                 | `.env` with `HEVY_API_KEY` |
 
 ---
 
@@ -49,18 +49,24 @@ Pick the workflow that fits your setup:
 
 - **Node.js**: v26 or higher (strongly recommended to use the exact version pinned in `.nvmrc`).
 - **npm**: v10 or higher.
+- **Bun** (optional): If you want to launch with `bunx`.
 - **Hevy API key**: Required for all operations (available with Hevy PRO).
 
 ---
 
 ## 📦 Installation
 
-### Run via npx (Recommended)
+### Run via npx or bunx
 
-You can launch the server directly without cloning:
+You can launch the server directly without cloning. Both launchers are covered
+by nightly smoke tests:
 
 ```bash
+# npm launcher
 HEVY_API_KEY=your_hevy_api_key_here npx -y hevy-mcp
+
+# bun launcher
+HEVY_API_KEY=your_hevy_api_key_here bunx hevy-mcp@latest
 ```
 
 ### Manual Installation
@@ -103,6 +109,15 @@ To use this server with Claude Desktop, add the following to your `claude_deskto
 }
 ```
 
+If you prefer Bun, swap the launcher fields:
+
+```json
+{
+	"command": "bunx",
+	"args": ["hevy-mcp@latest"]
+}
+```
+
 ### Cursor Configuration
 
 Add this server under `"mcpServers"` in `~/.cursor/mcp.json`:
@@ -121,6 +136,15 @@ Add this server under `"mcpServers"` in `~/.cursor/mcp.json`:
 }
 ```
 
+If you prefer Bun, swap the launcher fields:
+
+```json
+{
+	"command": "bunx",
+	"args": ["hevy-mcp@latest"]
+}
+```
+
 ### Other MCP Clients (via add-mcp)
 
 For a generic setup flow across MCP clients, use [`add-mcp`](https://github.com/neon-solutions/add-mcp):
@@ -144,16 +168,34 @@ This bootstraps the `hevy-mcp` entry in your client config without manual JSON e
 
 ## ⚙️ Configuration
 
-Supply your Hevy API key via:
+Supply your Hevy API key via the `HEVY_API_KEY` environment variable (in
+`.env` or system environment).
 
-1. **Environment Variable**: `HEVY_API_KEY` (in `.env` or system environment).
-2. **CLI Argument**: `--hevy-api-key=your_key` (after `--` in npm scripts).
+> ⚠️ CLI API key arguments (`--hevy-api-key=...`, `--hevyApiKey=...`,
+> `hevy-api-key=...`) are still accepted for backward compatibility, but are
+> deprecated and insecure. Use `HEVY_API_KEY` instead.
 
 ```env
 # Example .env
 HEVY_API_KEY=your_hevy_api_key_here
 ```
 
+### 🧠 Exercise Template Cache Behavior
+
+`search-exercise-templates` now uses a shared in-memory async cache for the
+full exercise template catalog:
+
+- **TTL**: 5 minutes per cached catalog entry.
+- **Memory bound**: max 1 catalog entry (LRU bounded cache).
+- **In-flight de-duplication**: concurrent requests share the same active
+  fetch when possible.
+- **Manual refresh**: set `refresh: true` in the tool input to invalidate the
+  cached catalog and force a re-fetch from the Hevy API.
+
+This cache currently applies to `search-exercise-templates` only. Paginated
+`get-exercise-templates` requests still call the API directly to keep paging
+behavior explicit and avoid cross-page invalidation complexity.
+
 ### 📡 Sentry Monitoring
 
 `hevy-mcp` includes Sentry monitoring to observe errors and usage in production. It initializes `@sentry/node` with tracing enabled and PII collection disabled by default. Recent observability changes also add:
@@ -166,15 +208,12 @@ HEVY_API_KEY=your_hevy_api_key_here
 ---
 
 <details>
-<summary><strong>⚠️ Deprecation Notices (HTTP/SSE & Docker)</strong></summary>
-
-### Stdio Only
+<summary><strong>⚠️ Migration Note (v1.18.0)</strong></summary>
 
-As of version **1.18.0**, `hevy-mcp` only supports **stdio** transport. HTTP/SSE transport has been completely removed to simplify the codebase and focus on the native MCP experience.
+As of **v1.18.0**, `hevy-mcp` removed both HTTP/SSE transport and Docker
+support.
 
-### Docker
-
-Docker-based workflows are retired. The provided `Dockerfile` now exits with a message pointing to the stdio-native experience. Legacy GHCR images are no longer updated.
+The supported path is stdio via `npx hevy-mcp`.
 
 </details>
 
@@ -191,6 +230,11 @@ Docker-based workflows are retired. The provided `Dockerfile` now exits with a m
 | **Body Measurements** | `get-body-measurements`, `get-body-measurement`, `create-body-measurement`, `update-body-measurement`                              |
 | **User**              | `get-user-info`                                                                                                                    |
 
+> **Delete operations are currently unsupported:** The upstream Hevy OpenAPI
+> spec does not expose `DELETE` endpoints for workouts, routines, routine
+> folders, exercise templates, or body measurements, so `hevy-mcp` does not
+> provide delete tools for these resources.
+
 ---
 
 ## 👨‍💻 Development & Contributing
@@ -199,12 +243,24 @@ Docker-based workflows are retired. The provided `Dockerfile` now exits with a m
 
 - **Build**: `npm run build`
 - **Lint/Format**: `npm run check` (uses oxlint/oxfmt)
+- **Type Check**: `npm run check:types`
 - **Unit Tests**: `npx vitest run --exclude tests/integration/**`
 - **Full Test Suite**: `npm test` (requires `HEVY_API_KEY`)
 - **Changeset Check**: `npm run check:changeset`
 
 For a detailed senior engineer guide, please refer to [AGENTS.md](./AGENTS.md).
 
+### Pull Request Checks
+
+- **Conventional Commits**: CI lints commit messages on pull requests, so use
+  prefixes such as `feat:`, `fix:`, `docs:`, `ci:`, `chore:`, `refactor:`,
+  `test:`, or `style:`.
+- **Type Checking**: CI runs `npm run check:types` on pull requests and pushes
+  to `main`; run this locally before opening a PR.
+- **Changesets**: Contributor pull requests targeting `main` must include a
+  changeset. Dependabot PRs and automated `changeset-release/main` release PRs
+  are handled by automation and skip this check.
+
 ### API Client Generation
 
 The API client is automatically generated from the OpenAPI spec using [Kubb](https://kubb.dev/):
@@ -215,24 +271,40 @@ npm run build:client
 
 ### Versioning & Releases
 
-This project uses [Changesets](https://github.com/changesets/changesets) to manage versioning, changelogs, releases, and pull request validation.
-
-1. **Every Pull Request Needs a Changeset**: If your change should ship in the next release, run:
+This project uses [Changesets](https://github.com/changesets/changesets) to
+manage versioning, changelogs, releases, and pull request validation.
+
+1. **Routine Release Cadence**: Merge the automated
+   `changeset-release/main` (**"Version Packages"**) Pull Request on a regular
+   cadence (weekly is a good default) instead of ad-hoc frequent merges.
+2. **Urgent Release Exception**: Security fixes and high-impact,
+   user-facing bug fixes can be released immediately outside the routine
+   cadence.
+3. **Use Bump Changesets Only for User-Facing Runtime Changes**: If your
+   change is user-facing/runtime-visible, run:
    ```bash
    npx changeset
    ```
-   Follow the prompts to specify the type of change (patch, minor, major) and write a short summary of your change. This creates a markdown file under the `.changeset/` directory.
-2. **Use an Empty Changeset for Non-Release Changes**: Docs, CI, test-only, refactor, and chore changes should still include an empty changeset:
+   Follow the prompts to choose `patch`, `minor`, or `major`, then write a
+   short summary. This creates a markdown file under `.changeset/`.
+4. **Use Empty Changesets for Internal-Only Work**: Docs, CI, test-only,
+   refactor, and chore changes should use an empty changeset:
    ```bash
    npx changeset --empty
    ```
-3. **Validate Before Opening a PR**: Pull requests targeting `main` are checked for a changeset in CI. You can run the same validation locally with:
+5. **Validate Before Opening a PR**: Contributor pull requests targeting
+   `main` are checked for a changeset in CI. Dependabot PRs and automated
+   `changeset-release/main` release PRs are handled separately. You can run the
+   same validation locally with:
    ```bash
    npm run check:changeset
    ```
-4. **Automated Releases**:
-   - Pushing changesets to `main` triggers a GitHub Action that automatically creates or updates a **"Version Packages"** Pull Request.
-   - When this Pull Request is merged, the package is automatically built, published to npm (via OIDC Trusted Publishing), and a GitHub Release is created.
+6. **Automated Releases**:
+   - Pushing changesets to `main` triggers a GitHub Action that automatically
+     creates or updates a **"Version Packages"** Pull Request.
+   - When this Pull Request is merged, the package is automatically built,
+     published to npm (via OIDC Trusted Publishing), and a GitHub Release is
+     created.
 
 ---
 

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@1.25.17" };
+		e.SENTRY_RELEASE = { id: "hevy-mcp@1.26.1" };
 		var n = new e.Error().stack;
 		n && (e._sentryDebugIds = e._sentryDebugIds || {}, e._sentryDebugIds[n] = "03cf150f-6466-4ca3-9cf1-e423cc0e3cd2", e._sentryDebugIdIdentifier = "sentry-dbid-03cf150f-6466-4ca3-9cf1-e423cc0e3cd2");
 	} catch (e) {}
 })();
-import { r as runServer } from "./src-1TMPprRG.mjs";
+import { r as runServer } from "./src-_FHG1OUO.mjs";
 //#region src/cli.ts
 runServer().catch((error) => {
 	console.error("Fatal error in main():", error);

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@1.25.17" };
+		e.SENTRY_RELEASE = { id: "hevy-mcp@1.26.1" };
 		var n = new e.Error().stack;
 		n && (e._sentryDebugIds = e._sentryDebugIds || {}, e._sentryDebugIds[n] = "5b077b94-9ef8-4f24-a0b0-8dcfbf491be1", e._sentryDebugIdIdentifier = "sentry-dbid-5b077b94-9ef8-4f24-a0b0-8dcfbf491be1");
 	} catch (e) {}
 })();
-import { n as createServer, r as runServer, t as configSchema } from "./src-1TMPprRG.mjs";
+import { n as createServer, r as runServer, t as configSchema } from "./src-_FHG1OUO.mjs";
 export { configSchema, createServer, createServer as default, runServer };