@awesomate/hosting-mcp 0.45.0 → 0.47.0

package/dist/index.js

@@ -39984,6 +39984,9 @@ function hubGet(config3, path) {
 function hubPost(config3, path, jsonBody = {}, opts = {}) {
   return hubRequest(config3, "POST", path, jsonBody, opts);
 }
+function hubPut(config3, path, jsonBody = {}) {
+  return hubRequest(config3, "PUT", path, jsonBody);
+}
 function hubPatch(config3, path, jsonBody = {}) {
   return hubRequest(config3, "PATCH", path, jsonBody);
 }
@@ -41190,6 +41193,9 @@ var TITLES = {
   awesomate_crm_write: "Write app data records",
   awesomate_crm_queries: "Save and run named data queries",
   awesomate_crm_recipes: "Save named write recipes",
+  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_email: "Draft an email to a contact list"
 };
 function annotate(name, kind) {
@@ -41878,23 +41884,13 @@ readTool(
   "Usage vs plan limits across every dimension (sites, custom domains, apps, database provisions today, workflow credits, AI-editor credits) plus a nudges[] array. Call BEFORE any create action; when a nudge has severity 'approaching' or 'exceeded', surface it to the user with the recommended plan \u2014 never execute an upgrade without preview + explicit confirmation (upgrade tools ship in a later release; for now deep-link to the hub billing page). pgProvisionsToday is a flat daily cap that resets within 24h \u2014 no plan raises it, so don't pitch an upgrade for it.",
   "/api/client-hosting/limits"
 );
-var KNOWLEDGE_NOT_INCLUDED = {
-  included: false,
-  onboardingMediaHours: 0,
-  onboardingPages: 0,
-  onboardingUrls: 0,
-  monthlyMediaHours: 0,
-  monthlyAnswers: 0,
-  maxStorageGb: 0,
-  agentModelTier: "sonnet"
-};
 var PLAN_LADDER_FALLBACK = {
-  note: "Live per-account limits come from awesomate_get_limits \u2014 this is the plan ladder reference (static fallback).",
+  note: "Live per-account limits come from awesomate_get_limits. This is the plan ladder reference (static fallback).",
   plans: [
-    { name: "Essentials", purchasable: false, monthlyPriceUsd: 75, maxSites: 1, maxCustomDomains: 1, maxApps: 0, cpanelAccess: true, shellAccess: false, appBuilder: false, knowledgeBase: KNOWLEDGE_NOT_INCLUDED },
-    { name: "Support Plus", purchasable: true, monthlyPriceUsd: 175, maxSites: 2, maxCustomDomains: 5, maxApps: 5, cpanelAccess: true, shellAccess: true, appBuilder: true, knowledgeBase: KNOWLEDGE_NOT_INCLUDED },
-    { name: "Pro", purchasable: true, monthlyPriceUsd: 375, maxSites: 10, maxCustomDomains: 20, maxApps: 20, cpanelAccess: true, shellAccess: true, appBuilder: true, knowledgeBase: { included: true, onboardingMediaHours: 10, onboardingPages: 2e3, onboardingUrls: 500, monthlyMediaHours: 5, monthlyAnswers: 1e3, maxStorageGb: 10, agentModelTier: "sonnet" } },
-    { name: "Embedded", purchasable: false, monthlyPriceUsd: null, maxSites: 100, maxCustomDomains: 100, maxApps: 100, cpanelAccess: true, shellAccess: true, appBuilder: true, knowledgeBase: { included: true, onboardingMediaHours: 50, onboardingPages: 1e4, onboardingUrls: 2500, monthlyMediaHours: 20, monthlyAnswers: 1e4, maxStorageGb: 50, agentModelTier: "opus" }, note: "Not generally available yet" }
+    { name: "Essentials", purchasable: false, monthlyPriceUsd: 75, maxSites: 1, maxCustomDomains: 1, maxApps: 0, cpanelAccess: true, shellAccess: false, appBuilder: false, knowledgeBase: { included: true, onboardingMediaHours: 0, onboardingPages: 50, onboardingUrls: 10, monthlyMediaHours: 0, monthlyAnswers: 50, maxStorageGb: 5, agentModelTier: "sonnet" } },
+    { name: "Support Plus", purchasable: true, monthlyPriceUsd: 175, maxSites: 2, maxCustomDomains: 5, maxApps: 5, cpanelAccess: true, shellAccess: true, appBuilder: true, knowledgeBase: { included: true, onboardingMediaHours: 5, onboardingPages: 1e3, onboardingUrls: 250, monthlyMediaHours: 2, monthlyAnswers: 500, maxStorageGb: 250, agentModelTier: "sonnet" } },
+    { name: "Pro", purchasable: true, monthlyPriceUsd: 375, maxSites: 10, maxCustomDomains: 20, maxApps: 20, cpanelAccess: true, shellAccess: true, appBuilder: true, knowledgeBase: { included: true, onboardingMediaHours: 10, onboardingPages: 2e3, onboardingUrls: 500, monthlyMediaHours: 5, monthlyAnswers: 1e3, maxStorageGb: 1024, agentModelTier: "sonnet" } },
+    { name: "Embedded", purchasable: false, monthlyPriceUsd: null, maxSites: 100, maxCustomDomains: 100, maxApps: 100, cpanelAccess: true, shellAccess: true, appBuilder: true, knowledgeBase: { included: true, onboardingMediaHours: 50, onboardingPages: 1e4, onboardingUrls: 2500, monthlyMediaHours: 20, monthlyAnswers: 1e4, maxStorageGb: 1024, agentModelTier: "opus" }, note: "Not generally available yet" }
   ],
   upgradePath: "Essentials \u2192 Support Plus \u2192 Pro \u2192 Embedded; upgrades at hub.awesomate.ai/billing (only Support Plus and Pro are purchasable)"
 };
@@ -42792,25 +42788,35 @@ server.registerTool(
   "awesomate_crm_kinds",
   {
     annotations: annotate("awesomate_crm_kinds", MUTATING),
-    description: "The kinds of app data in the client's own database (the tables an app keeps: jobs, memos, bookings, messages), created directly from here on Support Plus and above. action 'list': every kind with its attributes and links. 'define' {key, label?, label_plural?, attributes, links?}: a new kind; links: [{key, to, label?, required?}] where to is 'contact' or a kind already made, and each shows as <key>_id. 'add_attribute' {kind, attribute}. 'archive_attribute' {kind, key}: leaves the views, values kept. 'archive' {kind}: kept, restorable. No migration and no SQL: a kind is registry rows plus generated views. Business things whose values must be traced to a source (a property, an installed system) are 'tracked' kinds the owner accepts in the hub; they are refused here. Mark an attribute readable_by_ai only when the owner wants Claude and agents to see it, and never for anything sensitive. Confirm the design with the user before defining: a kind is part of their data, not scratch space.",
+    description: "The kinds of app data in the client's own database (the tables an app keeps: jobs, memos, bookings, messages), created directly from here on Support Plus and above. action 'list': every kind with its attributes and links. 'define' {key, label?, label_plural?, attributes, links?}: a new kind; links: [{key, to, label?, required?}] where to is 'contact' or a kind already made, and each shows as <key>_id. 'add_attribute' {kind, attribute}. 'archive_attribute' {kind, key}: leaves the views, values kept. 'archive' {kind}: kept, restorable. No migration and no SQL: a kind is registry rows plus generated views. Business things whose values must be traced to a source (a property, an installed system) are 'tracked' kinds the owner accepts in the hub; they are refused here. Mark an attribute readable_by_ai only when the owner wants Claude and agents to see it, and never for anything sensitive. 'set_access' {kind, access} (or access on define): who among the people signed in to the account's apps (awesomate_crm_apps) may read and change records of this kind, by their role: {read: {<role>: <rule>}, write: {<role>: <rule>}}. A rule is all, none, own (records they created), or linked:<link path ending at a contact> (linked:customer: jobs whose customer is them; linked:job.customer: memos on their jobs), joined with |. A role with no rule gets nothing; the default lets owner and staff do everything and members nothing. A write must leave the record inside the person's rule. Confirm the design with the user before defining: a kind is part of their data, not scratch space.",
     inputSchema: {
-      action: external_exports.enum(["list", "define", "add_attribute", "archive_attribute", "archive"]),
-      kind: external_exports.string().max(41).optional().describe("the kind to change (add_attribute, archive_attribute, archive)"),
+      action: external_exports.enum(["list", "define", "add_attribute", "archive_attribute", "archive", "set_access"]),
+      kind: external_exports.string().max(41).optional().describe("the kind to change (add_attribute, archive_attribute, archive, set_access)"),
       key: external_exports.string().max(41).optional().describe("define: the new kind; archive_attribute: the attribute"),
       label: external_exports.string().max(80).optional(),
       label_plural: external_exports.string().max(80).optional(),
       attributes: external_exports.array(crmAttribute).max(60).optional(),
       links: external_exports.array(external_exports.object({ key: external_exports.string().max(38), to: external_exports.string().max(41), label: external_exports.string().max(80).optional(), to_label: external_exports.string().max(80).optional(), required: external_exports.boolean().optional() })).max(20).optional(),
-      attribute: crmAttribute.optional().describe("add_attribute")
+      attribute: crmAttribute.optional().describe("add_attribute"),
+      access: external_exports.object({
+        read: external_exports.record(external_exports.string().max(200)).optional(),
+        write: external_exports.record(external_exports.string().max(200)).optional()
+      }).optional().describe("define / set_access: {read: {<role>: <rule>}, write: {<role>: <rule>}}")
     }
   },
-  async ({ action, kind, key, label, label_plural, attributes, links, attribute }) => {
+  async ({ action, kind, key, label, label_plural, attributes, links, attribute, access }) => {
     try {
       const cfg = requireConfig();
       if (action === "list") return textResult(await hubGet(cfg, "/api/my-crm/v1/kinds"));
-      if (action === "define") return textResult(await hubPost(cfg, "/api/my-crm/v1/kinds", { key, label, label_plural, attributes: attributes ?? [], links: links ?? [] }));
+      if (action === "define") {
+        return textResult(await hubPost(cfg, "/api/my-crm/v1/kinds", { key, label, label_plural, attributes: attributes ?? [], links: links ?? [], ...access ? { access } : {} }));
+      }
       if (!kind) return errorResult(new Error(`${action} needs the kind.`));
       const k = encodeURIComponent(kind);
+      if (action === "set_access") {
+        if (!access) return errorResult(new Error("set_access needs access: {read: {<role>: <rule>}, write: {<role>: <rule>}}."));
+        return textResult(await hubPut(cfg, `/api/my-crm/v1/kinds/${k}/access`, { access }));
+      }
       if (action === "add_attribute") return textResult(await hubPost(cfg, `/api/my-crm/v1/kinds/${k}/attributes`, { attribute }));
       if (action === "archive_attribute") {
         if (!key) return errorResult(new Error("archive_attribute needs key, the attribute."));
@@ -42855,6 +42861,102 @@ server.registerTool(
     }
   }
 );
+server.registerTool(
+  "awesomate_crm_apps",
+  {
+    annotations: annotate("awesomate_crm_apps", MUTATING),
+    description: "The account's own apps (a client portal, a members' app) whose users sign in by email link and then read and change only what each kind's access rules allow them (awesomate_crm_kinds set_access). Pro and above to create or change; reading is every plan. action 'list': each app with its publishable key, allowed origins, sign-up mode and default role. action 'create' {name, allowed_origins, sign_up?, default_role?}: name appears in the sign-in email; allowed_origins are the exact origins the app runs on (https://portal.example.com; http://localhost:5173 for development; capacitor://localhost for the mobile shell), with no path and no wildcard; sign_up 'invite' (default: only people added with awesomate_crm_app_users) or 'open' (anyone who uses the email link gets the default role). action 'update' {app_id, ...any of those, status?}: status 'disabled' signs everyone out of that app. The publishable key (pk_...) is not a secret: it goes in the app's browser code, with @awesomate/sdk. Never put the account's own token (amt_pat_...) in browser code. Confirm origins and sign-up mode with the user: open sign-up lets strangers in under the default role.",
+    inputSchema: {
+      action: external_exports.enum(["list", "create", "update"]),
+      app_id: external_exports.string().max(48).optional().describe("update: the app"),
+      name: external_exports.string().max(80).optional(),
+      allowed_origins: external_exports.array(external_exports.string().max(200)).max(10).optional(),
+      sign_up: external_exports.enum(["invite", "open"]).optional(),
+      default_role: external_exports.string().max(31).optional().describe("lower case; the role open sign-up gives"),
+      status: external_exports.enum(["active", "disabled"]).optional().describe("update only")
+    }
+  },
+  async ({ action, app_id, name, allowed_origins, sign_up, default_role, status }) => {
+    try {
+      const cfg = requireConfig();
+      if (action === "list") return textResult(await hubGet(cfg, "/api/my-crm/v1/apps"));
+      const fields = Object.fromEntries(Object.entries({ name, allowed_origins, sign_up, default_role }).filter(([, v]) => v !== void 0));
+      if (action === "create") return textResult(await hubPost(cfg, "/api/my-crm/v1/apps", fields));
+      if (!app_id) return errorResult(new Error("update needs app_id, from list."));
+      return textResult(await hubPatch(cfg, `/api/my-crm/v1/apps/${encodeURIComponent(app_id)}`, { ...fields, ...status ? { status } : {} }));
+    } catch (err) {
+      return errorResult(err);
+    }
+  }
+);
+server.registerTool(
+  "awesomate_crm_app_users",
+  {
+    annotations: annotate("awesomate_crm_app_users", MUTATING),
+    description: "The people who sign in to the account's apps (awesomate_crm_apps): their email, role, the contact they are (matched on email when they are added or first sign in), last sign-in and whether they are disabled. Pro and above to change; reading is every plan. action 'list'. action 'add' {email, role?}: lets them sign in to an invite-only app (no email is sent; they ask for a link in the app). action 'update' {id, role?, disabled?, contact_id?}: a role change applies to their very next request; disabled: true stops their next request and signs them out of every app at once; contact_id links them to a contact (null unlinks), which is what linked: rules follow. These are people's email addresses: show them only when the user asks, and never paste them anywhere else.",
+    inputSchema: {
+      action: external_exports.enum(["list", "add", "update"]),
+      id: external_exports.string().max(64).optional().describe("update: the person's id from list"),
+      email: external_exports.string().max(254).optional().describe("add"),
+      role: external_exports.string().max(31).optional().describe("lower case: owner, staff, member, or one of your own"),
+      disabled: external_exports.boolean().optional(),
+      contact_id: external_exports.string().max(64).nullable().optional()
+    }
+  },
+  async ({ action, id, email: email2, role, disabled, contact_id }) => {
+    try {
+      const cfg = requireConfig();
+      if (action === "list") return textResult(await hubGet(cfg, "/api/my-crm/v1/app-users"));
+      if (action === "add") {
+        if (!email2) return errorResult(new Error("add needs the email."));
+        return textResult(await hubPost(cfg, "/api/my-crm/v1/app-users", { email: email2, ...role ? { role } : {} }));
+      }
+      if (!id) return errorResult(new Error("update needs id, from list."));
+      const patch = Object.fromEntries(Object.entries({ role, disabled, contact_id }).filter(([, v]) => v !== void 0));
+      return textResult(await hubPatch(cfg, `/api/my-crm/v1/app-users/${encodeURIComponent(id)}`, patch));
+    } catch (err) {
+      return errorResult(err);
+    }
+  }
+);
+server.registerTool(
+  "awesomate_crm_assistant",
+  {
+    annotations: annotate("awesomate_crm_assistant", MUTATING),
+    description: "An AI participant in an app's conversations (a portal's per-job messages): when a signed-in customer writes, it answers from what that customer may see plus the account's own Knowledge Base, or drafts an answer for staff. Each conversation has a mode staff switch: off (people only, the default), draft (a suggested reply only staff see, sent by a person as themselves) or auto (it replies at once under its own name, marked as AI, when its gate allows; otherwise it drafts). It reads AS the customer, so the account's access rules bound it, and only attributes marked readable_by_ai reach it. The hub writes its replies, never the model. Pro and above to change; reading is every plan. action 'get' {app_id}. action 'set' {app_id, assistant}: assistant is {name, thread_link (the message kind's link to the job/booking), instructions?, knowledge_agent_id? (a PUBLISHED agent from awesomate_knowledge_agents, audience public), default_mode? (off), message_kind? (message), body_attribute? (body), settings_kind? (assistant_thread), drafts_kind? (assistant_draft), staff_roles? ([owner, staff]), daily_cap? (200), enabled?}. The tenant must already hold: the message kind with the body attribute marked readable_by_ai, a yes/no from_assistant attribute and the thread link; a settings kind {mode: choice off|draft|auto, needs_person?: yes_no} and a drafts kind {body, why?}, both linked to the same thread kind and readable by staff only (set_access). Saving an enabled assistant is refused with every problem listed; fix them with awesomate_crm_kinds and save again. action 'runs' {app_id, limit?}: what it decided per customer message (send, draft, handoff, skip, error) and why, by reference only. Confirm the name, the default mode and the knowledge agent with the user before 'set': switching it on lets an AI reply to their customers.",
+    inputSchema: {
+      action: external_exports.enum(["get", "set", "runs"]),
+      app_id: external_exports.string().max(48).describe("the app, from awesomate_crm_apps list"),
+      assistant: external_exports.object({
+        name: external_exports.string().max(40),
+        thread_link: external_exports.string().max(41),
+        instructions: external_exports.string().max(4e3).optional(),
+        knowledge_agent_id: external_exports.string().max(64).nullable().optional(),
+        default_mode: external_exports.enum(["off", "draft", "auto"]).optional(),
+        message_kind: external_exports.string().max(41).optional(),
+        body_attribute: external_exports.string().max(41).optional(),
+        settings_kind: external_exports.string().max(41).optional(),
+        drafts_kind: external_exports.string().max(41).optional(),
+        staff_roles: external_exports.array(external_exports.string().max(31)).max(10).optional(),
+        daily_cap: external_exports.number().int().min(1).max(1e3).optional(),
+        enabled: external_exports.boolean().optional()
+      }).optional().describe("set: the whole config; fields left out take their defaults"),
+      limit: external_exports.number().int().min(1).max(200).optional().describe("runs: how many, newest first (default 50)")
+    }
+  },
+  async ({ action, app_id, assistant, limit }) => {
+    try {
+      const cfg = requireConfig();
+      const path = `/api/my-crm/v1/apps/${encodeURIComponent(app_id)}/assistant`;
+      if (action === "get") return textResult(await hubGet(cfg, path));
+      if (action === "runs") return textResult(await hubGet(cfg, `${path}/runs${limit ? `?limit=${limit}` : ""}`));
+      if (!assistant) return errorResult(new Error("set needs assistant: {name, thread_link, ...}."));
+      return textResult(await hubPut(cfg, path, { assistant }));
+    } 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.45.0",
+  "version": "0.47.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,21 @@
 {
   "versions": [
+    {
+      "version": "0.47.0",
+      "highlights": [
+        "Your app's conversations can have an AI in them (awesomate_crm_assistant). When a customer writes, it answers from their own records and your Knowledge Base, or drafts an answer for your team. Pro and above",
+        "Your team decides per conversation: off, draft (a suggested reply only staff see, sent by a person as themselves) or auto (it replies at once, marked as AI). New conversations start off unless you choose otherwise",
+        "It reads as the customer it is answering, so your access rules bound it, and it sees only the fields you marked readable by AI. When someone asks for a person, it hands the conversation over and flags it"
+      ]
+    },
+    {
+      "version": "0.46.0",
+      "highlights": [
+        "Your own apps can now sign people in. Claude can set up an app (awesomate_crm_apps): where it runs, whether anyone can sign up or only people you add, and the key that goes in the app. Each person gets an email link, no passwords. Pro and above",
+        "You decide who sees what, per kind of record: members see their own jobs and the memos on them, staff see everything (awesomate_crm_kinds, set_access). The rules are kept in your own database, so a mistake in an app can't show anyone more",
+        "Add, re-role or switch off the people who sign in (awesomate_crm_app_users). Switching someone off takes effect on their very next click and signs them out everywhere"
+      ]
+    },
     {
       "version": "0.45.0",
       "highlights": [

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

@@ -1,21 +1,27 @@
 # Quotas, allowances, and Ingestion Packs
 
 Live numbers ALWAYS come from `awesomate_knowledge_status` (`usage` vs
-`usage.included` + `usage.packs`) — this file explains the model.
+`usage.included` + `usage.packs`). This file explains the model.
 
 ## Plan allowances
 
-| | Pro | Embedded |
-|---|---|---|
-| Included | yes | yes |
-| Onboarding (first month, one-off) | 10 media-hours, 2,000 pages / 500 URLs | 50 media-hours, 10,000 pages / 2,500 URLs |
-| Monthly media ingest | 5 hours | 20 hours |
-| Monthly verified answers | 1,000 | 10,000 |
-| Storage | 10 GB | 50 GB |
-| Agent model tier | sonnet | opus-eligible |
+Every plan includes the Knowledge Base. The NUMBERS (pages, answers a month,
+storage, business data) are not written here on purpose: they change as we learn
+real usage. Read them from `awesomate_knowledge_status` (`usage.included`), or
+from `awesomate_get_plan_features` for another plan.
 
-Essentials and Support Plus don't include Knowledge Base — status returns
-`upgrade_required` with the upsell copy; relay it once, honestly.
+| | Essentials | Support Plus | Pro |
+|---|---|---|---|
+| What it is for | Trying it out: your FAQs and an agent that answers from them | Day-to-day use | Everything, at the highest usage |
+| FAQs | Yes | Yes | Yes |
+| Documents, spreadsheets, web pages, pasted text | A small allowance | More | The most |
+| Website chat widget, unanswered-questions inbox | No | Yes | Yes |
+| Audio and video, scanned documents and images | No | No | Yes |
+| Ingestion Packs (below) | No: the answer is an upgrade | Yes | Yes |
+
+FAQ entries don't use up the page allowance. When an Essentials client outgrows
+it, say so plainly and point to Support Plus or Pro at hub.awesomate.ai/billing;
+never offer a pack, since Essentials cannot buy one.
 
 ## Ingestion Packs (overage)
 
@@ -31,8 +37,18 @@ One pack = **1 credit ($100)**, the user picks the dimension at purchase:
 - Insufficient credits → 402 `insufficient_credits`: top up from Billing
   first. Never loop on it.
 
-## Answer overage
-
-Answers are soft-gated: warnings at 100% of allowance, throttling well past
-it — chat never silently debits credits. If a client consistently outgrows
-the allowance, that's an upgrade/pack conversation, not a workaround.
+## Answer limit
+
+Answers are a hard stop. The allowance is the plan's monthly answers plus
+every answer pack held. When it is used up, every answer route (widget, agent
+chat, n8n, `ask`) returns 429 `quota_exceeded` until the 1st of next month
+(UTC), and a visitor sees "This assistant has reached its limit for this
+month". Answers on the client's own OpenRouter key never count.
+
+- The owner is emailed at 80% and again when the limit is reached.
+- Nothing ever debits credits on its own. The way past the limit is an answer
+  pack (Support Plus and above, the pack flow above, applied straight away) or
+  an upgrade. Essentials cannot buy packs, so for them it's the upgrade.
+- If a 429 `quota_exceeded` comes back from `ask` or a test chat, say so
+  plainly and offer those two routes. Don't retry: nothing changes until the
+  month turns or the allowance rises.