@awesomate/hosting-mcp 0.57.0 → 0.58.0

package/dist/index.js

@@ -42416,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"),
@@ -43123,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.57.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,12 @@
 {
   "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": [