@ductape/mcp 0.1.4 → 0.1.5

package/dist/index.js

@@ -31,20 +31,39 @@ There are THREE categories of operations. Use the right tool for each:
        These require an access key and CANNOT be done via ductape_execute (publishable key only).
        → Use ductape_cli instead. Examples:
            ductape_cli("products list")
-           ductape_cli("product create --name \\"My Product\\" --tag my-product")
-           ductape_cli("environments list my-product")
+           ductape_cli("products create --name \\"My Product\\" --tag my-product")
            ductape_cli("cloud connections list")
+           ductape_cli("link --product my-product --env dev")
        If the CLI is not installed, ductape_cli will return install instructions automatically.
+       NOTE: Environments and app actions are configured in the Workbench UI — there are no CLI commands for them.
+
+       DECLARATIVE SYNC  (apply sessions, notifications, events from code; run DB migrations)
+       → Also use ductape_cli. The project must be linked first (ductape init --link).
+           ductape_cli("apply")                        # sync all: sessions + notifications + events
+           ductape_cli("apply sessions")               # sessions only
+           ductape_cli("apply notifications")          # notifications only
+           ductape_cli("apply events")                 # event brokers only
+           ductape_cli("apply --dry-run")              # preview without changes
+           ductape_cli("db schema generate")           # diff schema.json → write migration files
+           ductape_cli("db schema generate --destructive")  # also generate drop operations
+           ductape_cli("db migrate")                   # apply pending migration files
+           ductape_cli("db migrate --dry-run")         # preview without applying
+           ductape_cli("db migrate --env prd")         # apply to a specific environment
+           ductape_cli("db migrate status")            # show applied vs pending migrations
+           ductape_cli("db migrate status --json")     # machine-readable status
+           ductape_cli("db migrate rollback")          # roll back last migration
+           ductape_cli("db migrate rollback -n 3")     # roll back last 3 migrations
 
   1. ASSET CREATION / UPDATE  (create, update, add, register… for ANY asset type)
        ALL creation and update operations require an access key and CANNOT go through ductape_execute.
        → Use ductape_cli for every create/update operation. Examples:
-           ductape_cli("app create --name \\"Email Service\\" --description \\"Transactional email\\"")
+           ductape_cli("apps create --name \\"Email Service\\" --description \\"Transactional email\\"")
            ductape_cli("apps list")
-           ductape_cli("actions list my-app-tag")
-       This applies to: products, apps, actions, auths, environments, databases, storage,
-       graphs, vectors, brokers, sessions, notifications, jobs, features, quotas, fallbacks,
-       healthchecks, caches, secrets, and webhooks.
+           ductape_cli("resources storage list")
+           ductape_cli("resources database create -f db-config.json")
+       This applies to: products, apps, and resources (databases, storage, caches, etc.),
+       cloud connections, and secrets. Environments, app actions, auths, features, quotas,
+       fallbacks, jobs, and healthchecks are configured in the Workbench UI.
 
   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.
@@ -788,27 +807,18 @@ function buildSnippet(language, payload, operationFamily, method) {
 }
 // ─── CLI helpers ─────────────────────────────────────────────────────────────
 const ADMIN_SUBCOMMANDS = [
-    'products', 'product',
-    'apps', 'app',
-    'workspaces', 'workspace',
-    'environments', 'environment',
+    'login', 'logout', 'whoami',
+    'profiles',
+    'workspaces',
+    'link', 'unlink', 'init',
+    'products', 'apps',
+    'resources',
     'cloud',
     'secrets',
-    'databases',
-    'storage',
-    'graphs',
-    'vectors',
-    'brokers',
-    'notifications',
-    'sessions',
-    'caches',
-    'jobs',
     'generate',
-    'resources',
-    'init',
-    'login',
-    'logout',
-    'whoami',
+    'apply',
+    'db',
+    'graph',
 ];
 function checkCli() {
     try {
@@ -842,10 +852,14 @@ function runCli(command) {
 }
 const cliInputSchema = z.object({
     command: z.string().describe('The ductape CLI command to run, without the leading "ductape" word. ' +
-        'Examples: "products list", "product create --name \\"My Product\\" --tag my-product", ' +
-        '"environments list my-product", "cloud connections list".\n\n' +
-        'Use this tool for ALL administrative operations: creating or updating products, apps, ' +
-        'environments, resources, cloud connections, and workspace configuration.\n\n' +
+        'Examples: "products list", "products create --name \\"My Product\\" --tag my-product", ' +
+        '"apps list", "apps create -f app.json", "resources storage list", ' +
+        '"cloud connections list", "link --product my-product --env dev".\n\n' +
+        'Use this tool for administrative operations: creating or updating products, apps, ' +
+        'resources (databases, storage, caches…), cloud connections, secrets, ' +
+        'and for apply/migrate workflows.\n\n' +
+        'Note: environments, app actions, features, quotas, fallbacks, and jobs are configured ' +
+        'in the Workbench UI — there are no CLI commands for them.\n\n' +
         'The CLI uses the user\'s local logged-in session (ductape login) — no key is required.'),
 });
 async function loadMcpSdk() {
@@ -1035,11 +1049,17 @@ async function main() {
             title: 'Ductape CLI',
             description: 'Run a Ductape CLI command for administrative operations.\n\n' +
                 'USE THIS TOOL for any operation that creates or modifies platform configuration:\n' +
-                '  - Creating or updating products, apps, environments\n' +
-                '  - Managing cloud connections and resources\n' +
+                '  - 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' +
+                '  - Managing cloud connections and cloud-linked resources\n' +
                 '  - Listing workspaces, products, secrets\n' +
-                '  - Any operation that would require an access key via the SDK\n\n' +
-                'DO NOT use ductape_execute for these — it uses a publishable key which only ' +
+                '  - Linking a project folder: "link --product <tag> --env <slug>"\n' +
+                '  - Syncing sessions/notifications/events: "apply" or "apply sessions" etc.\n' +
+                '  - Running database migrations: "db migrate", "db schema generate"\n\n' +
+                'NOTE: Environments, app actions, auths, features, quotas, fallbacks, and jobs are ' +
+                'configured in the Workbench UI — the CLI does not have commands for them.\n\n' +
+                'DO NOT use ductape_execute for admin operations — it uses a publishable key which only ' +
                 'covers runtime operations. Administrative operations will fail with "Authentication failed".\n\n' +
                 'The CLI uses the user\'s local logged-in session (ductape login). ' +
                 'If the CLI is not installed, this tool will return install instructions automatically.',

package/package.json

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

package/src/index.ts

@@ -42,20 +42,39 @@ There are THREE categories of operations. Use the right tool for each:
        These require an access key and CANNOT be done via ductape_execute (publishable key only).
        → Use ductape_cli instead. Examples:
            ductape_cli("products list")
-           ductape_cli("product create --name \\"My Product\\" --tag my-product")
-           ductape_cli("environments list my-product")
+           ductape_cli("products create --name \\"My Product\\" --tag my-product")
            ductape_cli("cloud connections list")
+           ductape_cli("link --product my-product --env dev")
        If the CLI is not installed, ductape_cli will return install instructions automatically.
+       NOTE: Environments and app actions are configured in the Workbench UI — there are no CLI commands for them.
+
+       DECLARATIVE SYNC  (apply sessions, notifications, events from code; run DB migrations)
+       → Also use ductape_cli. The project must be linked first (ductape init --link).
+           ductape_cli("apply")                        # sync all: sessions + notifications + events
+           ductape_cli("apply sessions")               # sessions only
+           ductape_cli("apply notifications")          # notifications only
+           ductape_cli("apply events")                 # event brokers only
+           ductape_cli("apply --dry-run")              # preview without changes
+           ductape_cli("db schema generate")           # diff schema.json → write migration files
+           ductape_cli("db schema generate --destructive")  # also generate drop operations
+           ductape_cli("db migrate")                   # apply pending migration files
+           ductape_cli("db migrate --dry-run")         # preview without applying
+           ductape_cli("db migrate --env prd")         # apply to a specific environment
+           ductape_cli("db migrate status")            # show applied vs pending migrations
+           ductape_cli("db migrate status --json")     # machine-readable status
+           ductape_cli("db migrate rollback")          # roll back last migration
+           ductape_cli("db migrate rollback -n 3")     # roll back last 3 migrations
 
   1. ASSET CREATION / UPDATE  (create, update, add, register… for ANY asset type)
        ALL creation and update operations require an access key and CANNOT go through ductape_execute.
        → Use ductape_cli for every create/update operation. Examples:
-           ductape_cli("app create --name \\"Email Service\\" --description \\"Transactional email\\"")
+           ductape_cli("apps create --name \\"Email Service\\" --description \\"Transactional email\\"")
            ductape_cli("apps list")
-           ductape_cli("actions list my-app-tag")
-       This applies to: products, apps, actions, auths, environments, databases, storage,
-       graphs, vectors, brokers, sessions, notifications, jobs, features, quotas, fallbacks,
-       healthchecks, caches, secrets, and webhooks.
+           ductape_cli("resources storage list")
+           ductape_cli("resources database create -f db-config.json")
+       This applies to: products, apps, and resources (databases, storage, caches, etc.),
+       cloud connections, and secrets. Environments, app actions, auths, features, quotas,
+       fallbacks, jobs, and healthchecks are configured in the Workbench UI.
 
   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.
@@ -832,27 +851,18 @@ function buildSnippet(
 // ─── CLI helpers ─────────────────────────────────────────────────────────────
 
 const ADMIN_SUBCOMMANDS = [
-  'products', 'product',
-  'apps', 'app',
-  'workspaces', 'workspace',
-  'environments', 'environment',
+  'login', 'logout', 'whoami',
+  'profiles',
+  'workspaces',
+  'link', 'unlink', 'init',
+  'products', 'apps',
+  'resources',
   'cloud',
   'secrets',
-  'databases',
-  'storage',
-  'graphs',
-  'vectors',
-  'brokers',
-  'notifications',
-  'sessions',
-  'caches',
-  'jobs',
   'generate',
-  'resources',
-  'init',
-  'login',
-  'logout',
-  'whoami',
+  'apply',
+  'db',
+  'graph',
 ];
 
 function checkCli(): { available: boolean; version?: string } {
@@ -888,10 +898,14 @@ function runCli(command: string): { success: boolean; output: string } {
 const cliInputSchema = z.object({
   command: z.string().describe(
     'The ductape CLI command to run, without the leading "ductape" word. ' +
-    'Examples: "products list", "product create --name \\"My Product\\" --tag my-product", ' +
-    '"environments list my-product", "cloud connections list".\n\n' +
-    'Use this tool for ALL administrative operations: creating or updating products, apps, ' +
-    'environments, resources, cloud connections, and workspace configuration.\n\n' +
+    'Examples: "products list", "products create --name \\"My Product\\" --tag my-product", ' +
+    '"apps list", "apps create -f app.json", "resources storage list", ' +
+    '"cloud connections list", "link --product my-product --env dev".\n\n' +
+    'Use this tool for administrative operations: creating or updating products, apps, ' +
+    'resources (databases, storage, caches…), cloud connections, secrets, ' +
+    'and for apply/migrate workflows.\n\n' +
+    'Note: environments, app actions, features, quotas, fallbacks, and jobs are configured ' +
+    'in the Workbench UI — there are no CLI commands for them.\n\n' +
     'The CLI uses the user\'s local logged-in session (ductape login) — no key is required.',
   ),
 });
@@ -1124,11 +1138,17 @@ async function main() {
         description:
           'Run a Ductape CLI command for administrative operations.\n\n' +
           'USE THIS TOOL for any operation that creates or modifies platform configuration:\n' +
-          '  - Creating or updating products, apps, environments\n' +
-          '  - Managing cloud connections and resources\n' +
+          '  - 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' +
+          '  - Managing cloud connections and cloud-linked resources\n' +
           '  - Listing workspaces, products, secrets\n' +
-          '  - Any operation that would require an access key via the SDK\n\n' +
-          'DO NOT use ductape_execute for these — it uses a publishable key which only ' +
+          '  - Linking a project folder: "link --product <tag> --env <slug>"\n' +
+          '  - Syncing sessions/notifications/events: "apply" or "apply sessions" etc.\n' +
+          '  - Running database migrations: "db migrate", "db schema generate"\n\n' +
+          'NOTE: Environments, app actions, auths, features, quotas, fallbacks, and jobs are ' +
+          'configured in the Workbench UI — the CLI does not have commands for them.\n\n' +
+          'DO NOT use ductape_execute for admin operations — it uses a publishable key which only ' +
           'covers runtime operations. Administrative operations will fail with "Authentication failed".\n\n' +
           'The CLI uses the user\'s local logged-in session (ductape login). ' +
           'If the CLI is not installed, this tool will return install instructions automatically.',