@awesomate/hosting-mcp 0.57.0 → 0.59.0

package/dist/index.js

@@ -41286,7 +41286,7 @@ server.registerTool(
   "awesomate_n8n_deploy",
   {
     annotations: annotate("awesomate_n8n_deploy", DESTRUCTIVE),
-    description: "Workflow lifecycle writes on the client's n8n, all consent-gated and audited server-side. Actions: 'validate' (structural + n8n-mcp check of workflowJson \u2014 ALWAYS validate before create_draft), 'create_draft' (creates an INACTIVE '[CLI] ' workflow tagged awm:client-cli; returns its webhook URLs), 'activate'/'deactivate' (activation strips the [CLI] prefix; production webhooks respond only while active; agency-managed workflows are refused), 'promote' (swaps a TESTED draft into the live workflow IN PLACE \u2014 live id + webhookIds preserved so external callers keep working; pass workflowId=the LIVE id and draftId=the tested draft; the draft is archived '[promoted <date>]'; response includes operationId for rollback), 'rollback' (restore a promote's pre-swap state \u2014 pass operationId), 'update_draft' (replace an INACTIVE self-built draft's full JSON in place \u2014 pass workflowId + workflowJson; live workflows are refused, use the promote path), 'delete_draft' (inactive self-built drafts only). Get explicit user approval before activate, promote, rollback, and delete_draft. 429 quota_exceeded = daily plan limit; 403 consent_required \u2192 send user to settingsUrl; 409 n8n_credential_invalid = the user's OWN n8n rejected the stored API key (NOT a hub outage \u2014 reads and validate keep working because they never touch their instance): tell them to create a new API key in their n8n under Settings \u2192 n8n API, paste it into their Awesomate account at hub.awesomate.ai/n8n/settings, then retry.",
+    description: "Workflow lifecycle writes on the client's n8n, all consent-gated and audited server-side. Actions: 'validate' (structural + n8n-mcp check of workflowJson; ALWAYS validate before create_draft), 'create_draft' (creates an INACTIVE '[CLI] ' workflow tagged awm:client-cli; returns its webhook URLs), 'activate'/'deactivate' (activation strips the [CLI] prefix; production webhooks respond only while active; one Awesomate built may be switched on or off, and the reply says built_by_us so you can tell the client what it does first, but every other write to it is refused with agency_managed; switching on a workflow installed from the library with an empty or missing credential answers 409 setup_incomplete with the list, so walk the client through filling it first), 'promote' (swaps a TESTED draft into the live workflow IN PLACE: live id + webhookIds preserved so external callers keep working; pass workflowId=the LIVE id and draftId=the tested draft; the draft is archived '[promoted <date>]'; response includes operationId for rollback), 'rollback' (restore a promote's pre-swap state; pass operationId), 'update_draft' (replace an INACTIVE self-built draft's full JSON in place; pass workflowId + workflowJson; live workflows are refused, use the promote path), 'delete_draft' (inactive self-built drafts only). Get explicit user approval before activate, promote, rollback, and delete_draft. 429 quota_exceeded = daily plan limit; 403 consent_required \u2192 send user to settingsUrl; 409 n8n_credential_invalid = the user's OWN n8n rejected the stored API key (NOT a hub outage: reads and validate keep working because they never touch their instance): tell them to create a new API key in their n8n under Settings \u2192 n8n API, paste it into their Awesomate account at hub.awesomate.ai/n8n/settings, then retry.",
     inputSchema: {
       action: external_exports.enum(["validate", "create_draft", "update_draft", "activate", "deactivate", "promote", "rollback", "delete_draft"]),
       workflowJson: external_exports.record(external_exports.unknown()).optional().describe("For validate: the full workflow JSON. For create_draft: must contain name, nodes, connections (settings optional)."),
@@ -41413,7 +41413,7 @@ server.registerTool(
   "awesomate_n8n_library",
   {
     annotations: annotate("awesomate_n8n_library", MUTATING),
-    description: "The Awesomate template library for THIS account: ready-made n8n automations and AI agents that Awesomate curates, including bundles linked to the account's referrer (e.g. Business Blueprint members see Dale Beaumont's bundles). Actions: 'list' (every bundle the account may see, each with installed, plan_ok and credentials_missing; every plan), 'detail' (slug: the templates in the bundle, what each does, the credential types it needs and whether the account already has each; every plan), 'install_plan' (slug: runs the pre-install checks WITHOUT writing and returns ready | paused | blocked; paused carries a help card per missing credential with where to get it, the exact page on their n8n to create it and our help article; Support Plus+), 'install' (slug: installs; refused unless the plan is ready, or every missing OPTIONAL credential is named in proceed_without and every ambiguous one has a choice in credential_choices; Support Plus+), 'redeem' (token: installs what a redeem token unlocks; Support Plus+). Then: 'installs' (what is on the instance, grouped by bundle), 'activate' (slug; switches the bundle's workflows on behind the same credential gate the hub uses: a workflow with an empty or missing credential answers setup_incomplete with the exact list; pass active:false to switch off), 'test' (slug; runs each template's test recipe and returns passed | failed | untested with the execution id; real side effects DO run, warn the client), 'rollback' (slug; removes what YOUR most recent install of this bundle created, never anything reused). Workflows land INACTIVE on install; activate is a separate, confirmed step. A 403 whose missingScopes contains n8n:deploy means the plan is Essentials: show the catalog, say installing needs Support Plus, and stop. Never create a credential for the client; send them to create_url and re-run install_plan afterwards.",
+    description: "The Awesomate template library for THIS account: ready-made n8n automations and AI agents that Awesomate curates, including bundles linked to the account's referrer (e.g. Business Blueprint members see Dale Beaumont's bundles). Actions: 'list' (every bundle the account may see, each with installed, plan_ok and credentials_missing; every plan), 'detail' (slug: the templates in the bundle, what each does, the credential types it needs and whether the account already has each; every plan), 'install_plan' (slug: runs the pre-install checks WITHOUT writing and returns ready | paused | blocked; paused carries a help card per missing credential with where to get it, the exact page on their n8n to create it and our help article; Support Plus+), 'install' (slug: installs; refused unless the plan is ready, or every missing OPTIONAL credential is named in proceed_without and every ambiguous one has a choice in credential_choices; Support Plus+), 'redeem' (token: installs what a redeem token unlocks; Support Plus+). Then: 'installs' (what is on the instance, grouped by bundle), 'activate' (slug; switches the bundle's workflows on behind the same credential gate the hub uses: a workflow with an empty or missing credential answers setup_incomplete with the exact list; pass active:false to switch off; this includes workflows Awesomate installed, marked built_by_us), 'test' (slug; runs each template's test recipe and returns passed | failed | untested with the execution id; real side effects DO run, warn the client), 'rollback' (slug; removes what YOUR most recent install of this bundle created, never anything reused). Workflows land INACTIVE on install; activate is a separate, confirmed step. A 403 whose missingScopes contains n8n:deploy means the plan is Essentials: show the catalog, say installing needs Support Plus, and stop. Never create a credential for the client; send them to create_url and re-run install_plan afterwards.",
     inputSchema: {
       action: external_exports.enum(["list", "detail", "install_plan", "install", "redeem", "installs", "activate", "test", "rollback"]),
       slug: external_exports.string().optional().describe("Bundle slug from list (detail, install_plan, install)"),
@@ -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.59.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,18 @@
 {
   "versions": [
+    {
+      "version": "0.59.0",
+      "highlights": [
+        "Claude can switch an automation Awesomate built for you off and on again when you ask, and says what it does first. Changing, deleting or rolling one back still goes through our support team"
+      ]
+    },
+    {
+      "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": [

package/skill/awesomate-n8n/SKILL.md

@@ -256,7 +256,8 @@ terms with the exact fix. Trust `errorSummary` only on `confident: true`
 (§0a). While you're there, check whether the workflow has an error plan at
 all — [error-handling.md](references/error-handling.md). Self-built workflows: fix via update_draft or the
 upgrade loop. Agency-managed (`agency_managed` error): read and explain
-freely; changes go through Awesomate support.
+freely, and switch it off or on if the user asks (say what it does first);
+any other change goes through Awesomate support.
 
 ## 6. "What could I automate?"
 

package/skill/awesomate-n8n/references/troubleshooting.md

@@ -87,10 +87,12 @@ rebuilt (a rebuilt instance shows 0 workflows and invalidates every old key).
 
 ## When to STOP and hand off
 
-- **`agency_managed` error** — the workflow is managed by Awesomate. Reads
+- **`agency_managed` error**: the workflow is managed by Awesomate. Reads
   are fine: list it, read executions, run `debug`, and explain the failure to
-  the user freely. Do NOT attempt any change (`deploy`, `test`, datatable
-  writes) — changes to agency-managed workflows go through Awesomate support.
+  the user freely. Switching it off or on is allowed when the user asks (the
+  reply carries `built_by_us`; tell them what stops while it's off). Do NOT
+  attempt any other change (`update_draft`, `promote`, `rollback`, `test`,
+  datatable writes): those go through Awesomate support.
   Summarize your diagnosis so the user can paste it into their ticket.
 - `403 consent_required` the user declines to enable — diagnose from the
   execution summary only; say plainly what deeper access would show.

package/skill/awesomate-n8n/references/upgrade-loop.md

@@ -23,7 +23,7 @@ workflow, a draft mid-iteration, or a workflow the user built in the n8n UI.
 | Iterating on an INACTIVE draft (not yet promoted/activated) | `update_draft` in place — no new workflow ids |
 | Changing a LIVE self-built workflow | Duplicate → draft loop → promote (steps below) |
 | Changing a workflow built in the n8n UI (no `awm:client-cli` tag) | Duplicate into a CLI draft; coordinated URL cutover |
-| Agency-managed workflow (`agency_managed` 403) | Read/explain only; changes go through Awesomate support |
+| Agency-managed workflow (`agency_managed` 403) | Read/explain; may be switched off or on when the user asks; other changes go through Awesomate support |
 
 ## Iterating on a draft: `update_draft`
 
@@ -94,5 +94,5 @@ Promote refuses these. Instead:
 |---|---|---|
 | 409 `workflow_active` | `update_draft` on a live workflow | Promote path, never deactivate-to-edit |
 | 403 `not_self_built` | No `awm:client-cli` tag | UI-built duplication path |
-| 403 `agency_managed` | Awesomate-deployed workflow | Explain only; route to support |
+| 403 `agency_managed` | Awesomate-deployed workflow | Explain; offer to switch it off or on if that is what they want; route changes to support |
 | 429 `quota_exceeded` | Daily plan cap | Tell the user; never retry-loop |