@ductape/mcp 0.1.55 → 0.1.57

package/dist/index.js

@@ -499,6 +499,8 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
   notifications.push.send   [{ product, env, notification, input: { ... }, session?, cache? }]  ← CALL ductape_generate_payload FIRST (operation_family="notification", method="push.send")
   notifications.sms.send    [{ product, env, notification, input: { ... }, session?, cache? }]  ← CALL ductape_generate_payload FIRST (operation_family="notification", method="sms.send")
   notifications.callback.send [{ product, env, notification, input: { ... }, session?, cache? }]  ← CALL ductape_generate_payload FIRST (operation_family="notification", method="callback.send")
+  notifications.slack.send   [{ product, env, notification, input: { text?, blocks?, channel? }, session?, cache? }]
+  notifications.discord.send [{ product, env, notification, input: { content?, embeds? }, session?, cache? }]
   notifications.dispatch   [{ product, env, notification, event, input, retries?, session?, cache?, schedule?: { cron?, every?, start_at? } }]  ← CALL ductape_generate_payload FIRST (operation_family="notification", method="dispatch") — requires redisUrl in ductape initialization
   notifications.getMessages [{ product_tag?, env?, notification_tag?, status?, type?, start_date?, end_date?, page?, limit? }]
 
@@ -998,7 +1000,7 @@ const ALLOWED_SNIPPET_METHODS = {
     graph: ['dispatch', 'find', 'insert', 'update', 'delete', 'query', 'execute'],
     vector: ['query', 'find', 'findSimilar', 'upsert', 'insert', 'delete', 'dispatch'],
     storage: ['dispatch', 'upload', 'download', 'remove', 'listFiles', 'getSignedUrl', 'stats'],
-    notification: ['dispatch', 'send', 'email.send', 'push.send', 'sms.send', 'callback.send'],
+    notification: ['dispatch', 'send', 'email.send', 'push.send', 'sms.send', 'callback.send', 'slack.send', 'discord.send'],
     messaging: ['dispatch', 'send', 'publish', 'produce', 'consume'],
     broker: ['dispatch', 'send', 'publish', 'produce', 'consume'],
     quota: ['run', 'dispatch', 'check', 'consume'],
@@ -1233,6 +1235,21 @@ function runCli(command) {
     catch (err) {
         const msg = (err.stderr || err.stdout || err.message || String(err)).trim();
         if (/\bHTTP 401\b|unauthori[sz]ed|invalid token|token expired/i.test(msg)) {
+            // Distinguish a genuinely expired login from a command-specific endpoint/auth bug.
+            // A valid workspace read proves the CLI session and selected workspace are authenticated.
+            if (checkLoginState() === 'ok') {
+                return {
+                    success: false,
+                    output: [
+                        'The Ductape CLI session and active workspace are authenticated, but this command endpoint returned HTTP 401.',
+                        'Do not ask the user to log in again and do not retry through ductape_execute.',
+                        'This indicates a CLI command routing or endpoint authorization problem.',
+                        '',
+                        'Update the Ductape CLI to the latest version and retry the same ductape_cli command.',
+                        `Original command: ductape ${command}`,
+                    ].join('\n'),
+                };
+            }
             authState = 'none';
             workspaceSynced = false;
             return {
@@ -2153,7 +2170,19 @@ DUCTAPE NOTIFICATIONS
 
 Notifications send messages across multiple channels: email, SMS, push, or HTTP callback.
 
-Create a notification through declarative apply or Workbench (administrative), using:
+ADMINISTRATION — CLI (never ductape_execute)
+  ductape_cli("resources notifications create -f notification.json")
+  ductape_cli("resources notifications get --tag <notification-tag> --json")
+  ductape_cli("resources notifications list --json")
+  ductape_cli("resources notifications update --tag <notification-tag> -f patch.json")
+  ductape_cli("resources notifications delete --tag <notification-tag>")
+  ductape_cli("notifications messages create -f message.json")
+  ductape_cli("notifications messages list --notification <notification-tag> --json")
+  ductape_cli("notifications messages get --tag <notification:message> --json")
+  ductape_cli("notifications messages update --tag <notification:message> -f patch.json")
+  Declarative alternative: ductape/notifications.json then ductape_cli("apply notifications").
+
+Notification definition:
   {
     tag: "welcome-email",
     name: "Welcome Email",
@@ -2174,6 +2203,8 @@ Send at runtime (one channel at a time):
   notifications.push.send     [{ product, env, notification, input: { device_tokens, title?, body?, data? } }]
   notifications.sms.send      [{ product, env, notification, input: { recipients, body? } }]
   notifications.callback.send [{ product, env, notification, input: { query?, headers?, params?, body? } }]
+  notifications.slack.send   [{ product, env, notification, input: { text?, blocks?, channel? } }]
+  notifications.discord.send [{ product, env, notification, input: { content?, embeds? } }]
 
 Multi-channel send (all channels in parallel):
   notifications.send [{ product, env, event: "notif_tag:message_tag", input: { ... } }]
@@ -2195,7 +2226,24 @@ Supported providers:
   Push:   firebase | expo
   Callback: any HTTP endpoint
 
-Channel configuration (envs per notification) is done in the Workbench UI, not via CLI.
+Each notification env may configure push_notifications, emails, sms, callbacks, slack, and discord.
+Email providers: smtp, sendgrid, mailgun, postmark, brevo.
+SMS providers: twilio, nexmo/vonage, plivo.
+
+FIREBASE THROUGH A GCP CLOUD CONNECTION
+  Complete and validate a GCP cloud connection with a service account authorized for Firebase
+  Cloud Messaging. Then configure the notification env without copying service-account JSON:
+    {
+      "slug": "snd",
+      "push_notifications": {
+        "type": "firebase",
+        "cloud": "gcp-connection-tag",
+        "authMode": "cloud_connection",
+        "databaseUrl": "https://<project>.firebaseio.com"
+      }
+    }
+  The SDK requests current GCP credentials from the cloud connection at send time. Never put the
+  service-account private key in the notification file. Expo does not use a GCP cloud connection.
 Notification tag and message tag are ALWAYS passed together as "notification_tag:message_tag".
 `.trim(),
     resilience: `

package/package.json

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

package/scripts/check-frontend-analytics-guidance.mjs

@@ -48,7 +48,11 @@ const safetyChecks = [
   ['execute blocks administrative mutations', /Administrative operation.*is blocked in ductape_execute/],
   ['CLI auth is remotely validated', /ductape workspaces list --json/],
   ['CLI 401 triggers login-required state', /authentication expired or was revoked \(HTTP 401\)[\s\S]*ductape login/],
+  ['CLI distinguishes endpoint 401 from expired login', /session and active workspace are authenticated[\s\S]*Do not ask the user to log in again/],
   ['CLI auth guidance does not request secrets', /Never ask the user to paste their password/],
+  ['notification CLI administration documented', /resources notifications create[\s\S]*notifications messages create/],
+  ['Firebase GCP cloud connection documented', /FIREBASE THROUGH A GCP CLOUD CONNECTION[\s\S]*authMode.*cloud_connection/],
+  ['Slack and Discord sends documented', /notifications\.slack\.send[\s\S]*notifications\.discord\.send/],
 ];
 
 for (const [name, pattern] of safetyChecks) {

package/src/index.ts

@@ -510,6 +510,8 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
   notifications.push.send   [{ product, env, notification, input: { ... }, session?, cache? }]  ← CALL ductape_generate_payload FIRST (operation_family="notification", method="push.send")
   notifications.sms.send    [{ product, env, notification, input: { ... }, session?, cache? }]  ← CALL ductape_generate_payload FIRST (operation_family="notification", method="sms.send")
   notifications.callback.send [{ product, env, notification, input: { ... }, session?, cache? }]  ← CALL ductape_generate_payload FIRST (operation_family="notification", method="callback.send")
+  notifications.slack.send   [{ product, env, notification, input: { text?, blocks?, channel? }, session?, cache? }]
+  notifications.discord.send [{ product, env, notification, input: { content?, embeds? }, session?, cache? }]
   notifications.dispatch   [{ product, env, notification, event, input, retries?, session?, cache?, schedule?: { cron?, every?, start_at? } }]  ← CALL ductape_generate_payload FIRST (operation_family="notification", method="dispatch") — requires redisUrl in ductape initialization
   notifications.getMessages [{ product_tag?, env?, notification_tag?, status?, type?, start_date?, end_date?, page?, limit? }]
 
@@ -1037,7 +1039,7 @@ const ALLOWED_SNIPPET_METHODS: Record<string, string[]> = {
   graph: ['dispatch', 'find', 'insert', 'update', 'delete', 'query', 'execute'],
   vector: ['query', 'find', 'findSimilar', 'upsert', 'insert', 'delete', 'dispatch'],
   storage: ['dispatch', 'upload', 'download', 'remove', 'listFiles', 'getSignedUrl', 'stats'],
-  notification: ['dispatch', 'send', 'email.send', 'push.send', 'sms.send', 'callback.send'],
+  notification: ['dispatch', 'send', 'email.send', 'push.send', 'sms.send', 'callback.send', 'slack.send', 'discord.send'],
   messaging: ['dispatch', 'send', 'publish', 'produce', 'consume'],
   broker: ['dispatch', 'send', 'publish', 'produce', 'consume'],
   quota: ['run', 'dispatch', 'check', 'consume'],
@@ -1293,6 +1295,21 @@ function runCli(command: string): { success: boolean; output: string } {
   } catch (err: any) {
     const msg = (err.stderr || err.stdout || err.message || String(err)).trim();
     if (/\bHTTP 401\b|unauthori[sz]ed|invalid token|token expired/i.test(msg)) {
+      // Distinguish a genuinely expired login from a command-specific endpoint/auth bug.
+      // A valid workspace read proves the CLI session and selected workspace are authenticated.
+      if (checkLoginState() === 'ok') {
+        return {
+          success: false,
+          output: [
+            'The Ductape CLI session and active workspace are authenticated, but this command endpoint returned HTTP 401.',
+            'Do not ask the user to log in again and do not retry through ductape_execute.',
+            'This indicates a CLI command routing or endpoint authorization problem.',
+            '',
+            'Update the Ductape CLI to the latest version and retry the same ductape_cli command.',
+            `Original command: ductape ${command}`,
+          ].join('\n'),
+        };
+      }
       authState = 'none';
       workspaceSynced = false;
       return {
@@ -2236,7 +2253,19 @@ DUCTAPE NOTIFICATIONS
 
 Notifications send messages across multiple channels: email, SMS, push, or HTTP callback.
 
-Create a notification through declarative apply or Workbench (administrative), using:
+ADMINISTRATION — CLI (never ductape_execute)
+  ductape_cli("resources notifications create -f notification.json")
+  ductape_cli("resources notifications get --tag <notification-tag> --json")
+  ductape_cli("resources notifications list --json")
+  ductape_cli("resources notifications update --tag <notification-tag> -f patch.json")
+  ductape_cli("resources notifications delete --tag <notification-tag>")
+  ductape_cli("notifications messages create -f message.json")
+  ductape_cli("notifications messages list --notification <notification-tag> --json")
+  ductape_cli("notifications messages get --tag <notification:message> --json")
+  ductape_cli("notifications messages update --tag <notification:message> -f patch.json")
+  Declarative alternative: ductape/notifications.json then ductape_cli("apply notifications").
+
+Notification definition:
   {
     tag: "welcome-email",
     name: "Welcome Email",
@@ -2257,6 +2286,8 @@ Send at runtime (one channel at a time):
   notifications.push.send     [{ product, env, notification, input: { device_tokens, title?, body?, data? } }]
   notifications.sms.send      [{ product, env, notification, input: { recipients, body? } }]
   notifications.callback.send [{ product, env, notification, input: { query?, headers?, params?, body? } }]
+  notifications.slack.send   [{ product, env, notification, input: { text?, blocks?, channel? } }]
+  notifications.discord.send [{ product, env, notification, input: { content?, embeds? } }]
 
 Multi-channel send (all channels in parallel):
   notifications.send [{ product, env, event: "notif_tag:message_tag", input: { ... } }]
@@ -2278,7 +2309,24 @@ Supported providers:
   Push:   firebase | expo
   Callback: any HTTP endpoint
 
-Channel configuration (envs per notification) is done in the Workbench UI, not via CLI.
+Each notification env may configure push_notifications, emails, sms, callbacks, slack, and discord.
+Email providers: smtp, sendgrid, mailgun, postmark, brevo.
+SMS providers: twilio, nexmo/vonage, plivo.
+
+FIREBASE THROUGH A GCP CLOUD CONNECTION
+  Complete and validate a GCP cloud connection with a service account authorized for Firebase
+  Cloud Messaging. Then configure the notification env without copying service-account JSON:
+    {
+      "slug": "snd",
+      "push_notifications": {
+        "type": "firebase",
+        "cloud": "gcp-connection-tag",
+        "authMode": "cloud_connection",
+        "databaseUrl": "https://<project>.firebaseio.com"
+      }
+    }
+  The SDK requests current GCP credentials from the cloud connection at send time. Never put the
+  service-account private key in the notification file. Expo does not use a GCP cloud connection.
 Notification tag and message tag are ALWAYS passed together as "notification_tag:message_tag".
 `.trim(),