@zibby/mcp-cli 0.3.8 → 0.3.9

package/index.js

@@ -202,16 +202,17 @@ const server = new McpServer({
   version: '0.3.0',
 });
 
-// ── Dual-register helper (product-noun migration: "workflow" → "agent") ──
-// The product UI now calls deployed automations "Agents". We expose every
-// workflow-related tool under BOTH its historical `*_workflow*` name AND a
-// new `*_agent*` name, pointing at the SAME schema + handler. Old names keep
-// working (additive alias, never removed); the agent-named ones are the new
-// primary. Internal CLI verbs / API routes / package names are untouched —
-// only the MCP-facing tool name + description prose change.
-function toolWithAlias(canonicalName, aliasName, description, schema, handler) {
-  server.tool(canonicalName, description, schema, handler);
-  server.tool(aliasName, description, schema, handler);
+// ── Agent-named tool registration (product-noun migration: "workflow" → "agent") ──
+// The product UI now calls deployed automations "Agents". Unlike the CLI —
+// where `agent` is an additive ALIAS and `workflow` stays for muscle memory /
+// scripts — MCP tool names are LLM-facing and surfaced wholesale via
+// tools/list. Registering both `*_workflow*` and `*_agent*` would put 6 exact
+// duplicate pairs in front of the model, cluttering the list and muddying tool
+// selection. So MCP exposes ONLY the agent-named tool. The legacy `*_workflow*`
+// name (first arg) is kept in the call signature for traceability but is no
+// longer registered. Internal CLI verbs / API routes / package names unchanged.
+function toolWithAlias(_legacyWorkflowName, agentName, description, schema, handler) {
+  server.tool(agentName, description, schema, handler);
 }
 
 // ── Tool: login ─────────────────────────────────────────────────────────

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zibby/mcp-cli",
-  "version": "0.3.8",
+  "version": "0.3.9",
   "description": "Zibby local-essential MCP Server — local workflow scaffold/validate/run + deploy/download (bundles local files). Pure-API tools live in the Zibby Remote MCP (api-prod.zibby.app/mcp).",
   "type": "module",
   "main": "index.js",