@awesomate/hosting-mcp 0.22.0 → 0.22.1

package/dist/index.js

@@ -41224,7 +41224,7 @@ server.registerTool(
 server.registerTool(
   "awesomate_site_create",
   {
-    description: "Create a WordPress site on the user's hosting. Plan limits are enforced server-side (429/403 with an upgrade hint if they're at their cap \u2014 relay it). Ask 'live or dev?' first per the awesomate-hosting skill. Returns the new site's admin details.",
+    description: "Create a WordPress site on the user's hosting. Plan limits are enforced server-side (429/403 with an upgrade hint if they're at their cap \u2014 relay it; 409 means WordPress already exists at that domain). Ask 'live or dev?' first per the awesomate-hosting skill. Omit `domain` and the next free siteN.{primary} subdomain is chosen for you. ASYNC and returns only {success:true} \u2014 no domain, no admin details: poll awesomate_list_sites to learn the name, and expect HTTPS to refuse connections for a minute or two while AutoSSL issues even though the site is already serving over http. See 'After creating a site' in the skill.",
     inputSchema: {
       domain: external_exports.string().optional().describe("Custom domain if they have one; omit for a default *.awesomate.site subdomain"),
       siteTitle: external_exports.string().optional(),

package/package.json

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

@@ -89,6 +89,21 @@ proxy failures, resuming a connect, support report) ·
 `references/rest-fallback.md` (no `awesomate_*` tools — serve over REST) ·
 `references/voice.md` (how to talk to a non-technical owner).
 
+## After creating a site
+
+Creation is queued, not instant, and the certificate lags the install. For a
+minute or two afterwards `https://` refuses the connection while `http://`
+already returns real WordPress HTML — and `sslActive` in the site list may
+already read `true`, because it reports intent rather than the live cert.
+
+That combination is the expected intermediate state, not a contradiction and
+not a failed build. Confirm over plain HTTP, say the certificate is still
+issuing, and poll until HTTPS answers. Never delete and recreate the site or
+start debugging DNS on the strength of it.
+
+New sites come up on the host's default theme (`hello-elementor`). A fresh
+install is not evidence that a custom theme shipped.
+
 ## 0a. Tool map — reach for it when
 
 | Tool | Reach for it when |
@@ -100,7 +115,7 @@ proxy failures, resuming a connect, support report) ·
 | `awesomate_get_hosting_status` | Is hosting provisioned at all — eligible/provisioned flags, in-progress step, primary domain, DNS targets. Check before suggesting any site action |
 | `awesomate_get_hosting_account` | cPanel account details: package, server, provisioned-at, masked username |
 | `awesomate_list_sites` | What WordPress sites exist on this account |
-| `awesomate_site_create` | Spin up a new WordPress site (check limits first) |
+| `awesomate_site_create` | Spin up a new WordPress site (check limits first). Async — poll `awesomate_list_sites` for the name, and expect HTTPS to fail for a minute or two while AutoSSL issues; see **After creating a site** below |
 | `awesomate_list_domains` | What domains are attached, and to which site |
 | `awesomate_domain_add` | Attach a custom domain to a site |
 | `awesomate_dns_check` | Live answer to "where does this domain actually point" — before and after any DNS change |

package/skill/awesomate-hosting/references/rest-fallback.md

@@ -26,5 +26,50 @@ GET with `Authorization: Bearer <pat>`:
 | `awesomate_list_domains` | `GET {apiBase}/api/client-hosting/domains` |
 | `awesomate_get_limits` | `GET {apiBase}/api/client-hosting/limits` |
 
+## Creating a site over REST
+
+`POST {apiBase}/api/client-hosting/sites` (JSON, same bearer) is the fallback
+for `awesomate_site_create`. Three things about it trip people up:
+
+- **The body field is `siteTitle`, not `title`.** An unknown key is ignored
+  silently, so the site ends up titled after its domain. `domain`, `themeSlug`,
+  `adminEmail` and `intent` are the other accepted keys; all are optional.
+- **Omit `domain` and the server picks the next free `siteN.{primary}`** —
+  the first install takes the bare primary domain, then `site2`, `site3`, and
+  so on. Pass `domain` explicitly if the user named one.
+- **The response is bare `{"success":true}`** — no domain, no id. It does not
+  tell you what got built, so read the name back from `GET /sites`.
+
+Refusals are specific and worth relaying verbatim: `403` means the plan's site
+cap is reached (staging clones are excluded from the count), `409` means
+WordPress already exists at that domain.
+
+## Provisioning is async — do not call it broken
+
+The POST returns as soon as the install is queued. Poll
+`GET {apiBase}/api/client-hosting/sites` until the new hostname appears rather
+than assuming the call failed.
+
+Then expect a **gap of a minute or two where HTTPS does not answer at all**
+while AutoSSL issues the certificate. During that window the symptom looks
+alarming but is normal and self-resolving:
+
+| Check | During issuance | Meaning |
+|---|---|---|
+| `curl https://…` | `000` / connection failed | Cert not issued **yet** |
+| `curl http://…` | `200`, real WordPress HTML | The site is genuinely built |
+| `dig +short` | resolves to the hosting IP | DNS is fine |
+| `/sites` `sslActive` | may already say `true` | Reports intent, not the live cert |
+
+So: an HTTPS failure straight after creation is not a failed build. Confirm
+over plain HTTP, tell the user the certificate is still issuing, and poll
+HTTPS until it answers. Do not delete and recreate the site, and do not go
+hunting through DNS or Cloudflare — `sslActive: true` alongside a dead HTTPS
+port is the expected intermediate state, not a contradiction.
+
+New sites come up on the host's default theme (currently
+`hello-elementor`). If the user asked for a custom theme, that is still ahead
+of you — the fresh install is not evidence their theme shipped.
+
 Serve the request with these now, then suggest restarting Claude Code at a
 natural break so the richer MCP integration loads.