@ductape/mcp 0.1.18 → 0.1.19

package/dist/index.js

@@ -297,9 +297,10 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
     description?: string, sample?: object, idempotent?: boolean,
     queueUrls?: [{ env_slug: string, url: string }]  // SQS only: per-env queue URL per topic
   }]
+  ← OPTIONAL for most providers: creating a producer automatically creates the topic if it does not exist.
+  ← Only required explicitly for SQS (must supply queueUrls per env) or when you want to set sample/idempotent upfront.
+  ← For Pub/Sub, Kafka, RabbitMQ, Redis, NATS: skip this — let producer creation handle it.
   ← A broker can have unlimited topics. Add one per logical event type.
-  ← For SQS: each topic needs queueUrls mapping env slug → the SQS queue URL for that topic+env.
-  ← For Pub/Sub and Service Bus: topic name resolves from the tag or broker env config; no queueUrls needed.
   messageBrokers.topics.update [product_tag, topic_tag, data: { name?: string, description?: string,
     sample?: object, idempotent?: boolean, queueUrls?: [{ env_slug: string, url: string }] }]
   messageBrokers.topics.fetch  [product_tag, topic_tag]
@@ -2034,8 +2035,17 @@ Import (register an EXISTING cloud resource):
     redis:    { host: "...", port: 6379, password?: "..." }
     nats:     { servers: ["nats://host:4222"], token?: "...", user?: "...", pass?: "...", tls?: true }
 
-━━━ STEP 2: ADD TOPIC DEFINITIONS (all broker types — add as many as needed) ━━━
+━━━ STEP 2: ADD TOPIC DEFINITIONS ━━━
 
+  For most providers (GCP Pub/Sub, Kafka, RabbitMQ, Redis, NATS, Azure Service Bus):
+  SKIP this step. Topics are auto-created when you create a producer (step 3).
+  You do NOT need to call messageBrokers.topics.create before creating a producer.
+
+  Only call topics.create explicitly when:
+    - Using AWS SQS (must supply queueUrls per env — auto-creation cannot know the queue URL)
+    - You want to pre-set sample data or idempotency config on the topic
+
+  If you do need it (SQS or explicit config):
   ductape_execute("messageBrokers.topics.create", [product_tag, {
     tag: "player-joined",
     name: "Player Joined",
@@ -2050,11 +2060,6 @@ Import (register an EXISTING cloud resource):
     ]
   }])
 
-  For GCP Pub/Sub and Azure Service Bus, the SDK resolves the topic name from the topic tag (or
-  config.topicName on the env config). No extra per-topic URL mapping is needed beyond the tag.
-  For SQS, every topic definition needs queueUrls to point to the specific per-env queue.
-  Repeat this call for each logical event type — there is no limit on number of topics.
-
   List topics on a broker:
     ductape_execute("messageBrokers.topics.list", [product_tag, "broker-tag"])
 
@@ -2485,7 +2490,7 @@ async function main() {
                 '    GCP Pub/Sub service identifier is "pubsub". AWS SQS is "sqs". Azure Service Bus is "servicebus".\n' +
                 '    Message brokers are import-only (no provision-persist). Import flow is the same as storage.\n' +
                 '    type field = "messageBrokers" (not "messagebrokers" or "events").\n' +
-                '    After importing, create topics via: ductape_execute("messageBrokers.topics.create", [product_tag, data])\n' +
+                '    After importing, create producers — topics are auto-created with the producer (except SQS, which needs explicit topics.create with queueUrls first).\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.18",
+  "version": "0.1.19",
   "description": "MCP server that exposes Ductape SDK operations via the backend proxy",
   "type": "module",
   "main": "dist/index.js",

package/src/index.ts

@@ -308,9 +308,10 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
     description?: string, sample?: object, idempotent?: boolean,
     queueUrls?: [{ env_slug: string, url: string }]  // SQS only: per-env queue URL per topic
   }]
+  ← OPTIONAL for most providers: creating a producer automatically creates the topic if it does not exist.
+  ← Only required explicitly for SQS (must supply queueUrls per env) or when you want to set sample/idempotent upfront.
+  ← For Pub/Sub, Kafka, RabbitMQ, Redis, NATS: skip this — let producer creation handle it.
   ← A broker can have unlimited topics. Add one per logical event type.
-  ← For SQS: each topic needs queueUrls mapping env slug → the SQS queue URL for that topic+env.
-  ← For Pub/Sub and Service Bus: topic name resolves from the tag or broker env config; no queueUrls needed.
   messageBrokers.topics.update [product_tag, topic_tag, data: { name?: string, description?: string,
     sample?: object, idempotent?: boolean, queueUrls?: [{ env_slug: string, url: string }] }]
   messageBrokers.topics.fetch  [product_tag, topic_tag]
@@ -2103,8 +2104,17 @@ Import (register an EXISTING cloud resource):
     redis:    { host: "...", port: 6379, password?: "..." }
     nats:     { servers: ["nats://host:4222"], token?: "...", user?: "...", pass?: "...", tls?: true }
 
-━━━ STEP 2: ADD TOPIC DEFINITIONS (all broker types — add as many as needed) ━━━
+━━━ STEP 2: ADD TOPIC DEFINITIONS ━━━
 
+  For most providers (GCP Pub/Sub, Kafka, RabbitMQ, Redis, NATS, Azure Service Bus):
+  SKIP this step. Topics are auto-created when you create a producer (step 3).
+  You do NOT need to call messageBrokers.topics.create before creating a producer.
+
+  Only call topics.create explicitly when:
+    - Using AWS SQS (must supply queueUrls per env — auto-creation cannot know the queue URL)
+    - You want to pre-set sample data or idempotency config on the topic
+
+  If you do need it (SQS or explicit config):
   ductape_execute("messageBrokers.topics.create", [product_tag, {
     tag: "player-joined",
     name: "Player Joined",
@@ -2119,11 +2129,6 @@ Import (register an EXISTING cloud resource):
     ]
   }])
 
-  For GCP Pub/Sub and Azure Service Bus, the SDK resolves the topic name from the topic tag (or
-  config.topicName on the env config). No extra per-topic URL mapping is needed beyond the tag.
-  For SQS, every topic definition needs queueUrls to point to the specific per-env queue.
-  Repeat this call for each logical event type — there is no limit on number of topics.
-
   List topics on a broker:
     ductape_execute("messageBrokers.topics.list", [product_tag, "broker-tag"])
 
@@ -2611,7 +2616,7 @@ async function main() {
           '    GCP Pub/Sub service identifier is "pubsub". AWS SQS is "sqs". Azure Service Bus is "servicebus".\n' +
           '    Message brokers are import-only (no provision-persist). Import flow is the same as storage.\n' +
           '    type field = "messageBrokers" (not "messagebrokers" or "events").\n' +
-          '    After importing, create topics via: ductape_execute("messageBrokers.topics.create", [product_tag, data])\n' +
+          '    After importing, create producers — topics are auto-created with the producer (except SQS, which needs explicit topics.create with queueUrls first).\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' +