@ductape/mcp 0.1.57 → 0.1.58

package/dist/index.js

@@ -323,6 +323,9 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
   IMPORTANT: ALL product.* methods require the access key and will return 403 with a publishable key.
   Use ductape_cli for ALL product operations — never ductape_execute:
     ductape_cli("products get --tag <tag> --json")           ← fetch product + full inventory
+    ductape_cli("products components list --tag <tag> --json") ← compact non-secret inventory
+    ductape_cli("products components get --tag <tag> --type notifications --json")
+    ductape_cli("products components get --tag <tag> --type events --json")
     ductape_cli("products create --name <name> --tag <tag>")
     ductape_cli("products environments list <tag> --json")
     ductape_cli("products environments get <tag> <slug> --json")
@@ -490,8 +493,8 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
   notifications.fetch    [product_tag, notif_tag]
   notifications.list     [product_tag]
   notifications.delete   [product_tag, notif_tag]
-  notifications.messages.create  [product_tag, data: { tag: string, notification: string, subject?: { template: string, data: object }, body?: { template: string, data: object } }]
-  notifications.messages.update  [product_tag, msg_tag, data: { subject?: { template: string, data: object }, body?: { template: string, data: object } }]
+  notifications.messages.create  [product_tag, data: { tag: string, name: string, description?: string, push_notification?: { title: string, body: string, data?: object }, email?: { subject: string, template: string }, callback?: object, sms?: string }]
+  notifications.messages.update  [product_tag, msg_tag, data: { name?: string, description?: string, push_notification?: { title: string, body: string, data?: object }, email?: { subject: string, template: string }, callback?: object, sms?: string }]
   notifications.messages.fetch   [product_tag, msg_tag]
   notifications.messages.list    [product_tag, notification_tag]
   notifications.send     [{ product, env, event, input: { ... } }]  ← CALL ductape_generate_payload FIRST (operation_family="notification", method="send", targets={notification})
@@ -1163,6 +1166,7 @@ const ADMIN_SUBCOMMANDS = [
     'link', 'unlink', 'init',
     'products', 'apps',
     'resources',
+    'notifications',
     'events',
     'cloud',
     'secrets',
@@ -2181,22 +2185,54 @@ ADMINISTRATION — CLI (never ductape_execute)
   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").
+  The file MUST be a top-level JSON array. Each item is a notification definition and may contain
+  a nested "messages" array. {"notifications":[],"messages":[]} is not a valid envelope.
 
 Notification definition:
   {
-    tag: "welcome-email",
+    tag: "welcome-email", // component tags cannot contain ":"
     name: "Welcome Email",
-    type: "email",   // optional hint; actual channels configured per env
+    description: "Transactional welcome messages",
+    envs: [{
+      slug: "prd",
+      emails: {
+        provider: "smtp",
+        smtp: {
+          host: "smtp.example.com",
+          port: "$Secret{smtp-port}",
+          sender_email: "hello@example.com",
+          auth: { user: "$Secret{smtp-user}", pass: "$Secret{smtp-password}" },
+          secure: true
+        }
+      }
+    }],
+    messages: []
   }
 
 Create a message template through declarative apply or Workbench:
   {
-    tag: "welcome-email:default",       // format: "notification_tag:message_tag"
-    notification: "welcome-email",
-    subject: { template: "Welcome, {{name}}!", data: { name: "" } },
-    body:    { template: "Hi {{name}}, thanks for signing up.", data: { name: "" } },
+    tag: "welcome-email:default", // message tags use component-tag:message-tag
+    name: "Default welcome",
+    description: "Sent after account creation",
+    push_notification: {
+      title: "Welcome, {{name}}!",
+      body: "Thanks for signing up.",
+      data: {}
+    },
+    email: {
+      subject: "Welcome, {{name}}!",
+      template: "Hi {{name}}, thanks for signing up."
+    }
   }
 
+TAG AND SMTP RULES
+  Component tag: "game-alerts-critical" (no colon).
+  Message tag: "game-alerts-critical:match-launch" (one colon separator).
+  Do not add "notification", "subject", or "body" at message root.
+  SMTP requires emails.smtp.sender_email.
+  emails.smtp.secure is a boolean and cannot be a $Secret{...} string.
+  Credential strings such as auth.user and auth.pass may use $Secret{...}.
+
 Send at runtime (one channel at a time):
   → CALL ductape_generate_payload FIRST (operation_family="notification", method="email.send")
   notifications.email.send    [{ product, env, notification, input: { recipients, subject?, template? } }]
@@ -2244,6 +2280,10 @@ FIREBASE THROUGH A GCP CLOUD CONNECTION
     }
   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.
+  The recommended cloud connection scope is "notifications". It expresses Ductape capability/UI
+  intent; creating a notification does not prove Google-side FCM permission. Runtime delivery
+  requires fcm.googleapis.com and roles/firebasecloudmessaging.admin, so validate the connection
+  and perform a delivery test.
 Notification tag and message tag are ALWAYS passed together as "notification_tag:message_tag".
 `.trim(),
     resilience: `
@@ -3753,8 +3793,10 @@ async function main() {
         const firstWord = args.command.trim().split(/\s+/)[0];
         const isAuthCommand = firstWord === 'login' || firstWord === 'logout';
         if (!isAuthCommand) {
-            // Check login status once per process (cached after first call)
-            if (authState === 'unknown') {
+            // Cache successful authentication, but re-check a missing/expired session on every call.
+            // The user may complete `ductape login` in another terminal while this MCP process remains
+            // alive; caching "none" would otherwise make the MCP blind to the newly written session.
+            if (authState === 'unknown' || authState === 'none') {
                 checkLoginState();
             }
             if (authState === 'none') {
@@ -4062,7 +4104,10 @@ async function main() {
                 '    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 first with ductape_cli("events topics create -f topic.json") — SQS requires explicit topic creation with queueUrls. For other providers, topics auto-register on first produce but should still be created explicitly before any consumer subscribes.\n' +
-                '  - Listing workspaces, products, secrets\n' +
+                '  - Listing workspaces, products, focused product components, secrets\n' +
+                '    Prefer "products components list --tag <tag> --json" for compact inventory; use\n' +
+                '    "products components get --tag <tag> --type notifications|events --json" for focused detail.\n' +
+                '  - Managing notification components and message templates through "resources notifications" and "notifications messages"\n' +
                 '  - 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' +

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ductape/mcp",
-  "version": "0.1.57",
+  "version": "0.1.58",
   "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

@@ -51,6 +51,11 @@ const safetyChecks = [
   ['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/],
+  ['notification command allowed by MCP', /ADMIN_SUBCOMMANDS[\s\S]*'notifications'/],
+  ['notification template uses SDK shape', /push_notification\?: \{ title: string, body: string[\s\S]*email\?: \{ subject: string, template: string/],
+  ['notification declarations require array shape', /file MUST be a top-level JSON array/],
+  ['external CLI login is re-read', /authState === 'unknown' \|\| authState === 'none'/],
+  ['compact product inventory documented', /products components list --tag <tag> --json/],
   ['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/],
 ];

package/src/index.ts

@@ -334,6 +334,9 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
   IMPORTANT: ALL product.* methods require the access key and will return 403 with a publishable key.
   Use ductape_cli for ALL product operations — never ductape_execute:
     ductape_cli("products get --tag <tag> --json")           ← fetch product + full inventory
+    ductape_cli("products components list --tag <tag> --json") ← compact non-secret inventory
+    ductape_cli("products components get --tag <tag> --type notifications --json")
+    ductape_cli("products components get --tag <tag> --type events --json")
     ductape_cli("products create --name <name> --tag <tag>")
     ductape_cli("products environments list <tag> --json")
     ductape_cli("products environments get <tag> <slug> --json")
@@ -501,8 +504,8 @@ ALL params are passed as a JSON array in positional order matching the SDK signa
   notifications.fetch    [product_tag, notif_tag]
   notifications.list     [product_tag]
   notifications.delete   [product_tag, notif_tag]
-  notifications.messages.create  [product_tag, data: { tag: string, notification: string, subject?: { template: string, data: object }, body?: { template: string, data: object } }]
-  notifications.messages.update  [product_tag, msg_tag, data: { subject?: { template: string, data: object }, body?: { template: string, data: object } }]
+  notifications.messages.create  [product_tag, data: { tag: string, name: string, description?: string, push_notification?: { title: string, body: string, data?: object }, email?: { subject: string, template: string }, callback?: object, sms?: string }]
+  notifications.messages.update  [product_tag, msg_tag, data: { name?: string, description?: string, push_notification?: { title: string, body: string, data?: object }, email?: { subject: string, template: string }, callback?: object, sms?: string }]
   notifications.messages.fetch   [product_tag, msg_tag]
   notifications.messages.list    [product_tag, notification_tag]
   notifications.send     [{ product, env, event, input: { ... } }]  ← CALL ductape_generate_payload FIRST (operation_family="notification", method="send", targets={notification})
@@ -1224,6 +1227,7 @@ const ADMIN_SUBCOMMANDS = [
   'link', 'unlink', 'init',
   'products', 'apps',
   'resources',
+  'notifications',
   'events',
   'cloud',
   'secrets',
@@ -2264,22 +2268,54 @@ ADMINISTRATION — CLI (never ductape_execute)
   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").
+  The file MUST be a top-level JSON array. Each item is a notification definition and may contain
+  a nested "messages" array. {"notifications":[],"messages":[]} is not a valid envelope.
 
 Notification definition:
   {
-    tag: "welcome-email",
+    tag: "welcome-email", // component tags cannot contain ":"
     name: "Welcome Email",
-    type: "email",   // optional hint; actual channels configured per env
+    description: "Transactional welcome messages",
+    envs: [{
+      slug: "prd",
+      emails: {
+        provider: "smtp",
+        smtp: {
+          host: "smtp.example.com",
+          port: "$Secret{smtp-port}",
+          sender_email: "hello@example.com",
+          auth: { user: "$Secret{smtp-user}", pass: "$Secret{smtp-password}" },
+          secure: true
+        }
+      }
+    }],
+    messages: []
   }
 
 Create a message template through declarative apply or Workbench:
   {
-    tag: "welcome-email:default",       // format: "notification_tag:message_tag"
-    notification: "welcome-email",
-    subject: { template: "Welcome, {{name}}!", data: { name: "" } },
-    body:    { template: "Hi {{name}}, thanks for signing up.", data: { name: "" } },
+    tag: "welcome-email:default", // message tags use component-tag:message-tag
+    name: "Default welcome",
+    description: "Sent after account creation",
+    push_notification: {
+      title: "Welcome, {{name}}!",
+      body: "Thanks for signing up.",
+      data: {}
+    },
+    email: {
+      subject: "Welcome, {{name}}!",
+      template: "Hi {{name}}, thanks for signing up."
+    }
   }
 
+TAG AND SMTP RULES
+  Component tag: "game-alerts-critical" (no colon).
+  Message tag: "game-alerts-critical:match-launch" (one colon separator).
+  Do not add "notification", "subject", or "body" at message root.
+  SMTP requires emails.smtp.sender_email.
+  emails.smtp.secure is a boolean and cannot be a $Secret{...} string.
+  Credential strings such as auth.user and auth.pass may use $Secret{...}.
+
 Send at runtime (one channel at a time):
   → CALL ductape_generate_payload FIRST (operation_family="notification", method="email.send")
   notifications.email.send    [{ product, env, notification, input: { recipients, subject?, template? } }]
@@ -2327,6 +2363,10 @@ FIREBASE THROUGH A GCP CLOUD CONNECTION
     }
   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.
+  The recommended cloud connection scope is "notifications". It expresses Ductape capability/UI
+  intent; creating a notification does not prove Google-side FCM permission. Runtime delivery
+  requires fcm.googleapis.com and roles/firebasecloudmessaging.admin, so validate the connection
+  and perform a delivery test.
 Notification tag and message tag are ALWAYS passed together as "notification_tag:message_tag".
 `.trim(),
 
@@ -3861,8 +3901,10 @@ async function main() {
     const isAuthCommand = firstWord === 'login' || firstWord === 'logout';
 
     if (!isAuthCommand) {
-      // Check login status once per process (cached after first call)
-      if (authState === 'unknown') {
+      // Cache successful authentication, but re-check a missing/expired session on every call.
+      // The user may complete `ductape login` in another terminal while this MCP process remains
+      // alive; caching "none" would otherwise make the MCP blind to the newly written session.
+      if (authState === 'unknown' || authState === 'none') {
         checkLoginState();
       }
       if (authState === 'none') {
@@ -4223,7 +4265,10 @@ async function main() {
           '    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 first with ductape_cli("events topics create -f topic.json") — SQS requires explicit topic creation with queueUrls. For other providers, topics auto-register on first produce but should still be created explicitly before any consumer subscribes.\n' +
-          '  - Listing workspaces, products, secrets\n' +
+          '  - Listing workspaces, products, focused product components, secrets\n' +
+          '    Prefer "products components list --tag <tag> --json" for compact inventory; use\n' +
+          '    "products components get --tag <tag> --type notifications|events --json" for focused detail.\n' +
+          '  - Managing notification components and message templates through "resources notifications" and "notifications messages"\n' +
           '  - 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' +