@awesomate/hosting-mcp 0.56.0 → 0.58.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"
 };
@@ -42415,7 +42416,7 @@ server.registerTool(
       removeCollectionIds: external_exports.array(external_exports.string().max(64)).max(16).optional().describe("move: remove from these collections"),
       sourceIds: external_exports.array(external_exports.string().max(300)).max(200).optional().describe("set_visibility/move: several sources at once"),
       confirm: external_exports.string().max(64).optional().describe("set_visibility to 'public' only: the account slug, after the user agreed in so many words"),
-      url: external_exports.string().url().optional().describe("add: one public page / blog post / YouTube link"),
+      url: external_exports.string().url().optional().describe("add: one public page or blog post. A YouTube or other video link is not transcribed: on Pro it is read as a page (title and description), below Pro it is refused. To transcribe a recording, upload the file"),
       sitemap: external_exports.string().url().optional().describe("add: sitemap.xml URL \u2014 ingests every listed page"),
       since: external_exports.string().optional().describe("add+sitemap only: skip entries with lastmod older than this ISO date"),
       sourceId: external_exports.string().optional().describe("remove only"),
@@ -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"),
@@ -43091,21 +43123,26 @@ server.registerTool(
   "awesomate_crm_recipes",
   {
     annotations: annotate("awesomate_crm_recipes", MUTATING),
-    description: `Write recipes: an app's own named writes over its kinds, a few steps that always happen together (log a job and its first memo; close a job and archive its booking). Run one with awesomate_crm_write action 'call'. action 'list': the recipes with their params. action 'save' {key, label, description?, params?, steps}: Support Plus and above; saving a key again replaces it. steps (1 to 10) are {op: 'write_record', kind, data?, links?, id?, as?} or {op: 'archive_record', kind, id}, run in order inside one transaction. {"$param": "<name>"} takes a caller's value; {"$step": "<as>"} takes the id an earlier step wrote, so a memo can link to the job made one step before. An id (an update or an archive) must come from a required uuid param or an earlier step, never a literal. Every kind, attribute, link and reference is checked when it is saved and again when it runs. Contacts are not written by recipes. A recipe is data the hub interprets, never code: there is no SQL and no condition logic. Confirm the steps with the user before saving.`,
+    description: `Write recipes: an app's own named writes over its kinds, a few steps that always happen together (log a job and its first memo; close a job and archive its booking). Run one with awesomate_crm_write action 'call'. action 'list': the recipes with their params. action 'save' {key, label, description?, params?, steps}: Support Plus and above; saving a key again replaces it. steps (1 to 10) are {op: 'write_record', kind, data?, links?, id?, as?} or {op: 'archive_record', kind, id}, run in order inside one transaction. {"$param": "<name>"} takes a caller's value; {"$step": "<as>"} takes the id an earlier step wrote, so a memo can link to the job made one step before. An id (an update or an archive) must come from a required uuid param or an earlier step, never a literal. Every kind, attribute, link and reference is checked when it is saved and again when it runs. Contacts are not written by recipes. A recipe is data the hub interprets, never code: there is no SQL and no condition logic. Confirm the steps with the user before saving. action 'run_by' {key, roles}: Pro and above. Lets the people who sign in to the account's apps, in those roles, run this recipe themselves with @awesomate/sdk app.call(key, args): something their write rule would not let them do by hand, such as accept their own quote ({op: 'write_record', kind: 'job', id: {$param: 'job'}, data: {status: 'accepted'}}). The database lets them do exactly the recipe's steps: only $param and $step positions take their values, every other value is fixed, and an existing record must be one they can already read. roles [] closes it again; archiving a recipe closes it too. Editing a recipe that customers can run changes what they can do: say so and confirm with the user before saving it.`,
     inputSchema: {
-      action: external_exports.enum(["list", "save", "archive"]),
-      key: external_exports.string().max(61).optional().describe("save/archive: lower_case name, not write_record or archive_record"),
+      action: external_exports.enum(["list", "save", "archive", "run_by"]),
+      key: external_exports.string().max(61).optional().describe("save/archive/run_by: lower_case name, not write_record or archive_record"),
+      roles: external_exports.array(external_exports.string().max(31)).max(10).optional().describe("run_by: the app roles (from awesomate_crm_app_users) that may run it; [] for the account only"),
       label: external_exports.string().max(120).optional(),
       description: external_exports.string().max(1e3).optional(),
       params: external_exports.array(crmParam).max(20).optional(),
       steps: external_exports.array(external_exports.record(external_exports.unknown())).min(1).max(10).optional()
     }
   },
-  async ({ action, key, label, description, params, steps }) => {
+  async ({ action, key, label, description, params, steps, roles }) => {
     try {
       const cfg = requireConfig();
       if (action === "list") return textResult(await hubGet(cfg, "/api/my-crm/v1/recipes"));
       if (!key) return errorResult(new Error(`${action} needs the key.`));
+      if (action === "run_by") {
+        if (!roles) return errorResult(new Error("run_by needs roles: a list of app roles, or [] to close it."));
+        return textResult(await hubPut(cfg, `/api/my-crm/v1/recipes/${encodeURIComponent(key)}/run-by`, { roles }));
+      }
       if (action === "save") return textResult(await hubPost(cfg, "/api/my-crm/v1/recipes", { key, label, description, params: params ?? [], steps: steps ?? [] }));
       return textResult(await hubDelete(cfg, `/api/my-crm/v1/recipes/${encodeURIComponent(key)}`));
     } catch (err) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.56.0",
+  "version": "0.58.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,19 @@
 {
   "versions": [
+    {
+      "version": "0.58.0",
+      "highlights": [
+        "Customers can do one exact thing their access would not let them do by hand, such as accept their own quote: Claude saves it as a recipe and, on your say-so, opens it to a role (awesomate_crm_recipes action 'run_by'). Pro and above",
+        "Your app runs it with @awesomate/sdk app.call(). The database lets them change only what the recipe says, and only on records they can already see; archiving the recipe closes it again"
+      ]
+    },
+    {
+      "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