@mcpcloud/cli 0.24.1 → 0.25.0-next-20260923001855

package/README.md

@@ -103,7 +103,9 @@ 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.
+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).
+
+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.
 
 Two behaviors worth internalizing:
 
@@ -126,7 +128,7 @@ mcp push --dry-run              # print the exact change set without writing
 mcp push                        # apply; exits non-zero if anything was refused
 ```
 
-Tool *shape* (schemas, method, path) is spec-owned and travels through `mcp servers push-spec`; `push` carries voice (description, tags, riskClass, idempotent) and handler code. A tool changed in the cloud since your pull is refused, never overwritten — re-run `mcp pull` and reapply. For single-tool round trips there are also `mcp tools pull` / `edit` / `diff` / `show` / `reset-handler`, and `mcp tools handlers list` shows which tools carry handler overrides.
+Tool *shape* (schemas, method, path) is spec-owned and travels through `mcp servers push-spec`; `push` carries voice (description, tags, riskClass, idempotent) and handler code. A tool changed in the cloud since your pull is refused, never overwritten — re-run `mcp pull` and reapply. For single-tool round trips there are also `mcp tools pull` / `edit` / `diff` / `show` / `reset-handler`, and `mcp tools handlers list` shows which tools carry handler overrides. A tool's name is not voice: editing `name:` in its file is refused by `edit`, `push`, and `mcp dev` — rename with `mcp tools rename <old> <new>`, then `mcp tools pull`. `mcp tools delete` removes a single tool (the remove-and-re-add route).
 
 ## The dev loop
 
@@ -609,6 +611,7 @@ _Generated from the live command tree by `bun run docs:readme` — do not edit b
 
 | Command | Description |
 | --- | --- |
+| `mcp tools delete <name>` | Delete one tool from a server (the remove-and-re-add route). Removes its access grants and archives its saved test scenarios. Requires --confirm "<name>". |
 | `mcp tools diff <name>` | Compare a tool's local files (metadata .md + handler .ts) against the cloud version. |
 | `mcp tools edit <name>` | Open a tool's local .md in $EDITOR; pushes your changes to the cloud on save. Requires `mcp dev` to have materialized tools (run `mcp tools pull` first if needed). |
 | `mcp tools enrich [name]` | Run AI enrichment for one tool (prints the suggested vs applied diff), or for the whole server with --all. |
@@ -617,6 +620,7 @@ _Generated from the live command tree by `bun run docs:readme` — do not edit b
 | `mcp tools list` | List tools for a project, or scope to a single server with --server |
 | `mcp tools pull [name]` | Refresh local tool files from the cloud, overwriting any unsaved local edits. Use after `409 conflict` to re-sync. |
 | `mcp tools pull-handler <name>` | Refresh a tool's handler source from the cloud, overwriting any local edits. Use after `409 conflict` to re-sync. |
+| `mcp tools rename [old] [new]` | Rename tools on a server, keeping their ids — access grants, saved test scenarios and composition references follow. Regenerates the stored bundle; deploy to ship the new names. |
 | `mcp tools reset-handler <name>` | Drop the cloud handler override for a tool and re-materialize the codegen default. Prompts to confirm unless --yes is passed. |
 | `mcp tools show <name>` | Show a tool's full applied metadata (and any pending AI suggestion). |