@ductape/mcp 0.1.8 → 0.1.9

package/dist/index.js

@@ -1123,8 +1123,18 @@ async function main() {
                 '  - 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' +
                 '  - Managing cloud connections and cloud-linked resources\n' +
-                '  - Provisioning cloud resources with a specific tier: "cloud resources provision -f file.json --tier <tier_name>"\n' +
-                '    (list available tiers first with "cloud tiers list --provider <aws|gcp|azure>")\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' +
+                '  - Provisioning and persisting a cloud resource: "cloud resources provision-persist -f file.json --tier <tier_name> --json"\n' +
+                '    The JSON file requires: cloud (connection tag), service (provider service), type (Ductape component type),\n' +
+                '    product (product tag), component (new component tag), and env (existing environment slug).\n' +
+                '    Provider parameters such as region, location, bucketName, dbName, and waitForReady may be supplied in the file.\n' +
+                '    Example GCS Standard file: {"cloud":"gcp-tag","service":"gcs","type":"storage",' +
+                '"product":"product-tag","component":"assets","env":"snd","location":"us-central1"}.\n' +
+                '    Use `provision-persist` when the result must be registered as a Ductape asset; `provision` alone only returns\n' +
+                '    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' +
                 '  - 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.8",
+  "version": "0.1.9",
   "description": "MCP server that exposes Ductape SDK operations via the backend proxy",
   "type": "module",
   "main": "dist/index.js",

package/src/index.ts

@@ -1217,8 +1217,18 @@ async function main() {
           '  - 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' +
           '  - Managing cloud connections and cloud-linked resources\n' +
-          '  - Provisioning cloud resources with a specific tier: "cloud resources provision -f file.json --tier <tier_name>"\n' +
-          '    (list available tiers first with "cloud tiers list --provider <aws|gcp|azure>")\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' +
+          '  - Provisioning and persisting a cloud resource: "cloud resources provision-persist -f file.json --tier <tier_name> --json"\n' +
+          '    The JSON file requires: cloud (connection tag), service (provider service), type (Ductape component type),\n' +
+          '    product (product tag), component (new component tag), and env (existing environment slug).\n' +
+          '    Provider parameters such as region, location, bucketName, dbName, and waitForReady may be supplied in the file.\n' +
+          '    Example GCS Standard file: {"cloud":"gcp-tag","service":"gcs","type":"storage",' +
+          '"product":"product-tag","component":"assets","env":"snd","location":"us-central1"}.\n' +
+          '    Use `provision-persist` when the result must be registered as a Ductape asset; `provision` alone only returns\n' +
+          '    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' +
           '  - 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' +