@awesomate/hosting-mcp 0.30.0 → 0.31.0

package/dist/index.js

@@ -40992,6 +40992,7 @@ var TITLES = {
   awesomate_n8n_kpis: "Get n8n KPIs",
   awesomate_n8n_node_docs: "Get n8n node docs",
   awesomate_n8n_deploy: "Deploy n8n workflow",
+  awesomate_n8n_library: "Install Awesomate templates",
   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",
@@ -41124,6 +41125,39 @@ server.registerTool(
     }
   }
 );
+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+). Workflows land INACTIVE; activation, testing and rollback of installed bundles arrive in the next release. 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"]),
+      slug: external_exports.string().optional().describe("Bundle slug from list (detail, install_plan, install)"),
+      token: external_exports.string().optional().describe("redeem only: the redeem token Awesomate handed over"),
+      proceed_without: external_exports.array(external_exports.string()).optional().describe("install only: OPTIONAL credential types the client agreed to skip (from install_plan.optional_missing)"),
+      credential_choices: external_exports.record(external_exports.string()).optional().describe("install only: credential type -> credential id the client chose for ambiguous types (from install_plan.ambiguous)")
+    }
+  },
+  async ({ action, slug, token, proceed_without, credential_choices }) => {
+    try {
+      const cfg = requireConfig();
+      if (action === "list") return textResult(await hubGet(cfg, "/api/my-n8n/library"));
+      if (action === "redeem") {
+        if (!token) return errorResult(new Error("token is required for redeem"));
+        return textResult(await hubPost(cfg, "/api/my-n8n/library/redeem", { token }));
+      }
+      if (!slug) return errorResult(new Error(`slug is required for ${action}`));
+      const base = `/api/my-n8n/library/bundles/${encodeURIComponent(slug)}`;
+      if (action === "detail") return textResult(await hubGet(cfg, base));
+      if (action === "install_plan") return textResult(await hubPost(cfg, `${base}/install-plan`, {}));
+      return textResult(
+        await hubPost(cfg, `${base}/install`, { proceed_without: proceed_without ?? [], credential_choices: credential_choices ?? {} })
+      );
+    } catch (err) {
+      return errorResult(err);
+    }
+  }
+);
 server.registerTool(
   "awesomate_n8n_test",
   {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.30.0",
+  "version": "0.31.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,13 @@
 {
   "versions": [
+    {
+      "version": "0.31.0",
+      "highlights": [
+        "Install Awesomate's ready-made automations from Claude Code: awesomate_n8n_library lists the bundles your account may use, including the ones linked to your referrer, explains what each does, and installs them into your n8n",
+        "Before anything is written, install_plan checks the credentials each template needs. If one is missing it pauses and tells you where to get it, the exact page on your n8n to create it, and the help article; then you re-run and install",
+        "Every credential is yours; nothing is placed in your account on your behalf. Essentials sees the catalog; installing needs Support Plus"
+      ]
+    },
     {
       "version": "0.30.0",
       "highlights": [

package/skill/awesomate-app-builder/scripts/migrate-check.mjs

@@ -142,7 +142,20 @@ if (replitAuth) add('replit_auth', 'warn', 'Replit Auth (OIDC against replit.com
 if (ws) add('websockets_proxy', 'info', 'WebSockets are used', { fix: 'Nothing to do: the reverse proxy forwards the Upgrade handshake on every environment address and attached hostname.' });
 if (evalUse) add('dynamic_code_eval', 'warn', 'eval() or new Function() in source', { fix: 'The prod security gate blocks these; replace before merging to main.' });
 if (detected.node && !/(^|[^0-9])22([^0-9]|$)|>=\s*(1[8-9]|2[0-2])/.test(String(detected.node))) add('node_engine_mismatch', 'warn', `engines.node is "${detected.node}"; Awesomate runs Node 22`, { fix: 'Test on Node 22 locally; update engines.' });
-if (pkg.scripts?.start && /NODE_ENV=/.test(pkg.scripts.start)) add('start_sets_node_env', 'info', 'start script sets NODE_ENV inline', { fix: 'Not needed: the account .env sets NODE_ENV per environment. deploy.start is the entry file, e.g. dist/index.js.' });
+if (pkg.scripts?.start && /NODE_ENV=/.test(pkg.scripts.start)) add('start_sets_node_env', 'info', 'start script sets NODE_ENV inline', { fix: 'Not needed: the account .env sets NODE_ENV=production. deploy.start is the entry file, e.g. dist/index.js.' });
+// The Vite pattern that killed careconnect's first deploy: dev-only middleware
+// behind a NODE_ENV check, imported at the top level. NODE_ENV is "production"
+// on every Awesomate environment, so the dev branch never runs; a TOP-LEVEL
+// import of vite still fails at startup because vite is not installed.
+const viteServerFiles = files.filter((f) => /import[^;]*['"]vite['"]|from ['"]vite['"]|require\(['"]vite['"]\)/.test((() => { try { return readFileSync(f, 'utf8'); } catch { return ''; } })()));
+for (const f of viteServerFiles) {
+  const rel = relative(dir, f);
+  if (/^(vite\.config|client\/)/.test(rel)) continue;
+  add('vite_imported_at_runtime', 'blocker', `${rel} imports vite, which is a devDependency and is NOT installed on the server`, {
+    file: rel,
+    fix: "Import vite only inside the branch that needs it (await import('vite') behind a NODE_ENV !== 'production' check), or better: serve the built client with express.static and delete the dev-server path from the deployed bundle. Awesomate sets NODE_ENV=production on every environment (use AWESOMATE_ENV to tell dev from prod).",
+  });
+}
 if (existsSync(join(dir, 'main.py'))) add('python_file_present', 'info', 'main.py present', { fix: 'Only Node runs on the account; delete it if it is a leftover.' });
 
 for (const name of readdirSync(dir, { withFileTypes: true })) {

package/skill/awesomate-knowledge/evals/deploy-chat-agent/graders/grader.md

@@ -10,7 +10,7 @@ numbered criteria hold and no automatic fail triggers.
    front of it.
 2. Treats KB-CHAT-7Q2M as the bundle redeem token and installs via the
    redeem path (hub Templates page or
-   `POST /api/client-settings/redeem {token}`) — it does NOT hand-build the
+   `POST /api/my-n8n/library/redeem (via awesomate_n8n_library redeem) {token}`) — it does NOT hand-build the
    chat workflow, the Setup Tool, or any credential node by node.
 3. Never creates, edits, or asks about the "Awesomate Knowledge Base"
    credential — the hub provisions it; a missing/broken one routes to the

package/skill/awesomate-knowledge/references/n8n-connection.md

@@ -55,9 +55,9 @@ Variables (all read from `$vars`, all with fallbacks):
 
 Flow you drive: confirm the knowledge base is active with indexed content and
 one published agent → the member installs the bundle from the hub's
-**Library** page (`/templates`, card "Verified Content Chat Agent"; a redeem
-token via `POST /api/client-settings/redeem {token}` also works if Awesomate
-hands one over) → the workflow publishes on install once the scope credential
+**Library** page (`/templates`, card "Verified Content Chat Agent"), or you install it
+for them with `awesomate_n8n_library { action: 'install_plan' | 'install', slug }` (a
+redeem token Awesomate handed over goes through `{ action: 'redeem', token }`) → the workflow publishes on install once the scope credential
 is verified → open "When chat message received", copy the **Chat URL**, and
 give them the embed snippet (it is also in the workflow's HOW IT WORKS note):
 

package/skill/awesomate-n8n/SKILL.md

@@ -93,6 +93,7 @@ the named node actually exists in the workflow before editing anything.
 | Node schemas, node search, community templates, node-level validation | `awesomate_n8n_node_docs` |
 | Validate / create draft / update draft / activate / promote / rollback / delete draft | `awesomate_n8n_deploy` |
 | Fire a test payload at an active workflow | `awesomate_n8n_test` |
+| Awesomate's template library: list, detail, install_plan (pauses on a missing credential), install, redeem | `awesomate_n8n_library` |
 | Create/alter data tables, write rows | `awesomate_n8n_datatable_write` |
 | Provision a Postgres DB + n8n credential | `awesomate_n8n_provision_pg` |
 | Wire a tested webhook workflow into one of their hosted apps (stores URL + secret on the app; returns the secret ONCE for the workflow's header check) | `awesomate_n8n_attach_to_app` |
@@ -177,6 +178,40 @@ what ran and what the human must verify ("check your inbox").
 the webhook URL, and what happens next. Delete unneeded drafts
 (`delete_draft`, deactivated only).
 
+## 3a. Installing an Awesomate template (bundle)
+
+Awesomate curates ready-made automations and agents, some linked to the account's
+referrer (a Business Blueprint member sees Dale Beaumont's bundles). This is the path for
+"set me up with the X templates" from someone who has never opened n8n. It is NOT the build
+loop: nothing is designed, the bundle is installed as curated.
+
+1. `awesomate_n8n_library { action: 'list' }`. Show the bundles by name with one line each,
+   mark `installed`, and say which need credentials the account does not have yet
+   (`credentials_missing`). Never show workflow JSON; the description is the product.
+2. `detail` for the one they pick. Read out what each template does and the credential
+   list with `have` ticks. Ask before installing.
+3. `install_plan`. Three answers:
+   - `ready`: go to step 4.
+   - `paused`: for each entry in `help_cards` tell them, in this order, what the credential
+     is for, `provider_url` + `provider_note` (where the key comes from), `create_url` (the
+     exact page on THEIR n8n that opens the create form), then any `help_articles`. Offer
+     the assisted route ONLY after that: a support session with the Awesomate team
+     (`assisted.book_session_url`, one credit). You never create a credential for them and
+     never ask for the secret in chat. When they say it is done, re-run `install_plan`.
+     `optional_missing` may be skipped with their say-so (pass them in `proceed_without`);
+     `ambiguous` needs their pick (`credential_choices`, type to credential id).
+   - `blocked`: read `blockers` verbatim. A plan or consent block has a settings link; a
+     connection block means their n8n key needs updating (see 0. First run).
+4. `install`. Workflows land INACTIVE. Say so, and say that switching on, testing and
+   rolling back from here arrive in the next release; until then the hub's Library page
+   (`/templates`) does it. Do not try `awesomate_n8n_deploy activate` on them: installed
+   templates are refused there as agency-managed.
+5. A 403 whose `missingScopes` contains `n8n:deploy` means Essentials. Show the catalog,
+   say installing needs Support Plus, link `https://hub.awesomate.ai/billing`, and stop.
+
+`redeem` takes a token Awesomate handed over and installs what it unlocks, no visibility
+check; use it when the member has a token, otherwise use the catalog.
+
 ## 4. Changing a LIVE workflow
 
 Never edit a live workflow directly, and never "activate the copy" — the