@awesomate/hosting-mcp 0.87.0 → 0.88.6

package/dist/index.js

@@ -41747,6 +41747,7 @@ var TITLES = {
   awesomate_elementor_mcp_connect: "Connect Elementor MCP",
   awesomate_app_create: "Create app",
   awesomate_app_get: "Get app details",
+  awesomate_app_remove_failed: "Remove an app whose setup failed",
   awesomate_app_scaffold: "Get app scaffold guide",
   awesomate_app_deploy_info: "Get app deploy briefing",
   awesomate_app_update: "Link repo to app",
@@ -41766,14 +41767,10 @@ var TITLES = {
   awesomate_n8n_findings: "Get n8n findings",
   awesomate_n8n_kpis: "Get n8n KPIs",
   awesomate_n8n_node_docs: "Get n8n node docs",
-  awesomate_n8n_deploy: "Deploy n8n workflow",
   awesomate_n8n_agents: "Build n8n Agents",
   awesomate_n8n_library: "Install Awesomate templates",
   awesomate_book_session: "Book a session with Awesomate",
-  awesomate_n8n_test: "Test-fire n8n workflow",
-  awesomate_n8n_datatable_write: "Write to n8n data table",
   awesomate_n8n_attach_to_app: "Attach n8n to app",
-  awesomate_n8n_provision_pg: "Provision Postgres for n8n",
   awesomate_request_build: "Request a build from Awesomate",
   awesomate_knowledge_status: "Get Knowledge Base status",
   awesomate_knowledge_provision: "Enable Knowledge Base",
@@ -41866,65 +41863,9 @@ server.registerTool(
 );
 readTool(
   "awesomate_n8n_context",
-  "Call FIRST before any n8n work. Returns the client's n8n instance URL, plan, whether Claude Code n8n access is consented (if consented=false, send the user to settingsUrl and re-check after), builder capability (Support Plus+), instance variant, and build/test quota limits. When consented it also returns an instance fingerprint (community packages, workflow/credential/datatable counts). Companion tools once consented: awesomate_n8n_workflows (world picture), awesomate_n8n_inspect (nodes/datatables/possibilities/credentials/variables), awesomate_n8n_executions, awesomate_n8n_node_docs (live node schemas + community templates \u2014 every plan).",
+  "Call FIRST before any n8n work. Returns the client's n8n instance URL, plan, whether Claude Code n8n access is consented (if consented=false, send the user to settingsUrl and re-check after), template-install capability (Support Plus+) and instance variant. When consented it also returns an instance fingerprint (community packages, workflow/credential/datatable counts). Companion tools once consented: awesomate_n8n_workflows (world picture), awesomate_n8n_inspect (nodes/datatables/possibilities/credentials/variables), awesomate_n8n_executions, awesomate_n8n_node_docs (live node schemas + community templates \u2014 every plan).",
   "/api/my-n8n/machine/context"
 );
-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; 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)."),
-      workflowId: external_exports.string().optional().describe("Required for activate/deactivate/delete_draft; for promote this is the LIVE workflow id"),
-      draftId: external_exports.string().optional().describe("promote only: the tested draft to swap into the live workflow"),
-      operationId: external_exports.string().optional().describe("rollback only: the operationId returned by promote")
-    }
-  },
-  async ({ action, workflowJson, workflowId, draftId, operationId }) => {
-    try {
-      if (action === "validate") {
-        return textResult(await hubPost(requireConfig(), "/api/my-n8n/machine/workflows/validate", { workflow: workflowJson }));
-      }
-      if (action === "create_draft") {
-        return textResult(await hubPost(requireConfig(), "/api/my-n8n/machine/workflows/draft", workflowJson ?? {}));
-      }
-      if (action === "update_draft") {
-        if (!workflowId) return errorResult(new Error("workflowId is required for update_draft"));
-        if (!workflowJson) return errorResult(new Error("workflowJson (full: name, nodes, connections, settings?) is required for update_draft"));
-        return textResult(
-          await hubPatch(requireConfig(), `/api/my-n8n/machine/workflows/${encodeURIComponent(workflowId)}`, workflowJson)
-        );
-      }
-      if (action === "rollback") {
-        if (!operationId) return errorResult(new Error("operationId is required for rollback"));
-        return textResult(
-          await hubPost(requireConfig(), `/api/my-n8n/machine/operations/${encodeURIComponent(operationId)}/rollback`, {})
-        );
-      }
-      if (!workflowId) return errorResult(new Error(`workflowId is required for ${action}`));
-      if (action === "activate" || action === "deactivate") {
-        return textResult(
-          await hubPost(requireConfig(), `/api/my-n8n/machine/workflows/${encodeURIComponent(workflowId)}/activate`, {
-            active: action === "activate"
-          })
-        );
-      }
-      if (action === "promote") {
-        if (!draftId) return errorResult(new Error("draftId is required for promote"));
-        return textResult(
-          await hubPost(requireConfig(), `/api/my-n8n/machine/workflows/${encodeURIComponent(workflowId)}/promote`, { draftId })
-        );
-      }
-      return textResult(
-        await hubDelete(requireConfig(), `/api/my-n8n/machine/workflows/${encodeURIComponent(workflowId)}`)
-      );
-    } catch (err) {
-      return errorResult(err);
-    }
-  }
-);
 var N8N_AGENT_TOOLS = [
   "get_agent_builder_reference",
   "search_projects",
@@ -41967,7 +41908,7 @@ server.registerTool(
   "awesomate_n8n_agents",
   {
     annotations: annotate("awesomate_n8n_agents", DESTRUCTIVE),
-    description: "Build and manage n8n AGENTS (the Agents tab in n8n 2.41+; NOT the AI Agent node inside a workflow, and NOT the older Chat Hub agents) on the client's own n8n. Every action works on EVERY plan, Essentials included. The hub relays one call at a time to n8n's own instance MCP server, consent-gated, quota-limited and audited; the client's MCP key never reaches this machine. Actions: 'status' (is it set up? keyConfigured / reachable / ready / limits; call FIRST, and when not ready relay setup.steps to the user in plain words), 'describe' (n8n's own description + JSON input schema for every relayed tool, or just `tool`; read it before calling a tool whose arguments you have not seen this session, never guess argument shapes), 'call' (run one n8n agent tool: pass `tool` and its `arguments` exactly as its schema defines them), 'result' (call_id: collect a call that was still running). Before the first build in a session call tool 'get_agent_builder_reference' and follow its build sequence and JSON schema; it is n8n's own live guide and beats anything remembered. Flow: search_projects \u2192 discover_agent_assets (models, workflows, subagents) + list_credentials \u2192 create_agent {projectId, name, config} \u2192 mutate_agent {agentId, baseConfigHash, operation} (always the LATEST configHash; result.ok=false with code stale_config \u2192 get_agent and retry) \u2192 validate_agent \u2192 call_agent with one representative test message (real tools run, say so) \u2192 ask the user \u2192 publish_agent ONLY on their explicit yes. call_agent can take a couple of minutes: this tool waits for it. If it comes back pending with a call_id, or 409 agent_call_in_progress, NEVER resend the message; use 'result'. 504 mcp_timeout means it may have run anyway: check before retrying. Workflow tools must start with an Execute Workflow Trigger and be active (Support Plus+ can activate through awesomate_n8n_deploy; on Essentials the client switches it on in n8n). 403 agent_tool_blocked: the config tried to attach a workflow Awesomate manages, or the n8n node / an n8n API credential; use one of the client's own workflows instead. delete_agent only works on agents Claude created. 409 mcp_key_missing / mcp_disabled / mcp_key_rejected = setup problem on THEIR n8n, relay `hint` + `setup`. 429 quota_exceeded = daily plan limit. A response with ok:false is n8n's own answer: read error.code/message and fix the input, don't retry blindly.",
+    description: "Build and manage n8n AGENTS (the Agents tab in n8n 2.41+; NOT the AI Agent node inside a workflow, and NOT the older Chat Hub agents) on the client's own n8n. Every action works on EVERY plan, Essentials included. The hub relays one call at a time to n8n's own instance MCP server, consent-gated, quota-limited and audited; the client's MCP key never reaches this machine. Actions: 'status' (is it set up? keyConfigured / reachable / ready / limits; call FIRST, and when not ready relay setup.steps to the user in plain words), 'describe' (n8n's own description + JSON input schema for every relayed tool, or just `tool`; read it before calling a tool whose arguments you have not seen this session, never guess argument shapes), 'call' (run one n8n agent tool: pass `tool` and its `arguments` exactly as its schema defines them), 'result' (call_id: collect a call that was still running). Before the first build in a session call tool 'get_agent_builder_reference' and follow its build sequence and JSON schema; it is n8n's own live guide and beats anything remembered. Flow: search_projects \u2192 discover_agent_assets (models, workflows, subagents) + list_credentials \u2192 create_agent {projectId, name, config} \u2192 mutate_agent {agentId, baseConfigHash, operation} (always the LATEST configHash; result.ok=false with code stale_config \u2192 get_agent and retry) \u2192 validate_agent \u2192 call_agent with one representative test message (real tools run, say so) \u2192 ask the user \u2192 publish_agent ONLY on their explicit yes. call_agent can take a couple of minutes: this tool waits for it. If it comes back pending with a call_id, or 409 agent_call_in_progress, NEVER resend the message; use 'result'. 504 mcp_timeout means it may have run anyway: check before retrying. Workflow tools must start with an Execute Workflow Trigger and be active (the client switches it on in n8n, or through their own connection to the instance's MCP server). 403 agent_tool_blocked: the config tried to attach a workflow Awesomate manages, or the n8n node / an n8n API credential; use one of the client's own workflows instead. delete_agent only works on agents Claude created. 409 mcp_key_missing / mcp_disabled / mcp_key_rejected = setup problem on THEIR n8n, relay `hint` + `setup`. 429 quota_exceeded = daily plan limit. A response with ok:false is n8n's own answer: read error.code/message and fix the input, don't retry blindly.",
     inputSchema: {
       action: external_exports.enum(["status", "describe", "call", "result"]),
       tool: external_exports.enum(N8N_AGENT_TOOLS).optional().describe("call: the n8n agent tool to run (required). describe: limit to this tool (optional)"),
@@ -42072,26 +42013,6 @@ server.registerTool(
     }
   }
 );
-server.registerTool(
-  "awesomate_n8n_test",
-  {
-    annotations: annotate("awesomate_n8n_test", MUTATING),
-    description: "Fire a synthetic test payload at an ACTIVE self-built workflow's production webhook and get back the webhook response plus the executionId it caused (then poll GET /api/my-n8n/executions/:id for node-by-node results). Sends the X-Awesomate-Test header. Real side effects DO run (emails actually send) \u2014 warn the user, use their own address, prefix subjects with [TEST]. Only works on awm:client-cli-tagged workflows.",
-    inputSchema: {
-      workflowId: external_exports.string(),
-      payload: external_exports.record(external_exports.unknown()).optional().describe("JSON body to POST to the webhook (format-valid, obviously-fake values)")
-    }
-  },
-  async ({ workflowId, payload }) => {
-    try {
-      return textResult(
-        await hubPost(requireConfig(), `/api/my-n8n/machine/workflows/${encodeURIComponent(workflowId)}/test-fire`, { payload })
-      );
-    } catch (err) {
-      return errorResult(err);
-    }
-  }
-);
 server.registerTool(
   "awesomate_n8n_workflows",
   {
@@ -42128,11 +42049,31 @@ server.registerTool(
     }
   }
 );
+function withCredentialStaleWarning(data) {
+  if (!data || typeof data !== "object") return data;
+  const d = data;
+  if (d.stale !== true) return data;
+  const asOf = d.asOf ? new Date(d.asOf) : null;
+  const when = asOf && !Number.isNaN(asOf.getTime()) ? `as of ${asOf.toLocaleDateString("en-AU", { timeZone: "Australia/Sydney" })} ${asOf.toLocaleTimeString("en-AU", { timeZone: "Australia/Sydney", hour: "2-digit", minute: "2-digit" })} Sydney time (${d.asOf})` : "with no known refresh time";
+  const why = {
+    consent: `the refresh needs the "How your automations are running" privacy setting${d.settingsUrl ? ` (${d.settingsUrl})` : ""}`,
+    refresh_failed: "the hub could not refresh it from the n8n instance just now",
+    n8n_unreachable: "the hub could not reach the n8n instance's database to check it"
+  }[d.staleReason ?? "refresh_failed"];
+  const parts = [`This credential list may be out of date: it is ${when}, because ${why}.`];
+  const added = d.drift?.added ?? [];
+  const removed = d.drift?.removed ?? [];
+  if (added.length) parts.push(`n8n also has: ${added.map((c) => `${c.name} (${c.type}, ${c.credential_id})`).join(", ")}.`);
+  if (removed.length) parts.push(`No longer in n8n: ${removed.join(", ")}.`);
+  parts.push("Tell the user the list may be out of date before relying on it, and check the credential in n8n itself when it matters.");
+  const { stale: _s, ...rest } = d;
+  return { warning: parts.join(" "), stale: true, ...rest };
+}
 server.registerTool(
   "awesomate_n8n_inspect",
   {
     annotations: annotate("awesomate_n8n_inspect", READ_ONLY),
-    description: `Instance inventory reads, one tool: 'nodes' (distinct node types in use, counts, versions, community/AI flags), 'datatables' (tables + columns + row counts), 'datatable_rows' (pass datatableId; limit \u2264 100), 'possibilities' (facts for "what could I automate": connected services with live-usage cross-check, unused connections, top nodes, AI tools [null = unknown, not none], community packages, counts \u2014 YOU turn these into suggestions, grounded only in what's actually there), 'credentials' (names/types/inferred service \u2014 never secrets), 'variables' ($vars keys). All consent-gated server-side; 403 consent_required \u2192 settingsUrl.`,
+    description: `Instance inventory reads, one tool: 'nodes' (distinct node types in use, counts, versions, community/AI flags), 'datatables' (tables + columns + row counts), 'datatable_rows' (pass datatableId; limit \u2264 100), 'possibilities' (facts for "what could I automate": connected services with live-usage cross-check, unused connections, top nodes, AI tools [null = unknown, not none], community packages, counts \u2014 YOU turn these into suggestions, grounded only in what's actually there), 'credentials' (names/types/inferred service \u2014 never secrets; a leading 'warning' means the list may be out of date: say so to the user), 'variables' ($vars keys). All consent-gated server-side; 403 consent_required \u2192 settingsUrl.`,
     inputSchema: {
       what: external_exports.enum(["nodes", "datatables", "datatable_rows", "possibilities", "credentials", "variables"]),
       datatableId: external_exports.string().optional().describe("datatable_rows only"),
@@ -42154,7 +42095,8 @@ server.registerTool(
         credentials: "/api/my-n8n/machine/credentials",
         variables: "/api/my-n8n/machine/variables"
       }[what];
-      return textResult(await hubGet(cfg, path));
+      const data = await hubGet(cfg, path);
+      return textResult(what === "credentials" ? withCredentialStaleWarning(data) : data);
     } catch (err) {
       return errorResult(err);
     }
@@ -42207,41 +42149,6 @@ server.registerTool(
     }
   }
 );
-server.registerTool(
-  "awesomate_n8n_datatable_write",
-  {
-    annotations: annotate("awesomate_n8n_datatable_write", DESTRUCTIVE),
-    description: "Datatable writes (Support Plus+, consent-gated, audited). 'create' {name, columns:[{name,type?}], workflowId?} \u2014 ALWAYS pass workflowId when the table serves a specific workflow (datatables resolve PER PROJECT at runtime; workflowId threads that workflow's project; a projectWarning in the response means pass it). 'add_column' {tableId, name, type?} \u2014 needs the 'direct database writes' privacy toggle; names: letters/digits/underscores only. 'insert' {tableId, rows:[...]} (\u2264100), 'update' {tableId, filter, data}, 'delete_rows' {tableId, filter \u2014 REQUIRED, there is no delete-all}. Writes only work on tables created through Claude Code (403 not_self_created otherwise \u2014 agency tables are off limits). Get explicit user approval before delete_rows.",
-    inputSchema: {
-      action: external_exports.enum(["create", "add_column", "insert", "update", "delete_rows"]),
-      tableId: external_exports.string().optional(),
-      name: external_exports.string().optional().describe("create: table name; add_column: column name"),
-      columns: external_exports.array(external_exports.object({ name: external_exports.string(), type: external_exports.enum(["string", "number", "boolean", "date"]).optional() })).optional(),
-      workflowId: external_exports.string().optional().describe("create: co-locate the table with this workflow (recommended)"),
-      type: external_exports.enum(["string", "number", "boolean", "date"]).optional().describe("add_column only"),
-      rows: external_exports.array(external_exports.record(external_exports.unknown())).optional().describe("insert only"),
-      filter: external_exports.record(external_exports.unknown()).optional().describe("update/delete_rows: {filters:[{columnName,condition,value}], type?}"),
-      data: external_exports.record(external_exports.unknown()).optional().describe("update only: column \u2192 new value")
-    }
-  },
-  async ({ action, tableId, name, columns, workflowId, type, rows, filter, data }) => {
-    try {
-      const cfg = requireConfig();
-      if (action === "create") {
-        return textResult(await hubPost(cfg, "/api/my-n8n/machine/datatables", { name, columns, workflowId }));
-      }
-      if (!tableId) return errorResult(new Error(`tableId is required for ${action}`));
-      const base = `/api/my-n8n/machine/datatables/${encodeURIComponent(tableId)}`;
-      if (action === "add_column") {
-        return textResult(await hubPost(cfg, `${base}/columns`, { name, type }));
-      }
-      const mode = action === "delete_rows" ? "delete" : action;
-      return textResult(await hubPost(cfg, `${base}/rows`, { mode, rows, filter, data }));
-    } catch (err) {
-      return errorResult(err);
-    }
-  }
-);
 server.registerTool(
   "awesomate_skill_update",
   {
@@ -42380,7 +42287,7 @@ server.registerTool(
   "awesomate_domain_add",
   {
     annotations: annotate("awesomate_domain_add", MUTATING),
-    description: "Add a custom domain to the user's hosting account. Returns the DNS steps they need to complete at their registrar. **Needs Support Plus or above from Claude** \u2014 Essentials gets 403 `upgrade_required` even though its plan DOES include one custom domain, because adding it from a machine token is Support Plus; tell them it takes two clicks at hub.awesomate.ai/sites/domains instead. Plan COUNT limits are enforced separately on top.",
+    description: "Add a custom domain to the user's hosting account. Returns the DNS steps they need to complete at their registrar: `dnsInstructions` (A rows only when there is a public address; CNAME rows always) and `dnsNote`. When `dnsNote` is set, relay it word for word: on that server the records must be Proxied (orange cloud) in Cloudflare and SSL/TLS set to Full, not Flexible (Full (strict) only once HTTPS is on); a DNS-only record will not load. **Needs Support Plus or above from Claude** \u2014 Essentials gets 403 `upgrade_required` even though its plan DOES include one custom domain, because adding it from a machine token is Support Plus; tell them it takes two clicks at hub.awesomate.ai/sites/domains instead. Plan COUNT limits are enforced separately on top.",
     inputSchema: { domain: external_exports.string().describe("The domain to add, e.g. example.com") }
   },
   async ({ domain }) => {
@@ -42501,7 +42408,7 @@ readTool(
 );
 readTool(
   "awesomate_get_limits",
-  "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.",
+  "Usage vs plan limits across every dimension (sites, custom domains, apps, 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).",
   "/api/client-hosting/limits"
 );
 var PLAN_LADDER_FALLBACK = {
@@ -42662,7 +42569,7 @@ server.registerTool(
   "awesomate_app_get",
   {
     annotations: annotate("awesomate_app_get", READ_ONLY),
-    description: "Get one app plus its environments (subdomains, ports, db engine/name, deploy + health state) and any hostnames of the user's own attached to them. Poll this after awesomate_app_create \u2014 status goes provisioning \u2192 active | failed (read provision_error on failure).",
+    description: "Get one app plus its environments (subdomains, ports, db engine/name, deploy + health state) and any hostnames of the user's own attached to them. Poll this after awesomate_app_create \u2014 status goes provisioning \u2192 active | failed (read provision_error on failure; to retry, call awesomate_app_create again with the same appSlug, or remove it with awesomate_app_remove_failed).",
     inputSchema: { appId: external_exports.number().int().positive().describe("The app id from awesomate_app_list / _create") }
   },
   async ({ appId }) => {
@@ -42673,6 +42580,24 @@ server.registerTool(
     }
   }
 );
+server.registerTool(
+  "awesomate_app_remove_failed",
+  {
+    annotations: annotate("awesomate_app_remove_failed", DESTRUCTIVE),
+    description: "Remove an app whose setup FAILED (awesomate_app_get shows status 'failed'), clearing whatever the attempt left on the user's hosting (subdomains, databases, folders). Only failed apps: an active, provisioning or suspended app is refused with 409 not_failed, and removing a working app stays a support request. A failed app already holds no plan slot and does not reserve its name, so to RETRY just call awesomate_app_create again with the same appSlug: the hub clears the failed attempt first. Use this when the user wants the failed app gone, not to retry. Tell the user what will be removed and get a yes first; confirm must equal the app's slug.",
+    inputSchema: {
+      appId: external_exports.number().int().positive().describe("The failed app id from awesomate_app_list / _get"),
+      confirm: external_exports.string().describe("Must equal the app's slug exactly, as proof of intent")
+    }
+  },
+  async ({ appId, confirm }) => {
+    try {
+      return textResult(await hubDelete(requireConfig(), `/api/my-apps/apps/${appId}`, { confirm }));
+    } catch (err) {
+      return errorResult(err);
+    }
+  }
+);
 server.registerTool(
   "awesomate_app_create",
   {
@@ -42876,10 +42801,10 @@ server.registerTool(
   "awesomate_n8n_attach_to_app",
   {
     annotations: annotate("awesomate_n8n_attach_to_app", MUTATING),
-    description: "Wire an app to call the user's own n8n as a backend. Give it the app + a webhook URL you already created/tested/promoted on their n8n (via awesomate_n8n_deploy \u2014 create_draft returns the webhook URL, and promote preserves it). It stores N8N_WEBHOOK_URL + a generated N8N_WEBHOOK_SECRET on the app (encrypted + injected) and RETURNS the secret so you can add a matching `X-Awesomate-Webhook-Secret` header check to the n8n workflow (so the webhook isn't world-callable). The app then calls it via src/lib/n8n.ts callWorkflow(). Node apps only. Only reach for this when the job needs an external app/credential or AI the user already has in n8n \u2014 not for pure in-app logic.",
+    description: "Wire an app to call the user's own n8n as a backend. Give it the app + the production webhook URL of a workflow on their n8n (read it with awesomate_n8n_workflows; a workflow Claude built through the instance's own MCP server works too). It stores N8N_WEBHOOK_URL + a generated N8N_WEBHOOK_SECRET on the app (encrypted + injected) and RETURNS the secret so you can add a matching `X-Awesomate-Webhook-Secret` header check to the n8n workflow (so the webhook isn't world-callable). The app then calls it via src/lib/n8n.ts callWorkflow(). Node apps only. Only reach for this when the job needs an external app/credential or AI the user already has in n8n \u2014 not for pure in-app logic.",
     inputSchema: {
       appId: external_exports.number().int().positive().describe("The app id"),
-      webhookUrl: external_exports.string().url().describe("The n8n workflow's production webhook URL (from awesomate_n8n_deploy)"),
+      webhookUrl: external_exports.string().url().describe("The n8n workflow's production webhook URL"),
       env: external_exports.enum(["dev", "staging", "prod"]).default("dev").describe("Which app environment to wire")
     }
   },
@@ -42927,21 +42852,6 @@ server.registerTool(
     }
   }
 );
-server.registerTool(
-  "awesomate_n8n_provision_pg",
-  {
-    annotations: annotate("awesomate_n8n_provision_pg", MUTATING),
-    description: "Provision a NEW Postgres database on the user's own Awesomate cPanel hosting and wire it into their n8n as a ready-to-use `postgres` credential their workflows can select. This is a WRITE that creates real infrastructure \u2014 get explicit user approval first. Requires: their n8n builder access (Support Plus+, allow_client_cli_builds) AND the allow_pg_writes consent (403 consent_required \u2192 send them to settingsUrl); AND an Awesomate cPanel hosting account (409 hosting_required otherwise). Limited to 2/day. Returns the new credential id + name, the database/user, and the password ONCE (it lives in the n8n credential, never stored by Awesomate \u2014 tell the user to note or rotate it). After this, build the workflow selecting the returned Postgres credential.",
-    inputSchema: {}
-  },
-  async () => {
-    try {
-      return textResult(await hubPost(requireConfig(), "/api/my-n8n/machine/pg-credentials", {}));
-    } catch (err) {
-      return errorResult(err);
-    }
-  }
-);
 function knowledgeResult(data) {
   return {
     content: [
@@ -43731,7 +43641,7 @@ server.registerTool(
       key: external_exports.string().max(41).optional().describe("save_calendar, save_service: lower case, digits and underscores"),
       name: external_exports.string().max(80).optional(),
       timezone: external_exports.string().max(60).optional().describe("IANA zone, like Australia/Sydney"),
-      hours: external_exports.record(external_exports.string(), external_exports.array(external_exports.tuple([external_exports.string(), external_exports.string()]))).optional().describe('save_calendar: {"mon": [["09:00","17:00"]], ...}'),
+      hours: external_exports.record(external_exports.string(), external_exports.array(external_exports.array(external_exports.string()).length(2))).optional().describe('save_calendar: {"mon": [["09:00","17:00"]], ...}'),
       min_notice_minutes: external_exports.number().int().min(0).optional(),
       buffer_minutes: external_exports.number().int().min(0).optional(),
       max_per_day: external_exports.number().int().min(1).nullable().optional(),
@@ -44432,7 +44342,7 @@ server.registerTool(
 server.registerTool(
   "awesomate_site_audit",
   {
-    description: "Run the SEO + AEO build gates against ONE live page the user owns, fetched AS GPTBot. Returns pass/fail per gate with specific fixes: is the content in the raw HTML at all (a React/Vue site is invisible to ChatGPT, Claude and Perplexity \u2014 only Gemini and Applebot run JavaScript), can the four retrieval bots reach it, is there an accidental noindex/nosnippet, does the canonical point at THIS domain (a leftover pointing at a Replit/Vercel/staging host silently de-indexes the real site), is the structured data valid AND mirrored in visible text, is the content structured so a single section survives being quoted, robots.txt + sitemap, and time-to-first-byte. Run it after building or changing any public page, and before telling the user their site is discoverable \u2014 reads on every plan. Two gates are reported as `skipped` because they need a headless browser or a full crawl; treat skipped as unknown, never as passing.",
+    description: "Run the SEO + AEO build gates against ONE live page the user owns, fetched AS OAI-SearchBot (a retrieval bot, so it sees what ChatGPT search sees; training crawlers like GPTBot are blocked by design on Awesomate-managed domains). Returns pass/fail per gate with specific fixes: is the content in the raw HTML at all (a React/Vue site is invisible to ChatGPT, Claude and Perplexity \u2014 only Gemini and Applebot run JavaScript), can the four retrieval bots reach it, is there an accidental noindex/nosnippet, does the canonical point at THIS domain (a leftover pointing at a Replit/Vercel/staging host silently de-indexes the real site), is the structured data valid AND mirrored in visible text, is the content structured so a single section survives being quoted, robots.txt + sitemap, and time-to-first-byte. Run it after building or changing any public page, and before telling the user their site is discoverable \u2014 reads on every plan. Two gates are reported as `skipped` because they need a headless browser or a full crawl; treat skipped as unknown, never as passing.",
     inputSchema: {
       domain: external_exports.string().min(3).max(253).describe("a domain on the user's own hosting account"),
       path: external_exports.string().max(400).optional().describe("page path to audit, default /")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.87.0",
+  "version": "0.88.6",
   "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",
@@ -28,6 +28,7 @@
     "zod": "^3.24.1"
   },
   "devDependencies": {
+    "@anthropic-ai/sdk": "^0.132.0",
     "@types/node": "^25.9.3",
     "esbuild": "^0.25.0",
     "typescript": "^6.0.3"

package/skill/CHANGELOG.json

@@ -1,5 +1,48 @@
 {
   "versions": [
+    {
+      "version": "0.88.6",
+      "highlights": [
+        "An app whose setup failed no longer uses one of your app slots or blocks its name: create it again with the same name to retry, or ask Claude to remove it with the new awesomate_app_remove_failed tool"
+      ]
+    },
+    {
+      "version": "0.88.5",
+      "highlights": [
+        "Adding a domain now gives your server's public address, never an internal one, and says the records must be Proxied (orange cloud) in Cloudflare with SSL/TLS set to Full"
+      ]
+    },
+    {
+      "version": "0.88.4",
+      "highlights": [
+        "The site audit now reads your page the way ChatGPT search does, so a page that turns AI bots away is reported as unreachable instead of being scored on the block message, and the sitemap check no longer reports a sitemap missing when it is there",
+        "SEO checks test the AI search bots that decide whether you get cited. AI training bots are blocked on purpose on Awesomate-managed addresses, so Claude no longer reports that as a fault"
+      ]
+    },
+    {
+      "version": "0.88.3",
+      "highlights": [
+        "When the hub cannot bring your n8n credential list up to date, Claude now says the list may be out of date, as of when, and which credentials n8n has added or removed since"
+      ]
+    },
+    {
+      "version": "0.88.2",
+      "highlights": [
+        "Fixed: the booking diary tool described its opening hours in an older JSON Schema form that strict clients refuse, which would stop every Awesomate tool loading there. Nothing changes in Claude Code"
+      ]
+    },
+    {
+      "version": "0.88.1",
+      "highlights": [
+        "Bookings can keep a calendar's busy times free from Outlook as well as Google Calendar, and write each booking into it; the owner connects it in the hub"
+      ]
+    },
+    {
+      "version": "0.88.0",
+      "highlights": [
+        "Claude no longer builds workflows through Awesomate: it writes them straight on your own n8n through n8n's MCP server (switch on MCP access in your n8n and add its key to Claude Code), with no Awesomate limits on it. Reading your n8n, installing templates and n8n Agents work as before"
+      ]
+    },
     {
       "version": "0.87.0",
       "highlights": [

package/skill/awesomate-app-builder/SKILL.md

@@ -70,9 +70,10 @@ decision brain. The short version, matched to what they say:
     a static app — there is nowhere to put a secret. Anything the page must
     keep private (an API key, a webhook URL you don't want public) rules
     static out.
-  - **`awesomate_n8n_attach_to_app` is Node-only.** So the "form posts to
-    their n8n" pattern needs a Node app, unless the webhook URL being public
-    is genuinely acceptable.
+  - **`awesomate_n8n_attach_to_app` is Node-only.** It takes any production
+    webhook URL on their n8n and stores it with a secret on the app, so the
+    "form posts to their n8n" pattern needs a Node app, unless the webhook
+    URL being public is genuinely acceptable.
   - **No separate dev site.** All three environment URLs point at the same
     single subdomain — there's no dev copy to review on, so every change is
     live the moment it's published.
@@ -125,7 +126,10 @@ target; never touch prod without an explicit ask.**
    webhooks/integrations → `node-api-only`; landing page → `static-landing`.
    It returns **202** with an `appId` + subdomain(s); poll `awesomate_app_get`
    until `status` is `active` (or `failed` — read `provision_error`, explain
-   plainly).
+   plainly). A failed app holds no plan slot and doesn't keep its name: to
+   retry, call `awesomate_app_create` again with the same `appSlug` (the hub
+   clears the failed attempt first). If the user would rather drop it, offer
+   `awesomate_app_remove_failed` (`confirm` = the slug) after their yes.
 4. **Scaffold** — call `awesomate_app_scaffold` and write each returned file
    into a fresh local project folder at its relative path (placeholders are
    already substituted), then `npm install` (Node) and read the bundled
@@ -256,10 +260,11 @@ keep going on what you can fix.
 - A `409` with code `app_limit` = the plan's app allowance is full (Support
   Plus 5, Pro 20 — `awesomate_app_context.limits` has the live numbers).
   Don't retry; tell the user and surface the `recommendedPlan`/`deepLink`
-  from the error. **There is no delete-app tool or route** — don't offer
-  "delete an old one to free a slot", because neither you nor the user can.
-  The honest options are an upgrade or asking support (awesomate-support
-  skill) to remove an app.
+  from the error. Failed apps never count toward it. There is no tool to
+  delete a WORKING app — don't offer "delete an old one to free a slot",
+  because neither you nor the user can. The honest options are an upgrade or
+  asking support (awesomate-support skill) to remove an app.
+  (`awesomate_app_remove_failed` only removes an app whose setup failed.)
 - Never invent that a capability exists — read `awesomate_app_context` first.
 - Never build on the hosting account, and never raise a support ticket for a
   repo or deploy problem yourself: the hub does both the building (via

package/skill/awesomate-app-builder/references/node-recipes.md

@@ -50,8 +50,9 @@ with a clear reason). Postgres code should prefer `DATABASE_URL`.
 ## Attach n8n as the backend
 
 Job needs email / a lookup in their connected apps / AI → build the webhook
-workflow with the awesomate-n8n skill, then `awesomate_n8n_attach_to_app`
-(stores `N8N_WEBHOOK_URL` + secret; returns the secret ONCE — add the
+workflow with the awesomate-n8n skill (through the user's own n8n MCP
+server), then `awesomate_n8n_attach_to_app` with its production webhook URL
+(stores `N8N_WEBHOOK_URL` + secret; returns the secret ONCE: add the
 matching `X-Awesomate-Webhook-Secret` header check to the workflow). The app
 calls `callWorkflow(payload)` from `src/lib/n8n.ts`; it no-ops when unset and
 never throws — check `result.ok` and degrade gracefully.

package/skill/awesomate-app-builder/references/stack-decision.md

@@ -65,13 +65,14 @@ credentials are already connected there, so there's nothing new to set up.
 - Check what's connected with `awesomate_n8n_inspect {what:'credentials'}`
   (names/types only) and offer what they already have: *"You've got Gmail +
   Google Sheets connected — want the form to email you and add the lead to a
-  sheet?"* That read needs the **"Build and change automations from Claude Code"**
+  sheet?"* That read needs the **"Let Claude Code work with your automations"**
   privacy toggle, which is off by default — a 403 `consent_required` means
   call `awesomate_privacy_settings`, name the toggle, and ask the user to flip
   it at hub.awesomate.ai/settings?tab=privacy.
 - Build the workflow with the **awesomate-n8n** skill (webhook trigger →
-  action), take its **webhook URL**, and wire it into the app.
-  - **Node app:** `awesomate_n8n_attach_to_app` — it stores
+  action, written through the user's own n8n MCP server), take its
+  **production webhook URL**, and wire it into the app.
+  - **Node app:** `awesomate_n8n_attach_to_app` with that URL. It stores
     `N8N_WEBHOOK_URL` plus a generated `N8N_WEBHOOK_SECRET` (encrypted +
     injected) and returns the secret so you can add the matching
     `X-Awesomate-Webhook-Secret` check on the n8n side. `src/lib/n8n.ts`

package/skill/awesomate-bookings/SKILL.md

@@ -82,9 +82,12 @@ themselves cannot be written through `awesomate_crm_write`; only these actions c
   Essentials, the tool answers `upgrade_required`: say the owner can do the same in the hub under
   Contacts, Bookings, and do not retry.
 - Payments and deposits are not part of bookings yet. Do not promise them; the price is shown only.
-- **Google Calendar** is connected per calendar in the hub (Contacts, Bookings, Set up, Connect
-  Google Calendar), by the person whose calendar it is: Claude cannot connect it, so send them
-  there. Once connected, times they are busy in Google are never offered, and every booking is
-  written to an "Awesomate bookings" calendar in their Google account, moved and removed with it.
-  `setup` lists the connected calendars under `links`. Outlook is not available yet; there the
-  notice email's invite is how a booking reaches their calendar.
+- **Google Calendar or Outlook** is connected per calendar in the hub (Contacts, Bookings, Set
+  up, Connect Google Calendar or Connect Outlook), by the person whose calendar it is: Claude
+  cannot connect it, so send them there. Once connected, times they are busy there are never
+  offered, and every booking is written to an "Awesomate bookings" calendar in their account,
+  moved and removed with it. `setup` lists the connected calendars under `links` (each with its
+  `provider`), and says which providers this hub offers (`google.available`,
+  `microsoft.available`). Where neither is offered, the notice email's invite is how a booking
+  reaches their calendar. A work account whose organisation limits apps may need its Microsoft
+  365 admin to approve Awesomate once; the hub says so when that happens.