@awesomate/hosting-mcp 0.55.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.55.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,20 @@
 {
   "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": [
+        "Knowledge: audio and video are Pro and above whether you upload them or link to them, and each month's media hours are the line where transcription stops",
+        "A one-off media-hours pack is for the month you buy it. For more every month, the owner can add 40 media hours a month for $100 on Knowledge, Usage",
+        "Claude no longer says a YouTube or other video link will be transcribed: for now a link is read as a web page, and the recording itself is transcribed when you upload the file"
+      ]
+    },
     {
       "version": "0.55.0",
       "highlights": [

package/skill/awesomate-knowledge/references/ingestion-sources.md

@@ -10,9 +10,9 @@ estimating BEFORE asking approval.
 |---|---|---|
 | Web page / blog post | `add {url}` | One page per URL; extraction skips pages under ~200 chars of real text |
 | Whole site / blog | `add {sitemap, since?}` | sitemap.xml; default cap 500 pages per job — a bigger sitemap FAILS the job loudly rather than truncating silently. `since` skips entries with older `<lastmod>` |
-| YouTube / hosted video, podcast audio | `add {url}` | Transcribed (Deepgram); language defaults to English |
+| YouTube / hosted video, podcast audio | `add {url}` | **Not transcribed today**: a link to a recording is read as a web page (title and description). Pro and above only; below Pro, or in a trial, it is refused (403 `media_ingest`). To transcribe a recording, upload the file |
 | PDF / book / document / markdown | hub upload page | Text layer used; scanned pages OCR'd automatically (`auto` mode, capped at 300 OCR pages per job — over that the job fails BEFORE any vision spend) |
-| Video/audio FILES | hub upload page (≤ 100 MB) | Bigger media: host it and add by URL |
+| Video/audio FILES | hub upload page (≤ 100 MB) | Transcribed (Deepgram, language defaults to English). Pro and above, within the month's media hours. A longer recording: split or compress it and upload each part |
 | Images | hub upload page | Vision-described, then indexed |
 | Facebook export | hub upload page | The platform's facebook-export lane |
 | FAQs | Markdown file via `awesomate_knowledge_upload` | One `##` per question, so each becomes its own citable section. **Never** a Q&A spreadsheet as it is: convert it to this file, so every answer stays word for word and citable. Full recipe: [faqs.md](faqs.md) |

package/skill/awesomate-knowledge/references/quotas-and-packs.md

@@ -33,8 +33,9 @@ Knowledge → Usage page. A full library on Support Plus and up answers 402
 `addon_required` with the add-on's details when the owner can buy it, or 402
 `storage_full` with a sentence when they can't (in a trial, at the cap, or
 not the owner). Relay either one as it is; never buy anything.
-An answers pack counts only for the calendar month (UTC) it is bought in, so
-buying one late in the month buys less; say so before they confirm.
+An answers pack and a media-hours pack count only for the calendar month (UTC)
+they are bought in, so buying one late in the month buys less; say so before
+they confirm. A media-hours pack is Pro and above (audio and video are).
 
 - An ingest that would exceed included+packs returns `pack_required`. The
   tool response purchases NOTHING and queues NOTHING.
@@ -45,6 +46,20 @@ buying one late in the month buys less; say so before they confirm.
 - Insufficient credits → 402 `insufficient_credits`: top up from Billing
   first. Never loop on it.
 
+## Media hours
+
+Audio and video are Pro and above. The month's media hours are where
+transcription stops: the plan's hours, plus the one-off onboarding hours in the
+workspace's first month, plus this month's media-hours packs, plus the monthly
+media-hours add-on. Past them, a new recording is refused (`media_hours_exceeded`)
+until the 1st of next month (UTC); a recording already transcribed once is never
+charged again. The owner is told at 80% and 100%.
+
+The ways past it: a media-hours pack (40 hours for the rest of this month,
+1 credit, via the pack flow above), the monthly media-hours add-on (40 more hours
+in every month it runs, $100 a month on the card, added by the owner on Knowledge
+→ Usage; don't buy it from here), or a bigger plan.
+
 ## Answer limit
 
 Answers are a hard stop. The allowance is the plan's monthly answers plus

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