@awesomate/hosting-mcp 0.15.0 → 0.16.0

package/dist/index.js

@@ -40031,7 +40031,7 @@ server.registerTool(
 server.registerTool(
   "awesomate_get_context",
   {
-    description: "Call this FIRST each session. Returns the connected Awesomate account: plan, capabilities (shell access), plan limits, scopes this token can exercise, token expiry (warn the user if within 7 days), cPanel routing when provisioned, and skill.updateAvailable \u2014 if true, the local awesomate-hosting skill files are older than this server; tell the user to re-run Connect Claude Code from hub.awesomate.ai/sites to refresh them (this also renews the token).",
+    description: "Call this FIRST each session. Returns the connected Awesomate account: plan, capabilities (shell access), plan limits, scopes this token can exercise, token expiry (warn the user if within 7 days), cPanel routing when provisioned, and skill.updateAvailable \u2014 if true, the local Awesomate skill files are older than this server; run awesomate_skill_update to refresh them in place (new content loads next session \u2014 mention once, finish the current task first). If the token is also near expiry, re-running Connect Claude Code from hub.awesomate.ai/sites refreshes skills AND renews the token in one go.",
     inputSchema: {}
   },
   async () => {
@@ -40285,10 +40285,10 @@ server.registerTool(
 server.registerTool(
   "awesomate_support",
   {
-    description: "Help the user with the service itself \u2014 questions, being stuck, or reaching a human. action 'faq' {q} searches the published help library (answer FROM the results; never invent policy or pricing). action 'create_ticket' {subject, message} opens a support ticket \u2014 draft it in the user's words, SHOW it, and get an explicit yes before sending; it emails the Awesomate team and returns a portal URL. action 'list_tickets' shows their tickets and status. Use the awesomate-support skill for the full flow. Not for building \u2014 route n8n work to awesomate-n8n and hosting to awesomate-hosting.",
+    description: "Help the user with the service itself \u2014 questions, being stuck, or reaching a human. action 'faq' {q} searches the published help library (answer FROM the results; never invent policy or pricing). action 'help_docs' {q} searches the full Help Centre articles live \u2014 use when the FAQ has no good answer, and cite the returned article URLs. action 'create_ticket' {subject, message} opens a support ticket \u2014 draft it in the user's words, SHOW it, and get an explicit yes before sending; it emails the Awesomate team and returns a portal URL. action 'list_tickets' shows their tickets and status. Use the awesomate-support skill for the full flow. Not for building \u2014 route n8n work to awesomate-n8n and hosting to awesomate-hosting.",
     inputSchema: {
-      action: external_exports.enum(["faq", "create_ticket", "list_tickets"]),
-      q: external_exports.string().optional().describe("faq only: the question"),
+      action: external_exports.enum(["faq", "help_docs", "create_ticket", "list_tickets"]),
+      q: external_exports.string().optional().describe("faq and help_docs: the question or topic"),
       subject: external_exports.string().optional().describe("create_ticket only"),
       message: external_exports.string().optional().describe("create_ticket only: the body, in the user's words")
     }
@@ -40299,6 +40299,10 @@ server.registerTool(
       if (action === "faq") {
         return textResult(await hubGet(cfg, `/api/help/faq${q ? `?q=${encodeURIComponent(q)}` : ""}`));
       }
+      if (action === "help_docs") {
+        if (!q) return errorResult(new Error("help_docs needs q"));
+        return textResult(await hubGet(cfg, `/api/help/docs?q=${encodeURIComponent(q)}`));
+      }
       if (action === "list_tickets") {
         return textResult(await hubGet(cfg, "/api/support/tickets"));
       }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "description": "Awesomate MCP server \u2014 lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases",
   "license": "UNLICENSED",
   "type": "module",

package/skill/awesomate-hosting/SKILL.md

@@ -37,8 +37,9 @@ once (plus `awesomate_get_limits` before any create/change) and cache:
 - **`patExpiresAt`** — within ~7 days, or any 401: re-run the setup prompt at
   **hub.awesomate.ai/sites → Connect Claude Code** to refresh the token.
 - **`skill.updateAvailable`** — this skill's local files are older than the MCP
-  server. Mention once (don't nag); the same Connect re-run refreshes the skill
-  and renews the token in one go. Not urgent — finish the user's request first.
+  server. Mention once (don't nag); run `awesomate_skill_update` to refresh in
+  place (new content loads next session). If the token is also near expiry, the
+  Connect re-run above does both. Not urgent — finish the user's request first.
 - **`cpanel`** routing (host/user), present once hosting is provisioned.
 
 If `awesomate_get_context` fails with a connectivity error, it's the user's

package/skill/awesomate-support/SKILL.md

@@ -20,18 +20,22 @@ also carries the plan). Describe what a plan or upgrade INCLUDES from
 balance without spending anything. Never quote a plan, price, or balance
 from memory.
 
-## 1. FAQ first
+## 1. FAQ first, then help docs
 
 For any "how do I", "why does", "what is" question about the service:
 
 1. Call `awesomate_support {action:'faq', q:'<their question>'}`.
 2. Answer FROM the returned entries, in your own plain words. Cite nothing
    the FAQ and tools didn't say — no invented policy, no guessed pricing.
-3. If the FAQ answers it, you're done. If it partially answers, give what
-   you have and say which part is unconfirmed.
-4. If it doesn't answer it: "I don't have a confirmed answer for that. Want
+3. If the FAQ misses or only partially answers, call
+   `awesomate_support {action:'help_docs', q:'<topic>'}` — a live search of
+   the full Help Centre articles. Answer from the excerpts and give the
+   article's URL so the user can read the full steps.
+4. If neither answers it: "I don't have a confirmed answer for that. Want
    me to ask the Awesomate team? I'll draft a support ticket for you to
-   approve first." Then go to §2 if they say yes.
+   approve first." Then go to §2 if they say yes. (An empty help_docs
+   result can also mean the search is temporarily down — the response's
+   help_centre_url is always safe to offer for browsing.)
 
 ## 2. Ticket flow — talking to a human