@ductape/mcp 0.2.25 → 0.2.26

package/dist/index.js

@@ -6146,24 +6146,33 @@ async function main() {
                 '  - Atlas (MongoDB Atlas) import flow — service identifier is "atlas-cluster" (required, not optional):\n' +
                 '    IMPORTANT: dbName is mandatory for every MongoDB env — see "MONGODB CLOUD CONNECTION RULE" in the\n' +
                 '    databases module above. The SDK enforces this at create time; omitting it throws a validation error.\n' +
+                '    An existing Atlas cluster is NEVER a blocker. Atlas has no concept of provisioning a new cluster\n' +
+                '    per database — a MongoDB "database" is just a named namespace inside a cluster, created on first\n' +
+                '    write. Any number of database components may point at the SAME cluster (same cloud connection,\n' +
+                '    same resource/cluster name) as long as each uses a DIFFERENT dbName. Needing a new database on a\n' +
+                '    cluster that already has one imported is the normal path, not a conflict — do not stop or ask\n' +
+                '    the user to provision a new cluster; just import again with a different dbName.\n' +
                 '    Step 1 — discover the cluster name:\n' +
                 '      ductape_cli("cloud resources list -f /tmp/atlas-list.json --json")\n' +
                 '      File: {"cloud": "<atlas-connection-tag>", "service": "atlas-cluster"}\n' +
                 '      Returns a list of clusters; note the "name" field (this is your resource identifier).\n' +
-                '    Step 2 — check if the database component already exists:\n' +
+                '    Step 2 — decide new database vs. repoint an existing one:\n' +
                 '      ductape_cli("resources databases list <product_tag> --json")\n' +
-                '      If a component already uses the same Atlas cluster, do NOT re-import — instead update it:\n' +
-                '        use ductape_cli resource update when supported; otherwise update it in Workbench\n' +
-                '      Add or change the dbName in the env\'s connection_url to switch databases on the same cluster.\n' +
-                '    Step 3 — import (only if no existing component uses this cluster):\n' +
+                '      Only skip importing when you want an EXISTING component (same product, env, and dbName) to\n' +
+                '      keep pointing at the same database — that is a repoint, not a new database, and should go\n' +
+                '      through ductape_cli resource update (or Workbench) instead of a fresh import.\n' +
+                '      Otherwise — including "same cluster, different database" — proceed to Step 3 with a new\n' +
+                '      component tag and a dbName distinct from every other component already on that cluster.\n' +
+                '    Step 3 — import (one entry per new database; reusing a cluster across components is expected):\n' +
                 '      Use import-persist-all with one entry per product env. Required fields per entry:\n' +
                 '        cloud (connection tag), service: "atlas-cluster", type: "databases",\n' +
                 '        product, component (new tag), env, resource (cluster name from Step 1),\n' +
-                '        dbName (the MongoDB database name to connect to — required for Atlas).\n' +
-                '      Example: [{"cloud":"atlas-tag","service":"atlas-cluster","type":"databases",\n' +
-                '        "product":"my-product","component":"core-db","env":"snd","resource":"Cluster0","dbName":"myapp_snd"},\n' +
+                '        dbName (the MongoDB database name to connect to — must be unique per cluster, not per workspace).\n' +
+                '      Example — a second database ("billing-db") added to the same cluster as an existing "core-db":\n' +
+                '      [{"cloud":"atlas-tag","service":"atlas-cluster","type":"databases",\n' +
+                '        "product":"my-product","component":"billing-db","env":"snd","resource":"Cluster0","dbName":"billing_snd"},\n' +
                 '        {"cloud":"atlas-tag","service":"atlas-cluster","type":"databases",\n' +
-                '        "product":"my-product","component":"core-db","env":"prd","resource":"Cluster0","dbName":"myapp_prd"}]\n' +
+                '        "product":"my-product","component":"billing-db","env":"prd","resource":"Cluster0","dbName":"billing_prd"}]\n' +
                 '  - Message broker / event broker import:\n' +
                 '    CLI accepts these aliases for the messageBrokers module: events, event, broker, brokers, message-brokers.\n' +
                 '    List existing brokers: ductape_cli("resources events list --json")\n' +

package/package.json

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