@awesomate/hosting-mcp 0.56.0 → 0.57.0

package/dist/index.js

@@ -41219,6 +41219,7 @@ var TITLES = {
   awesomate_crm_apps: "Set up sign-in for your own apps",
   awesomate_crm_app_users: "Manage the people who sign in to your apps",
   awesomate_crm_assistant: "Set up the AI in your app's conversations",
+  awesomate_crm_notifications: "Email people when someone replies in your app",
   awesomate_crm_hooks: "Send record changes to your n8n",
   awesomate_crm_email: "Draft an email to a contact list"
 };
@@ -43042,6 +43043,37 @@ server.registerTool(
     }
   }
 );
+server.registerTool(
+  "awesomate_crm_notifications",
+  {
+    annotations: annotate("awesomate_crm_notifications", MUTATING),
+    description: "Reply emails for an app's conversations (a portal's messages on a job): when someone writes, the people on the other side who are not in the app at that moment get one email, at most once an hour per conversation. A customer writing emails the team (app people in staff_roles); the team, the assistant, the account or an n8n workflow writing emails that conversation's customer. Never the author, never someone switched off. Sent from the app's name, with the message quoted and a link to the app's first https address. They are system emails, like a ticket reply or a receipt, so they carry no unsubscribe link: the owner switches them on or off per app. Off until switched on; switching on starts from now, so nothing said earlier is emailed. Email only for now. Pro and above to change; reading is every plan. action 'get' {app_id}: the setting, how many have been sent, and the last error. action 'set' {app_id, notifications}: notifications is {enabled, thread_link (the message kind's link to the conversation, e.g. 'job'), message_kind? ('message'), body_attribute? ('body'), title_attribute? ('title', on the conversation record, used in the subject), customer_link? ('customer', the conversation record's link to the customer contact), staff_roles? (['owner', 'staff'])}. Turning it on is refused with every problem listed while the kinds don't fit. Confirm with the owner before switching it on: it emails their customers.",
+    inputSchema: {
+      action: external_exports.enum(["get", "set"]),
+      app_id: external_exports.string().max(48).describe("the app, from awesomate_crm_apps list"),
+      notifications: external_exports.object({
+        enabled: external_exports.boolean(),
+        thread_link: external_exports.string().max(41),
+        message_kind: external_exports.string().max(41).optional(),
+        body_attribute: external_exports.string().max(41).optional(),
+        title_attribute: external_exports.string().max(41).optional(),
+        customer_link: external_exports.string().max(41).optional(),
+        staff_roles: external_exports.array(external_exports.string().max(31)).max(10).optional()
+      }).optional().describe("set: the whole setting; fields left out take their defaults")
+    }
+  },
+  async ({ action, app_id, notifications }) => {
+    try {
+      const cfg = requireConfig();
+      const path = `/api/my-crm/v1/apps/${encodeURIComponent(app_id)}/notifications`;
+      if (action === "get") return textResult(await hubGet(cfg, path));
+      if (!notifications) return errorResult(new Error("set needs notifications: {enabled, thread_link, ...}."));
+      return textResult(await hubPut(cfg, path, { notifications }));
+    } catch (err) {
+      return errorResult(err);
+    }
+  }
+);
 var crmParam = external_exports.object({
   name: external_exports.string().max(41).describe("lower_case"),
   type: external_exports.enum(["text", "number", "date", "datetime", "boolean", "uuid", "text_list", "number_list"]).optional().describe("default text"),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.56.0",
+  "version": "0.57.0",
   "description": "Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases",
   "license": "UNLICENSED",
   "type": "module",

package/skill/CHANGELOG.json

@@ -1,5 +1,12 @@
 {
   "versions": [
+    {
+      "version": "0.57.0",
+      "highlights": [
+        "Reply emails for your portal's conversations (awesomate_crm_notifications): when your team or Bree replies, the customer gets an email if they aren't in the portal, and when a customer writes, your team does. At most one an hour per conversation",
+        "Off until you switch them on, per app. They're system emails, like a ticket reply or a receipt, sent from your app's name with the message quoted and a link back"
+      ]
+    },
     {
       "version": "0.56.0",
       "highlights": [

package/skill/awesomate-portals/SKILL.md

@@ -135,6 +135,15 @@ lists the two staff-only kinds it needs (`assistant_thread`, `assistant_draft`)
 agent (awesomate-knowledge skill) so she can answer questions about the business. Confirm the
 name and the default mode with the owner: switching it on lets an AI reply to their customers.
 
+## 6b. Optional: reply emails
+
+`awesomate_crm_notifications {action:'set', app_id, notifications: {enabled: true, thread_link: 'job'}}`
+emails the other side of a conversation when someone writes there and they are not in the app:
+the customer when the team or the assistant replies, the team when a customer writes. At most one
+an hour per conversation, from the app's name, with the message quoted and a link back. They are
+system emails (no unsubscribe link); the owner switches them on or off per app. Ask the owner
+first: it emails their customers.
+
 ## 7. Optional: automation
 
 - **Server key** (`awesomate_crm_apps {action:'create_key'}`): for the app's own server or an n8n