@ductape/mcp 0.1.36 → 0.1.38

package/dist/index.js

@@ -276,19 +276,24 @@ SPECIALIZED MODULES (for injecting handles directly without @InjectContext):
 ALL params are passed as a JSON array in positional order matching the SDK signature.
 
 ━━━ MODULE: product ━━━
+  IMPORTANT: ALL product.* methods require the access key and will return 403 with a publishable key.
+  Use ductape_cli for ALL product operations — never ductape_execute:
+    ductape_cli("products get --tag <tag> --json")           ← fetch product + full inventory
+    ductape_cli("products create --name <name> --tag <tag>")
+    ductape_cli("products environments list <tag> --json")
+    ductape_cli("products environments get <tag> <slug> --json")
+    ductape_cli("products apps list --product <id> --json")
+
+  SDK method signatures (for reference, admin key only):
   product.create        [data: { name, description, tag?, envs?: [{slug, name}] }]
   product.fetch         [product_tag: string]
   product.update        [product_tag: string, data: { name?: string, description?: string }]
-  product.init          [product_tag: string]
-  product.environments.create   [product_tag, data: { slug: string, env_name: string, description: string, active?: boolean }]
-  product.environments.update   [product_tag, slug: string, data: { env_name?: string, description?: string, active?: boolean }]
+  product.environments.create   [product_tag, data: { slug, env_name, description, active? }]
   product.environments.list     [product_tag]
   product.environments.fetch    [product_tag, slug]
-  product.apps.connect  [product_tag, app_tag]
-  product.apps.add      [product_tag, app: { access_tag: string, envs: [{ app_env_slug: string, product_env_slug: string, variables?: [{key: string, value: string}], auth?: { auth_tag: string, data: string|object, expiry?: number } }] }]
+  product.apps.add      [product_tag, app: { access_tag, envs: [{ app_env_slug, product_env_slug, variables?, auth? }] }]
   product.apps.list     [product_tag]
   product.apps.fetch    [product_tag, access_tag]
-  product.apps.update   [product_tag, access_tag: string, data: { version?: string, envs?: [{ app_env_slug: string, product_env_slug: string, variables?: [{key: string, value: string}], auth?: { auth_tag: string, data: string|object, expiry?: number } }] }]
 
 ━━━ MODULE: app ━━━
   app.create    [data: { app_name: string, description: string, unique?: boolean }]
@@ -1769,14 +1774,10 @@ Variables (per-env mutable values) and Constants (fixed values):
   ductape_execute("app.constants.create", [app_tag, { key, value }])
 
 Connecting an app to a product (after creation):
-  ductape_execute("product.apps.add", [product_tag, {
-    access_tag: "app_access_tag",
-    envs: [{ app_env_slug: "production", product_env_slug: "prd",
-             variables: [{ key: "BASE_URL", value: "https://api.example.com" }],
-             auth: { auth_tag: "api-key-auth", data: "$Secret{API_KEY}" } }]
-  }])
-  ductape_execute("product.apps.list",   [product_tag])
-  ductape_execute("product.apps.fetch",  [product_tag, access_tag])
+  NOTE: All product.* module methods require the access key and CANNOT use ductape_execute (publishable key only).
+  Use ductape_cli for all product-level operations:
+  ductape_cli("products apps list --product <product_id> --json")
+  ductape_cli("products get --tag <product_tag> --json")    ← includes apps[], databases[], features[] etc.
 `.trim(),
     products: `
 DUCTAPE PRODUCTS
@@ -1785,20 +1786,20 @@ A product is the top-level namespace for all Ductape infrastructure: apps, datab
 vectors, storage, brokers, sessions, caches, notifications, resilience, features, jobs, and envs.
 Every SDK service call resolves within a product context.
 
+IMPORTANT: The product module requires the access key. ALL product operations must use ductape_cli,
+not ductape_execute (which only accepts the publishable key and will return 403 for product.*).
+
 Create a product:
   ductape_cli("products create --name \\"My App\\" --tag my-app")
-  ductape_execute("product.create", [{ name: "My App", tag: "my-app",
-    envs: [{ slug: "dev", name: "Development" }, { slug: "prd", name: "Production" }] }])
 
 Environments — every resource's envs array MUST cover all product env slugs:
-  ductape_execute("product.environments.create", [product_tag, { slug, env_name, description, active? }])
-  ductape_execute("product.environments.list",   [product_tag])
-  ductape_execute("product.environments.fetch",  [product_tag, slug])
-  BEFORE registering any resource, always run environments.list and collect all slugs.
+  ductape_cli("products environments list <product_tag> --json")
+  ductape_cli("products environments get <product_tag> <slug> --json")
+  BEFORE registering any resource, always run environments list and collect all slugs.
 
 Fetch / update:
-  ductape_execute("product.fetch",  [product_tag])
-  ductape_execute("product.update", [product_tag, { name?, description? }])
+  ductape_cli("products get --tag <product_tag> --json")
+  ductape_cli("products get --id <product_id> --json")
 
 Connect apps to a product:
   See ductape_docs({ topic: "apps" }) for product.apps.add / product.apps.list.
@@ -2081,15 +2082,16 @@ STEP 1 — UNDERSTAND the goal
   understand: what the feature does, what it returns, what can fail and how failures should behave.
 
 STEP 2 — INVENTORY existing Ductape components
-  Call ductape_execute("products.fetch", [product_tag]) to read the product.
+  Call ductape_cli("products get --tag <product_tag> --json") to read the full product document.
+  (product.* requires the access key — never use ductape_execute for product reads, it will return 403)
   Note what already exists:
     - databases[]      → available for ctx.database.insert/query/update/delete steps
     - apps[]           → available for ctx.api.run steps (check app.events[] for event tags)
     - notifications[]  → available for ctx.notification.email/sms/push steps
     - storage[]        → available for ctx.storage.upload/download steps
-    - messageBrokers[] → available for ctx.messaging.produce steps
+    - messageBrokers[] → available for ctx.events.produce steps
     - graphs[]         → available for ctx.graph steps
-    - features[]       → can be called as child features via ctx.feature()
+    - features[]       → can be called as child features via ctx.feature.execute()
     - caches[], sessions[]
   Do NOT assume a component or event tag exists — verify from the product before using it.
 

package/package.json

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

package/src/index.ts

@@ -287,19 +287,24 @@ SPECIALIZED MODULES (for injecting handles directly without @InjectContext):
 ALL params are passed as a JSON array in positional order matching the SDK signature.
 
 ━━━ MODULE: product ━━━
+  IMPORTANT: ALL product.* methods require the access key and will return 403 with a publishable key.
+  Use ductape_cli for ALL product operations — never ductape_execute:
+    ductape_cli("products get --tag <tag> --json")           ← fetch product + full inventory
+    ductape_cli("products create --name <name> --tag <tag>")
+    ductape_cli("products environments list <tag> --json")
+    ductape_cli("products environments get <tag> <slug> --json")
+    ductape_cli("products apps list --product <id> --json")
+
+  SDK method signatures (for reference, admin key only):
   product.create        [data: { name, description, tag?, envs?: [{slug, name}] }]
   product.fetch         [product_tag: string]
   product.update        [product_tag: string, data: { name?: string, description?: string }]
-  product.init          [product_tag: string]
-  product.environments.create   [product_tag, data: { slug: string, env_name: string, description: string, active?: boolean }]
-  product.environments.update   [product_tag, slug: string, data: { env_name?: string, description?: string, active?: boolean }]
+  product.environments.create   [product_tag, data: { slug, env_name, description, active? }]
   product.environments.list     [product_tag]
   product.environments.fetch    [product_tag, slug]
-  product.apps.connect  [product_tag, app_tag]
-  product.apps.add      [product_tag, app: { access_tag: string, envs: [{ app_env_slug: string, product_env_slug: string, variables?: [{key: string, value: string}], auth?: { auth_tag: string, data: string|object, expiry?: number } }] }]
+  product.apps.add      [product_tag, app: { access_tag, envs: [{ app_env_slug, product_env_slug, variables?, auth? }] }]
   product.apps.list     [product_tag]
   product.apps.fetch    [product_tag, access_tag]
-  product.apps.update   [product_tag, access_tag: string, data: { version?: string, envs?: [{ app_env_slug: string, product_env_slug: string, variables?: [{key: string, value: string}], auth?: { auth_tag: string, data: string|object, expiry?: number } }] }]
 
 ━━━ MODULE: app ━━━
   app.create    [data: { app_name: string, description: string, unique?: boolean }]
@@ -733,7 +738,7 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
     handler: async (ctx) => {
       // ctx.input                – typed feature input
       // ctx.step(tag, fn, rollback?, opts?)  – define a durable step
-      // ctx.action.run({ app, event, input }) – call an app action
+      // ctx.api.run({ app, event, input }) – call an app action
       // ctx.database.query/insert/update/delete({ database, event, ... })
       // ctx.graph.execute({ graph, action, input })
       // ctx.notification.send/email/push/sms({ notification, event, ... })
@@ -1835,14 +1840,10 @@ Variables (per-env mutable values) and Constants (fixed values):
   ductape_execute("app.constants.create", [app_tag, { key, value }])
 
 Connecting an app to a product (after creation):
-  ductape_execute("product.apps.add", [product_tag, {
-    access_tag: "app_access_tag",
-    envs: [{ app_env_slug: "production", product_env_slug: "prd",
-             variables: [{ key: "BASE_URL", value: "https://api.example.com" }],
-             auth: { auth_tag: "api-key-auth", data: "$Secret{API_KEY}" } }]
-  }])
-  ductape_execute("product.apps.list",   [product_tag])
-  ductape_execute("product.apps.fetch",  [product_tag, access_tag])
+  NOTE: All product.* module methods require the access key and CANNOT use ductape_execute (publishable key only).
+  Use ductape_cli for all product-level operations:
+  ductape_cli("products apps list --product <product_id> --json")
+  ductape_cli("products get --tag <product_tag> --json")    ← includes apps[], databases[], features[] etc.
 `.trim(),
 
   products: `
@@ -1852,20 +1853,20 @@ A product is the top-level namespace for all Ductape infrastructure: apps, datab
 vectors, storage, brokers, sessions, caches, notifications, resilience, features, jobs, and envs.
 Every SDK service call resolves within a product context.
 
+IMPORTANT: The product module requires the access key. ALL product operations must use ductape_cli,
+not ductape_execute (which only accepts the publishable key and will return 403 for product.*).
+
 Create a product:
   ductape_cli("products create --name \\"My App\\" --tag my-app")
-  ductape_execute("product.create", [{ name: "My App", tag: "my-app",
-    envs: [{ slug: "dev", name: "Development" }, { slug: "prd", name: "Production" }] }])
 
 Environments — every resource's envs array MUST cover all product env slugs:
-  ductape_execute("product.environments.create", [product_tag, { slug, env_name, description, active? }])
-  ductape_execute("product.environments.list",   [product_tag])
-  ductape_execute("product.environments.fetch",  [product_tag, slug])
-  BEFORE registering any resource, always run environments.list and collect all slugs.
+  ductape_cli("products environments list <product_tag> --json")
+  ductape_cli("products environments get <product_tag> <slug> --json")
+  BEFORE registering any resource, always run environments list and collect all slugs.
 
 Fetch / update:
-  ductape_execute("product.fetch",  [product_tag])
-  ductape_execute("product.update", [product_tag, { name?, description? }])
+  ductape_cli("products get --tag <product_tag> --json")
+  ductape_cli("products get --id <product_id> --json")
 
 Connect apps to a product:
   See ductape_docs({ topic: "apps" }) for product.apps.add / product.apps.list.
@@ -2153,15 +2154,16 @@ STEP 1 — UNDERSTAND the goal
   understand: what the feature does, what it returns, what can fail and how failures should behave.
 
 STEP 2 — INVENTORY existing Ductape components
-  Call ductape_execute("products.fetch", [product_tag]) to read the product.
+  Call ductape_cli("products get --tag <product_tag> --json") to read the full product document.
+  (product.* requires the access key — never use ductape_execute for product reads, it will return 403)
   Note what already exists:
     - databases[]      → available for ctx.database.insert/query/update/delete steps
-    - apps[]           → available for ctx.action.run steps (check app.events[] for event tags)
+    - apps[]           → available for ctx.api.run steps (check app.events[] for event tags)
     - notifications[]  → available for ctx.notification.email/sms/push steps
     - storage[]        → available for ctx.storage.upload/download steps
-    - messageBrokers[] → available for ctx.messaging.produce steps
+    - messageBrokers[] → available for ctx.events.produce steps
     - graphs[]         → available for ctx.graph steps
-    - features[]       → can be called as child features via ctx.feature()
+    - features[]       → can be called as child features via ctx.feature.execute()
     - caches[], sessions[]
   Do NOT assume a component or event tag exists — verify from the product before using it.
 
@@ -2214,8 +2216,8 @@ STEP 8 — SET rollbacks for reversible steps
   Any step that allocates a resource should undo it if a later step fails:
     const charge = await ctx.step(
       'charge',
-      async () => ctx.action.run({ app: 'stripe', event: 'create-charge', input: { amount: ctx.input.amount } }),
-      async (result) => ctx.action.run({ app: 'stripe', event: 'refund', input: { chargeId: result.id } })
+      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 } })
     );
 
 Step types: action | database | graph | notification | storage | produce | quota | fallback |