@@ -123,22 +123,12 @@ disambiguation is which repo you are standing in, not the tag text.
     - `mcp` only: the official MCP Registry, which `publish.yml` updates after npm.
       Check that `https://registry.modelcontextprotocol.io/v0/servers?search=dev.wraps/email`
       lists the new version with `isLatest: true`.
-12. **`mcp` only: cut the Glama release by hand.** Glama's Auto-Release is **off on
-    purpose**. It fires on *every* GitHub release in wraps-js, so an `email-v*`,
-    `sms-v*` or `client-v*` release would publish a mislabeled MCP release. Glama has
-    no tag filter and no write API, so the release is cut by hand, in a browser
-    signed in to Glama as `stewartjarod`:
-    1. `glama.ai/mcp/servers/wraps-team/wraps-js/admin/repository`: click **Sync
-       Server** and wait until "Last known commit" shows the release commit. Glama
-       rejects a pinned SHA it has not synced ("Commit not found").
-    2. `.../admin/dockerfile`: click **Build**, not Build & Release, and wait for
-       status `success`. Leave the build spec alone. It is Glama's own template,
-       not the repo `Dockerfile`: build steps `pnpm install --frozen-lockfile
-       --filter '@wraps.dev/mcp...'` and `pnpm --filter '@wraps.dev/mcp...' build`,
-       CMD `node packages/mcp/dist/index.js`.
-    3. On that build test's page, click **Create Release** and enter the **npm
-       version** (it defaults to `0.1.0`). The GitHub release notes are fine as
-       the changelog.
+12. **`mcp` only: Glama is not updated.** We stopped cutting Glama releases
+    (2026-11-03): it has no API and ignores the version you type, so its listing
+    lags npm on purpose. Do not add it back to the routine or prompt for it.
+    Glama's Auto-Release stays **off**: it fires on *every* GitHub release in
+    wraps-js, so an `email-v*`, `sms-v*` or `client-v*` release would publish a
+    mislabeled MCP release.
 
 ## Pre-flight checks