@ductape/mcp 0.2.26 → 0.2.27

package/dist/index.js

@@ -780,11 +780,19 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
   databases.migration.rollback [migrations, count?]
   databases.migration.history []
   databases.migration.status [migrations]
-  databases.action.create [{ product, database, data: { tag, name, description?, type:"sql"|"nosql", query } }]
-  databases.action.update [{ product: string, tag: string, data: { name?: string, description?: string, query?: string } }]
-  databases.action.fetch  [action_tag]
-  databases.action.list   [database_tag]
-  databases.action.delete [action_tag]
+  databases.action.create [{ tag: "product:database:action", name, tableName, operation: "query"|"insert"|"update"|"delete"|"upsert"|"aggregate"|"rawSql", template: { where?, select?, limit?, offset?, orderBy?, records?, query?, params?, ... }, description?, filterTemplate? }]
+    ← ADMINISTRATIVE (access key required). FORBIDDEN via ductape_execute (publishable key) —
+      use ductape_cli("db actions create -f action.json") instead. tag MUST be fully qualified
+      "product_tag:database_tag:action_tag" — a 2-part "database:action" shorthand only resolves
+      inside a long-lived process that already has that product's builder cached, never in a
+      fresh CLI/MCP call. This is pure metadata registration; it never connects to the live
+      database, so it does NOT require the database to be reachable at call time.
+  databases.action.update [{ tag, name?, description?, template?, filterTemplate? }]
+    ← ADMINISTRATIVE. Use ductape_cli("db actions update --tag <tag> -f patch.json").
+  databases.action.fetch  [action_tag]  ← read-only, safe via ductape_execute
+  databases.action.fetchAll [database_tag]  ← read-only, safe via ductape_execute.
+    NOTE: the method is fetchAll — "action.list" is not a callable method on this sub-object.
+  databases.action.delete [action_tag]  ← ADMINISTRATIVE. Use ductape_cli("db actions delete <tag>").
   databases.action.dispatch [{ product, env, database, action, input, schedule? }]  ← CALL ductape_generate_payload FIRST (operation_family="database", method="dispatch", targets={database: "db_tag", table: "table_name"}) — requires redisUrl in ductape initialization
   databases.dispatch [{ product, env, database, action, input, schedule? }]  ← CALL ductape_generate_payload FIRST (operation_family="database", method="dispatch", targets={database: "db_tag", table: "table_name"}) — requires redisUrl in ductape initialization
   databases.beginTransaction [{ product, env, database, isolationLevel?: "READ_COMMITTED"|"REPEATABLE_READ"|"SERIALIZABLE" }]
@@ -2399,10 +2407,30 @@ DUCTAPE DATABASE PERFORMANCE GUIDANCE
     actions: `
 DUCTAPE DATABASE ACTIONS
 
-A database action is a saved query or mutation (SQL string or NoSQL command) stored
-on the Ductape product and executed by tag at runtime.
-
-Create/update actions in Workbench (administrative access), never through ductape_execute.
+A database action is a saved, parameterized query or mutation template (with {{placeholder}}
+fields) stored on a database component and executed by tag at runtime. This is what
+ctx.database.query/insert/update/delete inside a Feature step actually calls via its
+\`event\` field — Features do NOT accept the top-level {table, where} shape that
+sdk.databases.query/insert/update use outside of a Feature.
+
+Create/update/delete are ADMINISTRATIVE (access key) — FORBIDDEN through ductape_execute
+(publishable key). Use ductape_cli, same as every other admin resource:
+  ductape_cli("db actions create -f action.json")
+    File: { tag: "product:database:action", name, tableName,
+             operation: "query"|"insert"|"update"|"delete"|"upsert"|"aggregate"|"rawSql",
+             template: { where?, select?, limit?, offset?, orderBy?, records?, query?, params? },
+             description?, filterTemplate? }
+    tag MUST be fully qualified "product_tag:database_tag:action_tag" — the SDK's 2-part
+    "database:action" shorthand only works inside one already-warm process, never a fresh CLI call.
+    This is pure metadata registration — it does not connect to the live database, so the
+    database does not need to be reachable at creation time.
+  ductape_cli("db actions update --tag <tag> -f patch.json")
+  ductape_cli("db actions delete <tag>")
+
+List/fetch are read-only and safe via ductape_execute:
+  ductape_execute("databases.action.fetchAll", ["product_tag:database_tag"])
+    NOTE: the method is fetchAll — "action.list" is not a callable method on this sub-object.
+  ductape_execute("databases.action.fetch",  ["product_tag:database_tag:action_tag"])
 
 Dispatch an action at runtime:
   → CALL ductape_generate_payload FIRST to get the canonical input shape.
@@ -2414,13 +2442,6 @@ Dispatch an action at runtime:
     input: { status: "active" },
   }])
 
-List actions for a database:
-  ductape_execute("databases.action.list", ["database_tag"])
-
-Fetch:
-  ductape_execute("databases.action.fetch",  ["action_tag"])
-Update/delete are administrative and must be performed in Workbench.
-
 Actions are the preferred way to encapsulate complex or reused queries — they can be
 scheduled, dispatched with retries, and audited via logs.
 `.trim(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ductape/mcp",
-  "version": "0.2.26",
+  "version": "0.2.27",
   "description": "MCP server that exposes Ductape SDK operations via the backend proxy",
   "type": "module",
   "main": "dist/index.js",