@ductape/mcp 0.2.20 → 0.2.21

package/dist/index.js

@@ -876,7 +876,8 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
       // ctx.input                – typed runtime input; always compiles to $Input{} operators
       // ctx.sampleInput          – compile-time sample for loop/branch discovery only
       // ctx.step(tag, fn, rollback?, opts?)  – define a durable step
-      // ctx.api.run({ app, event, input }) – call an app action
+      // ctx.api.run({ app, action, input }) – call an app action (NOT 'event' -- that field name
+      //   only applies to ctx.database/ctx.notification/ctx.storage below, never ctx.api/ctx.action)
       // ctx.database.query/insert/update/delete({ database, event, ... })
       // ctx.graph.execute({ graph, action, input })
       // ctx.notification.send/email/push/sms({ notification, event, ... })
@@ -2501,7 +2502,8 @@ Import an existing resource and register it on the product:
   File is a JSON ARRAY — one entry per env, same product + component tag across all entries.
   Each entry: { cloud, service, type, product, component, env, resource, region?, dbName? }
   Supported service identifiers: s3, gcs, blob, rds, postgresql, cloudsql, sqs, pubsub,
-    servicebus, neptune, cosmos-gremlin, opensearch, azure-search, atlas-cluster, aura-instance
+    servicebus, neptune, cosmos-gremlin, opensearch, azure-search, atlas-cluster, aura-instance,
+    vertex-vector-search, spanner-graph, dynamodb, keyspaces, mysql
 
 Provision a brand-new resource and register it:
   ductape_cli("cloud resources provision-persist-all -f all-envs.json --json")
@@ -2509,6 +2511,20 @@ Provision a brand-new resource and register it:
   List available tiers first: ductape_cli("cloud tiers --provider aws --type database --db-type postgresql --json")
   NEVER infer region, tier, or cost — always list and confirm with the user first.
   Atlas and Neo4j Aura are IMPORT-ONLY — provision is not supported for these providers.
+  Per-provider provisionable services: aws → s3, sqs, rds, neptune, opensearch, dynamodb, keyspaces.
+    gcp → gcs, cloudsql, pubsub, spanner-graph, vertex-vector-search.
+    azure → blob, servicebus, postgresql, mysql, cosmos-gremlin, azure-search.
+
+  vertex-vector-search (GCP): additional per-entry params: dimensions (default 1536), metric
+    ("cosine"|"euclidean"|"dotproduct", default cosine), algorithm ("tree-ah"|"brute-force",
+    default tree-ah), deployIndex (default true — set false to create the Index and Index
+    Endpoint without deploying, avoiding ongoing compute cost until you deploy manually),
+    machineType (default "e2-standard-2"), minReplicaCount/maxReplicaCount (default 1).
+    Provisioning creates the Index Endpoint, the actual Index (STREAM_UPDATE method, required
+    for runtime vector.upsert/upsertOne), and deploys the Index to the Endpoint — all three are
+    needed for the result to be queryable. A DEPLOYED index runs dedicated compute continuously
+    (real ongoing cost, not free-tier) — always confirm machine type/replica count with the user
+    before provisioning, the same as any other tier/cost decision.
 
 VPC connector (private networking):
   ductape_cli("cloud connections vpc update <tag> --vpc-id vpc-xxx --subnet-ids subnet-1,subnet-2")
@@ -2680,7 +2696,7 @@ CONNECT A DISCOVERED APP THROUGH MCP:
   obtain user approval when the user has not already requested the connection.
 
 ONLY after all five steps can any code call:
-  ctx.api.run({ app: '<app_tag>', event: '<action_tag>', input: { ... } })   ← in a feature handler
+  ctx.api.run({ app: '<app_tag>', action: '<action_tag>', input: { ... } })   ← in a feature handler
   actions.run([{ product, env, app: '<app_tag>', action: '<action_tag>', input }])   ← at runtime
 
 ctx.api (alias for ctx.action) is NOT a generic HTTP call. It ONLY invokes a pre-registered
@@ -2745,8 +2761,11 @@ Run an action at runtime:
   ductape_execute("actions.dispatch", [{ product, env, app, action, input, schedule? }])
 
 In a Ductape feature handler, call the registered action through:
-  await ctx.api.run({ app: "<app_tag>", event: "<action_tag>", input: { ... } })
+  await ctx.api.run({ app: "<app_tag>", action: "<action_tag>", input: { ... } })
 ctx.api is the supported feature-context surface (also described as ctx.action in older code).
+NEVER use 'event' as the field name here -- that is only correct for ctx.database/ctx.notification/
+ctx.storage steps. ctx.api.run's real field is 'action'; passing 'event' instead silently produces
+an unset step and fails feature compilation with "did not record a portable operation".
 There is no ctx.apps, ctx.integrations, or generic external-HTTP feature surface.
 
 PAYSTACK CONFIGURATION:
@@ -3657,8 +3676,8 @@ STEP 8 — SET rollbacks for reversible steps
   ctx.api.run requires a pre-registered Ductape App — 'stripe' below is the tag of a registered App:
     const charge = await ctx.step(
       'charge',
-      async () => ctx.api.run({ app: 'stripe', event: 'create-charge', input: { amount: ctx.input.amount } }),
-      async (result) => ctx.api.run({ app: 'stripe', event: 'refund', input: { chargeId: result.id } })
+      async () => ctx.api.run({ app: 'stripe', action: 'create-charge', input: { amount: ctx.input.amount } }),
+      async (result) => ctx.api.run({ app: 'stripe', action: 'refund', input: { chargeId: result.id } })
     );
 
 Code-first ctx step types currently record: function | action | database | graph | vector | session |

package/package.json

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