@awesomate/hosting-mcp 0.10.0 → 0.11.0

package/dist/index.js

@@ -40111,22 +40111,36 @@ 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 PLAN_LADDER_FALLBACK = {
+  note: "Live per-account limits come from awesomate_get_limits \u2014 this is the plan ladder reference (static fallback).",
+  plans: [
+    { name: "Essentials", purchasable: false, monthlyPriceUsd: 75, maxSites: 1, maxCustomDomains: 0, maxApps: 0, cpanelAccess: true, shellAccess: false, appBuilder: false },
+    { name: "Support Plus", purchasable: true, monthlyPriceUsd: 175, maxSites: 2, maxCustomDomains: 3, maxApps: 5, cpanelAccess: true, shellAccess: true, appBuilder: true },
+    { name: "Pro", purchasable: true, monthlyPriceUsd: 375, maxSites: 10, maxCustomDomains: 10, maxApps: 20, cpanelAccess: true, shellAccess: true, appBuilder: true },
+    { name: "Embedded", purchasable: false, monthlyPriceUsd: null, maxSites: 100, maxCustomDomains: 100, maxApps: 100, cpanelAccess: true, shellAccess: true, appBuilder: true, 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)"
+};
 server.registerTool(
   "awesomate_get_plan_features",
   {
-    description: "Static reference: what each Awesomate plan includes for hosting (sites, custom domains, cPanel, shell/Claude Code access) and monthly pricing. Use to explain what an upgrade unlocks.",
+    description: "The Awesomate plan ladder: what each plan includes for hosting (WordPress sites, custom domains, hosted apps, cPanel, shell/Claude Code access) and which plans are purchasable. Fetched live from the hub (single source of truth) with a static fallback. Use to explain what an upgrade unlocks; live per-account usage comes from awesomate_get_limits.",
     inputSchema: {}
   },
-  async () => textResult({
-    note: "Live per-account limits come from awesomate_get_limits \u2014 this is the plan ladder reference.",
-    plans: [
-      { name: "Essentials", monthlyPriceUsd: 75, maxSites: 1, maxCustomDomains: 0, cpanelAccess: true, shellAccess: false },
-      { name: "Support Plus", monthlyPriceUsd: 175, maxSites: 1, maxCustomDomains: 1, cpanelAccess: true, shellAccess: true },
-      { name: "Pro", monthlyPriceUsd: 375, maxSites: 3, maxCustomDomains: 3, cpanelAccess: true, shellAccess: true },
-      { name: "Embedded", monthlyPriceUsd: null, maxSites: null, maxCustomDomains: null, cpanelAccess: true, shellAccess: true, note: "Unlimited sites/domains; not generally available yet" }
-    ],
-    upgradePath: "Essentials \u2192 Support Plus \u2192 Pro \u2192 Embedded; upgrades at hub.awesomate.ai/billing"
-  })
+  async () => {
+    try {
+      const live = await hubGet(requireConfig(), "/api/client-hosting/plan-ladder");
+      if (Array.isArray(live?.plans) && live.plans.length > 0) {
+        return textResult({
+          note: "Live plan ladder from the hub. Per-account usage comes from awesomate_get_limits.",
+          ...live,
+          upgradePath: PLAN_LADDER_FALLBACK.upgradePath
+        });
+      }
+    } catch {
+    }
+    return textResult(PLAN_LADDER_FALLBACK);
+  }
 );
 server.registerTool(
   "awesomate_snapshot_site",
@@ -40207,7 +40221,7 @@ server.registerTool(
 server.registerTool(
   "awesomate_app_create",
   {
-    description: "Provision a new app on the client's cPanel account. Choose the stack deliberately (see the awesomate-app-builder skill): kind 'static' = a single fast landing/lead page served straight from the docroot (no DB, no server process \u2014 pick this for brochure/landing/lead-capture); kind 'node' = a dynamic app with a backend + database (logins, custom logic, an API). Pick the template by job \u2014 'node-auth-sync' (user accounts/logins, MySQL), 'node-crud-postgres' (structured data without logins: trackers/dashboards \u2014 ready-made CRUD + UI, Postgres), 'node-api-only' (webhooks/integrations/glue, no DB wiring), 'static-landing' (marketing/lead page). If dbEngine is omitted the template's native engine is used (node-crud-postgres \u2192 postgres). Returns 202 immediately with an appId + subdomain(s); poll awesomate_app_get until status=active, then fetch the starter files with awesomate_app_scaffold. Requires apps:write (Support Plus+) \u2014 a 403 means offer an upgrade. Get the user's confirmation on the stack + name before calling.",
+    description: "Provision a new app on the client's cPanel account. Choose the stack deliberately (see the awesomate-app-builder skill): kind 'static' = a single fast landing/lead page served straight from the docroot (no DB, no server process \u2014 pick this for brochure/landing/lead-capture); kind 'node' = a dynamic app with a backend + database (logins, custom logic, an API). Pick the template by job \u2014 'node-auth-sync' (user accounts/logins, MySQL), 'node-crud-postgres' (structured data without logins: trackers/dashboards \u2014 ready-made CRUD + UI, Postgres), 'node-api-only' (webhooks/integrations/glue, no DB wiring), 'static-landing' (marketing/lead page). If dbEngine is omitted the template's native engine is used (node-crud-postgres \u2192 postgres). Returns 202 immediately with an appId + subdomain(s); poll awesomate_app_get until status=active, then fetch the starter files with awesomate_app_scaffold. Requires apps:write (Support Plus+) \u2014 a 403 means offer an upgrade. Plans also cap the NUMBER of apps (Support Plus 5, Pro 20 \u2014 check awesomate_get_limits.dimensions.apps first): a 409 with code 'app_limit' means the cap is reached \u2014 do NOT retry; tell the user their allowance is full and surface the recommendedPlan/deepLink from the error. Get the user's confirmation on the stack + name before calling.",
     inputSchema: {
       appSlug: external_exports.string().regex(/^[a-z][a-z0-9]{1,15}$/).describe("2-16 chars, starts with a letter, lowercase alphanumeric \u2014 used for subdomains + db names"),
       kind: external_exports.enum(["node", "static"]).default("node").describe("'static' for a landing/lead page (no DB); 'node' for a dynamic app"),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.10.0",
+  "version": "0.11.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/awesomate-app-builder/SKILL.md

@@ -115,6 +115,10 @@ files directly (no build step).
 - Confirm the stack + name before `awesomate_app_create`. Default the target
   to **dev**; never push to prod without an explicit ask.
 - A `403` on a write = plan gate (Support Plus+). Offer an upgrade, don't retry.
+- 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. Deleting an unused app also frees a slot.
 - Never invent that a capability exists — read `awesomate_app_context` first.
 - Never print a secret or commit a `.env` (the credentials + github skills
   enforce this).

package/skill/awesomate-hosting/SKILL.md

@@ -148,15 +148,18 @@ natural break so the richer MCP integration loads.
 
 ## 1. The plan model (so your nudges are accurate)
 
-| Plan | WP sites | Custom domains | Shell / Claude Code | Notes |
-|---|---|---|---|---|
-| **Essentials** | 1 | 0 | **No** | read/status + upgrade nudges only |
-| **Support Plus** | (per plan) | ≥1 | **Yes** | shell, WP-CLI, snapshot/rollback, deploy |
-| **Pro** | more | more | **Yes** | + higher limits |
-| **Embedded** | ∞ | ∞ | **Yes** | agency tier |
+| Plan | WP sites | Hosted apps | Custom domains | Shell / Claude Code | Notes |
+|---|---|---|---|---|---|
+| **Essentials** | 1 | 0 | 0 | **No** | read/status + upgrade nudges only |
+| **Support Plus** | 2 | 5 | 3 | **Yes** | shell, WP-CLI, snapshot/rollback, deploy, app builder |
+| **Pro** | 10 | 20 | 10 | **Yes** | + higher limits |
+| **Embedded** | 100 | 100 | 100 | **Yes** | agency tier, not generally available |
 
 Authoritative limits are always what `awesomate_get_limits` returns for THIS
-account — never quote the table above as fact; use it only to explain upgrades.
+account (and `awesomate_get_plan_features` fetches the live ladder from the
+hub) — never quote the table above as fact; use it only to explain upgrades.
+App creation past the cap returns a 409 with code `app_limit` — don't retry;
+surface the recommended plan instead.
 
 ## 2. Branch by capability