@ductape/mcp 0.1.9 → 0.1.11

package/dist/index.js

@@ -65,6 +65,23 @@ There are THREE categories of operations. Use the right tool for each:
        cloud connections, and secrets. Environments, app actions, auths, features, quotas,
        fallbacks, jobs, and healthchecks are configured in the Workbench UI.
 
+       ⚠ MULTI-ENV REQUIREMENT — applies to ALL product assets (storage, database, cache,
+       messageBroker, graph, vector, and any other resource with an envs array):
+       The envs array MUST contain one entry for EVERY environment defined on the product.
+       Omitting an env causes a validation error ("env X is not defined, please provide
+       connection details"). You cannot scope an asset to a subset of environments.
+
+       BEFORE constructing any resource file:
+         1. Run: ductape_cli("products environments list <product_tag> --json")
+         2. Note every slug returned (e.g. dev, snd, prd).
+         3. Collect connection details or confirmation for EACH slug from the user.
+
+       Sharing one resource across multiple envs is allowed but must be confirmed per env:
+         - Ask the user explicitly: "Should <env> use the same <resource> as <other_env>?"
+         - Never assume shared configuration without confirmation.
+         - For cloud-linked envs, set config.cloud to the connection tag for that env and
+           omit raw credentials; the cloud connection must exist for that env too.
+
   2. RUNTIME OPERATIONS  (run, dispatch, execute, start, send, produce, query, insert, update, delete…)
        The "input" field shape is product- and operation-specific — it is NOT derivable from Joi validators.
        It is defined by how the product's action/feature/session/quota/etc. was configured in Ductape.
@@ -636,7 +653,8 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
     "graphs.create", "graphs.update", "vectors.create", "vectors.update",
     "sessions.create", "sessions.update", "healthchecks.create",
     "quotas.create", "quotas.update", "functions.create", "functions.update",
-    "agents.create", "agents.update", "models.create", "models.update"
+    "agents.create", "agents.update", "models.create", "models.update",
+    "storage.create", "storage.update"
 
   When to use this tool:
   - Before calling ductape_execute to create or update any asset — use this to discover required fields
@@ -1112,7 +1130,14 @@ async function main() {
             description: 'Returns the full field manifest for Ductape asset creation/update methods, ' +
                 'derived live from the SDK Joi validators. Includes field types, required flags, ' +
                 'enum values, nested structures, and all enum constants. ' +
-                'Pass module="app" or module="product" to scope the result.',
+                'Pass module="app" or module="product" to scope the result.\n\n' +
+                'ALWAYS call this before constructing a file for "resources <type> create" or any cloud ' +
+                'import/provision operation — field shapes are not guessable from context.\n\n' +
+                'Conditional fields: some fields are returned as oneOf (an array of variant shapes). ' +
+                'For example, storage.create envs[].config is oneOf [awsConfig, gcpConfig, azureConfig] — ' +
+                'pick the variant whose fields match the envs[].type value (aws/gcp/azure). ' +
+                'Fields inside oneOf variants are context-dependent and should all be treated as optional ' +
+                'unless the chosen variant explicitly marks them required.',
             inputSchema: schemaInputSchema,
         }, schemaHandler);
         server.registerTool('ductape_cli', {
@@ -1122,6 +1147,28 @@ async function main() {
                 '  - Creating or updating products (products create/update) and apps (apps create/update)\n' +
                 '  - Importing an app from a Postman v2.1 or OpenAPI 3.0 file: "apps import <file> -t postman|openapi"\n' +
                 '  - Managing resources via "resources <type> <verb>" (databases, storage, caches…)\n' +
+                '    ALWAYS call ductape_schema(module="product") first to get the exact field shape before\n' +
+                '    constructing a file. Storage envs[].config is conditional on envs[].type (aws/gcp/azure)\n' +
+                '    and returned as oneOf — pick the variant matching the type.\n' +
+                '    REQUIRED: before building any resource file, run\n' +
+                '      ductape_cli("products environments list <product_tag> --json")\n' +
+                '    and include an envs entry for EVERY environment returned. Omitting any env causes a\n' +
+                '    validation error. If the user has not supplied connection details for every env, ask\n' +
+                '    them explicitly. Confirm per-env before reusing the same resource across environments.\n' +
+                '  - Three distinct storage registration flows — choose the right one:\n' +
+                '    1. Manual credentials (bucket already exists, you supply keys directly):\n' +
+                '         resources storage create -f storage.json\n' +
+                '       File shape: { name, tag, envs: [{ slug, type: "aws"|"gcp"|"azure", config: { bucketName, ...creds } }] }\n' +
+                '       For cloud-linked envs set config.cloud to the connection tag and omit raw credentials.\n' +
+                '    2. Import an existing cloud bucket via a cloud connection (no provisioning):\n' +
+                '         cloud resources import-persist -f import.json --json\n' +
+                '       File requires: cloud (connection tag), service (e.g. "gcs","s3"), type ("storage"),\n' +
+                '       product, component (new tag), env, and the existing bucket identifier (e.g. bucketName).\n' +
+                '       Example: {"cloud":"gcp-conn","service":"gcs","type":"storage","product":"my-product",\n' +
+                '       "component":"assets","env":"snd","bucketName":"my-existing-bucket"}.\n' +
+                '       If import-persist fails, the error message now reports both the create failure and the\n' +
+                '       update fallback failure — read both to diagnose. Do not retry blindly.\n' +
+                '    3. Provision a brand-new bucket AND register it (see provision-persist docs below).\n' +
                 '  - Managing cloud connections and cloud-linked resources\n' +
                 '  - Discovering cloud tiers: "cloud tiers --provider <provider> --type <database|storage> [--db-type <type>] --json"\n' +
                 '    IMPORTANT: `cloud tiers` has no `list` verb. Use only a tier returned for the selected provider/type.\n' +
@@ -1135,6 +1182,11 @@ async function main() {
                 '    the provider resource and component draft. Tier discovery does not by itself prove that a connection supports\n' +
                 '    provisioning that service: if provisioning reports an unsupported provider/service pair, stop and report it.\n' +
                 '    Never infer an environment, provider service, region, tier, or cost. List/verify each before provisioning.\n' +
+                '  - Known provisioning limitations: MongoDB Atlas (M0 free tier) and Neo4j Aura cannot be provisioned via\n' +
+                '    Ductape — they are import-only. Only AWS, GCP, and Azure managed services support provision-persist.\n' +
+                '    Supported service/component pairs include: rds→database, aurora→database, gcs→storage, s3→storage,\n' +
+                '    azure-blob→storage, cloud-sql→database, neptune→graph, opensearch→vector. Attempting an unsupported pair\n' +
+                '    will return an error; do not retry with a different tier — report the limitation to the user.\n' +
                 '  - Listing workspaces, products, secrets\n' +
                 '  - Linking a project folder: "link --product <tag> --env <slug>"\n' +
                 '  - Syncing sessions/notifications/events: "apply" or "apply sessions" etc.\n' +

package/package.json

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

package/src/index.ts

@@ -76,6 +76,23 @@ There are THREE categories of operations. Use the right tool for each:
        cloud connections, and secrets. Environments, app actions, auths, features, quotas,
        fallbacks, jobs, and healthchecks are configured in the Workbench UI.
 
+       ⚠ MULTI-ENV REQUIREMENT — applies to ALL product assets (storage, database, cache,
+       messageBroker, graph, vector, and any other resource with an envs array):
+       The envs array MUST contain one entry for EVERY environment defined on the product.
+       Omitting an env causes a validation error ("env X is not defined, please provide
+       connection details"). You cannot scope an asset to a subset of environments.
+
+       BEFORE constructing any resource file:
+         1. Run: ductape_cli("products environments list <product_tag> --json")
+         2. Note every slug returned (e.g. dev, snd, prd).
+         3. Collect connection details or confirmation for EACH slug from the user.
+
+       Sharing one resource across multiple envs is allowed but must be confirmed per env:
+         - Ask the user explicitly: "Should <env> use the same <resource> as <other_env>?"
+         - Never assume shared configuration without confirmation.
+         - For cloud-linked envs, set config.cloud to the connection tag for that env and
+           omit raw credentials; the cloud connection must exist for that env too.
+
   2. RUNTIME OPERATIONS  (run, dispatch, execute, start, send, produce, query, insert, update, delete…)
        The "input" field shape is product- and operation-specific — it is NOT derivable from Joi validators.
        It is defined by how the product's action/feature/session/quota/etc. was configured in Ductape.
@@ -647,7 +664,8 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
     "graphs.create", "graphs.update", "vectors.create", "vectors.update",
     "sessions.create", "sessions.update", "healthchecks.create",
     "quotas.create", "quotas.update", "functions.create", "functions.update",
-    "agents.create", "agents.update", "models.create", "models.update"
+    "agents.create", "agents.update", "models.create", "models.update",
+    "storage.create", "storage.update"
 
   When to use this tool:
   - Before calling ductape_execute to create or update any asset — use this to discover required fields
@@ -1201,7 +1219,14 @@ async function main() {
           'Returns the full field manifest for Ductape asset creation/update methods, ' +
           'derived live from the SDK Joi validators. Includes field types, required flags, ' +
           'enum values, nested structures, and all enum constants. ' +
-          'Pass module="app" or module="product" to scope the result.',
+          'Pass module="app" or module="product" to scope the result.\n\n' +
+          'ALWAYS call this before constructing a file for "resources <type> create" or any cloud ' +
+          'import/provision operation — field shapes are not guessable from context.\n\n' +
+          'Conditional fields: some fields are returned as oneOf (an array of variant shapes). ' +
+          'For example, storage.create envs[].config is oneOf [awsConfig, gcpConfig, azureConfig] — ' +
+          'pick the variant whose fields match the envs[].type value (aws/gcp/azure). ' +
+          'Fields inside oneOf variants are context-dependent and should all be treated as optional ' +
+          'unless the chosen variant explicitly marks them required.',
         inputSchema: schemaInputSchema,
       },
       schemaHandler,
@@ -1216,6 +1241,28 @@ async function main() {
           '  - Creating or updating products (products create/update) and apps (apps create/update)\n' +
           '  - Importing an app from a Postman v2.1 or OpenAPI 3.0 file: "apps import <file> -t postman|openapi"\n' +
           '  - Managing resources via "resources <type> <verb>" (databases, storage, caches…)\n' +
+          '    ALWAYS call ductape_schema(module="product") first to get the exact field shape before\n' +
+          '    constructing a file. Storage envs[].config is conditional on envs[].type (aws/gcp/azure)\n' +
+          '    and returned as oneOf — pick the variant matching the type.\n' +
+          '    REQUIRED: before building any resource file, run\n' +
+          '      ductape_cli("products environments list <product_tag> --json")\n' +
+          '    and include an envs entry for EVERY environment returned. Omitting any env causes a\n' +
+          '    validation error. If the user has not supplied connection details for every env, ask\n' +
+          '    them explicitly. Confirm per-env before reusing the same resource across environments.\n' +
+          '  - Three distinct storage registration flows — choose the right one:\n' +
+          '    1. Manual credentials (bucket already exists, you supply keys directly):\n' +
+          '         resources storage create -f storage.json\n' +
+          '       File shape: { name, tag, envs: [{ slug, type: "aws"|"gcp"|"azure", config: { bucketName, ...creds } }] }\n' +
+          '       For cloud-linked envs set config.cloud to the connection tag and omit raw credentials.\n' +
+          '    2. Import an existing cloud bucket via a cloud connection (no provisioning):\n' +
+          '         cloud resources import-persist -f import.json --json\n' +
+          '       File requires: cloud (connection tag), service (e.g. "gcs","s3"), type ("storage"),\n' +
+          '       product, component (new tag), env, and the existing bucket identifier (e.g. bucketName).\n' +
+          '       Example: {"cloud":"gcp-conn","service":"gcs","type":"storage","product":"my-product",\n' +
+          '       "component":"assets","env":"snd","bucketName":"my-existing-bucket"}.\n' +
+          '       If import-persist fails, the error message now reports both the create failure and the\n' +
+          '       update fallback failure — read both to diagnose. Do not retry blindly.\n' +
+          '    3. Provision a brand-new bucket AND register it (see provision-persist docs below).\n' +
           '  - Managing cloud connections and cloud-linked resources\n' +
           '  - Discovering cloud tiers: "cloud tiers --provider <provider> --type <database|storage> [--db-type <type>] --json"\n' +
           '    IMPORTANT: `cloud tiers` has no `list` verb. Use only a tier returned for the selected provider/type.\n' +
@@ -1229,6 +1276,11 @@ async function main() {
           '    the provider resource and component draft. Tier discovery does not by itself prove that a connection supports\n' +
           '    provisioning that service: if provisioning reports an unsupported provider/service pair, stop and report it.\n' +
           '    Never infer an environment, provider service, region, tier, or cost. List/verify each before provisioning.\n' +
+          '  - Known provisioning limitations: MongoDB Atlas (M0 free tier) and Neo4j Aura cannot be provisioned via\n' +
+          '    Ductape — they are import-only. Only AWS, GCP, and Azure managed services support provision-persist.\n' +
+          '    Supported service/component pairs include: rds→database, aurora→database, gcs→storage, s3→storage,\n' +
+          '    azure-blob→storage, cloud-sql→database, neptune→graph, opensearch→vector. Attempting an unsupported pair\n' +
+          '    will return an error; do not retry with a different tier — report the limitation to the user.\n' +
           '  - Listing workspaces, products, secrets\n' +
           '  - Linking a project folder: "link --product <tag> --env <slug>"\n' +
           '  - Syncing sessions/notifications/events: "apply" or "apply sessions" etc.\n' +