@mcpcloud/cli 0.26.0-next-20260927194202 → 0.26.0-next-20260927194247

package/README.md

@@ -103,7 +103,7 @@ mcp servers get my-api --probe         # verify the endpoint serves what the con
 mcp invoke my-api getUser --args '{"id":"abc"}'
 ```
 
-Servers are addressable by id, name, or memorable slug throughout the CLI. Two verbs keep a server current after its API changes: `mcp servers push-spec` diffs a local spec against the stored tools (preview by default; `--apply` reconciles schemas by stable operation key, preserving curated descriptions, tags, risk classes, and enrichment), and `mcp servers regenerate` re-fetches the original source spec and rebuilds with the current codegen (`--dry-run` previews the per-tool changes first). To read a server from a different spec URL from now on, `mcp servers update <server> --source-url <url>` checks the new URL, shows what a regenerate from it would change, and stores it (`--dry-run` checks without storing); then regenerate and deploy. Operations a spec marks `x-mcp: false` never become tools.
+Servers are addressable by id, name, or memorable slug throughout the CLI. Two verbs keep a server current after its API changes: `mcp servers push-spec` diffs a local spec against the stored tools (preview by default; `--apply` reconciles schemas by stable operation key, preserving curated descriptions, tags, risk classes, and enrichment), and `mcp servers regenerate` re-fetches the original source spec and rebuilds with the current codegen (`--dry-run` previews the per-tool changes first), storing the spec document it read so the generated code and the drift check follow it. To read a server from a different spec URL from now on, `mcp servers update <server> --source-url <url>` checks the new URL, shows what a regenerate from it would change, and stores it (`--dry-run` checks without storing); then regenerate and deploy. Operations a spec marks `x-mcp: false` never become tools.
 
 Neither verb renames a tool — both match tools on their stable operation key. Codegen now keeps an operationId's own case (`getRecording`); servers created before that change keep their lowercased names (`getrecording`), and both previews say how many. `mcp tools rename --from-operation-ids --server <server>` (or `push-spec --rename-to-operation-ids`) adopts the new names while keeping tool ids, access grants, and saved scenarios; `mcp tools rename <old> <new>` renames one tool. Deploy afterwards — the live server keeps the old names until then.
 

package/dist/index.js

@@ -8278,11 +8278,16 @@ async function runPushSpec(serverRef, opts) {
 
 // src/commands/servers-regenerate.ts
 function registerServerRegenerateCommand(servers) {
-  servers.command("regenerate <server>").description("Re-fetch a server's source spec and rebuild its tools with the current codegen (preserves customizations). Works for spec-URL, OpenAPI, and GraphQL sources; a pasted or manual server has nothing to re-fetch. Wraps POST /api/v1/server/regenerate.").option("--org <organizationId>", "Organization ID").option("--project <project>", "Project (id or name; defaults to the server's project)").option("--source-url <url>", "Read the spec from this URL for this run only — nothing is stored (needed for GraphQL servers whose introspection endpoint wasn't persisted). To change the stored source, use `mcp servers update <server> --source-url <url>`.").option("--dry-run", "Report what would change (per tool) without writing anything").addHelpText("after", [
+  servers.command("regenerate <server>").description("Re-fetch a server's source spec and rebuild its tools with the current codegen (preserves customizations). Works for spec-URL, OpenAPI, and GraphQL sources; a pasted or manual server has nothing to re-fetch. Wraps POST /api/v1/server/regenerate.").option("--org <organizationId>", "Organization ID").option("--project <project>", "Project (id or name; defaults to the server's project)").option("--source-url <url>", "Read the spec from this URL for this run only: the tools are rebuilt from it, but the stored source and its document are left as they are (needed for GraphQL servers whose introspection endpoint wasn't persisted). To change the stored source, use `mcp servers update <server> --source-url <url>`.").option("--dry-run", "Report what would change (per tool) without writing anything").addHelpText("after", [
     "",
     "Regenerate re-introspects/re-parses the source and rebuilds each tool with",
-    "the current codegen, so codegen fixes reach existing servers. It does not",
-    "deploy — run `mcp servers deploy` afterwards to ship the rebuilt bundle.",
+    "the current codegen, so codegen fixes AND upstream spec changes reach",
+    "existing servers. It stores the spec document it read — codegen builds",
+    "from that document and the daily drift check compares against it — and",
+    "resets the drift check. It does not deploy — run `mcp servers deploy`",
+    "afterwards to ship the rebuilt bundle.",
+    "With --source-url for a different URL, the document is NOT stored: an",
+    "override is for one run, and the stored source keeps pointing where it did.",
     "It never renames a tool: names that predate the current naming rule",
     "(getrecording vs getRecording) are reported, and",
     "`mcp tools rename --from-operation-ids` adopts the rule.",
@@ -8343,7 +8348,8 @@ function printRegeneration(r, serverId) {
     [`tools ${dryRun ? "that would be added" : "added"}`]: String(r.inserted),
     ...r.unchanged !== undefined ? { "tools unchanged": String(r.unchanged) } : {},
     "tools dropped from spec": String(r.removed),
-    generation: r.generationStatus
+    generation: r.generationStatus,
+    ...r.storedDocument ? { "spec document": storedDocumentLine(r.storedDocument) } : {}
   });
   for (const change of r.changes ?? []) {
     printInfo(`  ~ ${change.name}${change.fields.length > 0 ? ` (${change.fields.join(", ")})` : ""}`);
@@ -8360,8 +8366,21 @@ function printRegeneration(r, serverId) {
   });
   if (drift)
     printWarn(`  ! ${drift}`);
+  if (r.storedDocument === "keptForOverride") {
+    printInfo(c.dim(`  → to read ${serverId} from that URL from now on: \`mcp servers update ${serverId} --source-url <url>\`, then regenerate.`));
+  }
   printInfo(c.dim(dryRun ? `  → run \`mcp servers regenerate ${serverId}\` (without --dry-run) to apply, then \`mcp servers deploy ${serverId} --wait\`.` : `  → run \`mcp servers deploy ${serverId} --wait\` to ship the regenerated bundle.`));
 }
+function storedDocumentLine(disposition) {
+  switch (disposition) {
+    case "refreshed":
+      return "stored — codegen builds from it; drift check reset";
+    case "wouldRefresh":
+      return "would be stored (and the drift check reset)";
+    case "keptForOverride":
+      return "kept — --source-url reads another URL for this run only";
+  }
+}
 
 // src/commands/servers-lifecycle.ts
 function registerServerLifecycleCommands(servers) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcpcloud/cli",
-  "version": "0.26.0-next-20260927194202",
+  "version": "0.26.0-next-20260927194247",
   "description": "The official CLI for MCPCloud — manage projects, servers, skills, and API keys from the terminal",
   "type": "module",
   "bin": {