@awesomate/hosting-mcp 0.38.0 → 0.40.0

package/dist/index.js

@@ -41138,6 +41138,7 @@ var TITLES = {
   awesomate_wp_post: "Manage WordPress posts",
   awesomate_wp_media_import: "Import media to WordPress",
   awesomate_wp_settings: "Change WordPress settings",
+  awesomate_elementor_mcp_connect: "Connect Elementor MCP",
   awesomate_app_create: "Create app",
   awesomate_app_get: "Get app details",
   awesomate_app_scaffold: "Get app scaffold guide",
@@ -41179,7 +41180,9 @@ var TITLES = {
   awesomate_knowledge_collections: "Manage knowledge collections",
   awesomate_knowledge_faq: "Manage FAQs",
   awesomate_knowledge_people: "Manage knowledge entities",
-  awesomate_knowledge_data: "Query knowledge data warehouse"
+  awesomate_knowledge_data: "Query knowledge data warehouse",
+  awesomate_crm_metrics: "List contact list metrics",
+  awesomate_crm_query: "Query contact list metrics"
 };
 function annotate(name, kind) {
   const title = TITLES[name];
@@ -41772,6 +41775,23 @@ server.registerTool(
     }
   }
 );
+server.registerTool(
+  "awesomate_elementor_mcp_connect",
+  {
+    annotations: annotate("awesomate_elementor_mcp_connect", DESTRUCTIVE),
+    description: "Connect this Claude Code to Elementor's OWN MCP server on one of the user's WordPress sites, so pages can be built as native, editable Elementor structure instead of raw HTML. Use it when a site uses Elementor (hello-elementor theme or the elementor plugin) and the user wants pages built or edited. One call does what the Elementor > Elementor MCP page does: installs or updates Elementor to 4.3+, turns on the Editor V4 (Atomic) experiments, enables MCP access, and mints a WordPress application password for the user's own administrator. The response carries `claudeCodeCommand` (a `claude mcp add --transport http \u2026` line) and `mcpServersConfig` (the mcp-remote JSON shape): run the command for the user, or write the config, then tell them to restart Claude Code; the Elementor tools then appear as a separate MCP server. The application password is shown ONCE and Awesomate does not keep it: never paste it into chat or a file other than the MCP config, and tell the user it is revocable under Users > Profile > Application Passwords. Support Plus+ (403 upgrade_required on Essentials: an Essentials owner does the same in wp-admin under Elementor > Elementor MCP). The Elementor MCP builds Editor V4 Atomic pages only, and Pro elements need an Elementor Pro plan on the site. Snapshot first with awesomate_snapshot_site if this is the session's first change to a live site.",
+    inputSchema: {
+      domain: external_exports.string().min(3).max(253).describe("The site domain, e.g. mybusiness.awesomate.site")
+    }
+  },
+  async ({ domain }) => {
+    try {
+      return textResult(await hubPost(requireConfig(), `/api/client-hosting/sites/${encodeURIComponent(domain.toLowerCase())}/elementor-mcp`, {}));
+    } catch (err) {
+      return errorResult(err);
+    }
+  }
+);
 server.registerTool(
   "awesomate_uninstall_site",
   {
@@ -42629,6 +42649,59 @@ server.registerTool(
     }
   }
 );
+server.registerTool(
+  "awesomate_crm_metrics",
+  {
+    annotations: annotate("awesomate_crm_metrics", READ_ONLY),
+    description: "What the client's own contact list (Contacts & email in the hub) can answer with numbers. action 'metrics' \u2014 the measures: people (a count) plus every number field the owner has named, with unit and synonyms. 'datasets' \u2014 the one dataset, 'contact', with its columns by kind: measures, dimensions (choice, yes/no and text fields to group by) and anchors (date fields a person can be counted by, plus created_at). Read this FIRST; awesomate_crm_query only accepts names listed here. Sensitive fields never appear. Read-only; counts and sums only, never a person's details.",
+    inputSchema: { action: external_exports.enum(["metrics", "datasets"]) }
+  },
+  async ({ action }) => {
+    try {
+      return textResult(await hubGet(requireConfig(), `/api/my-crm/v1/data/${action}`));
+    } catch (err) {
+      return errorResult(err);
+    }
+  }
+);
+server.registerTool(
+  "awesomate_crm_query",
+  {
+    annotations: annotate("awesomate_crm_query", READ_ONLY),
+    description: "Numbers from the client's contact list, read-only, never a row of personal details. action 'series' {metric, grain?, from?, to?, range?, compare?, anchor?, tz?} \u2014 one metric over time (people added per month, spend per quarter), with labels, points and a previous-period comparison when compare='previous'. action 'query' {measures:[{column, agg}], dimensions?, filters?, time?, order_by?, limit?} \u2014 grouped numbers (people by plan, sum of spend by suburb). Column names MUST come from awesomate_crm_metrics 'datasets'; an unknown name is refused, never guessed. Dates are YYYY-MM-DD; range presets: 7d, 30d, 90d, 12m, mtd, qtd, ytd, fytd, this_month, last_month, this_fy, last_fy (financial year starts 1 July). The response's applied.defaults says what was assumed; repeat those to the user.",
+    inputSchema: {
+      action: external_exports.enum(["series", "query"]),
+      metric: external_exports.string().max(80).optional().describe("series: 'people' or a measure key"),
+      agg: external_exports.enum(["sum", "avg", "min", "max", "count"]).optional().describe("series: how to aggregate a measure (default sum)"),
+      grain: external_exports.enum(["day", "week", "month", "quarter", "year", "fy"]).optional(),
+      from: external_exports.string().max(10).optional(),
+      to: external_exports.string().max(10).optional(),
+      range: external_exports.string().max(20).optional().describe("a preset instead of from/to"),
+      compare: external_exports.enum(["previous"]).optional(),
+      anchor: external_exports.string().max(80).optional().describe("the date a person counts by: created_at or a date field key"),
+      tz: external_exports.string().max(64).optional().describe("IANA time zone; default Australia/Sydney"),
+      measures: external_exports.array(external_exports.object({ column: external_exports.string().max(80), agg: external_exports.string().max(10).optional() })).max(8).optional(),
+      dimensions: external_exports.array(external_exports.string().max(80)).max(6).optional(),
+      filters: external_exports.array(external_exports.object({ column: external_exports.string().max(80), op: external_exports.string().max(5).optional(), value: external_exports.unknown() })).max(10).optional(),
+      time: external_exports.object({ grain: external_exports.string().max(10).optional(), preset: external_exports.string().max(20).optional(), from: external_exports.string().max(10).optional(), to: external_exports.string().max(10).optional(), anchor: external_exports.string().max(80).optional(), tz: external_exports.string().max(64).optional() }).optional(),
+      order_by: external_exports.array(external_exports.object({ field: external_exports.string().max(80), dir: external_exports.enum(["asc", "desc"]).optional() })).max(4).optional(),
+      limit: external_exports.number().int().min(1).max(2e3).optional()
+    }
+  },
+  async ({ action, metric, agg, grain, from, to, range, compare, anchor, tz, measures, dimensions, filters, time: time3, order_by, limit }) => {
+    try {
+      const cfg = requireConfig();
+      if (action === "series") {
+        const qs = new URLSearchParams();
+        for (const [k, v] of Object.entries({ metric, agg, grain, from, to, range, compare, anchor, tz })) if (v) qs.set(k, String(v));
+        return textResult(await hubGet(cfg, `/api/my-crm/v1/data/series?${qs}`));
+      }
+      return textResult(await hubPost(cfg, "/api/my-crm/v1/data/query", { measures, dimensions, filters, time: time3, order_by, limit }));
+    } catch (err) {
+      return errorResult(err);
+    }
+  }
+);
 server.registerTool(
   "awesomate_n8n_kpis",
   {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.38.0",
+  "version": "0.40.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.39.0",
+      "highlights": [
+        "Ask Claude for numbers from your contact list: how many people joined each month, spend by plan, customers by suburb (awesomate_crm_metrics, awesomate_crm_query). It only ever gets counts and sums, never anyone's details",
+        "The fields you named on an import are what it can measure and group by; anything you marked sensitive is left out entirely",
+        "Every answer says what it assumed (the date range, the time zone, which date a person counts by) so you can check it"
+      ]
+    },
     {
       "version": "0.38.0",
       "highlights": [

package/skill/awesomate-hosting/SKILL.md

@@ -104,8 +104,41 @@ 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.
+New sites on Support Plus, Pro and Embedded come up with free Elementor and
+the Hello Elementor theme (plus Jetpack, Yoast, Site Kit, Contact Form 7,
+WP Super Cache and Limit Login Attempts); an Essentials account installs
+WordPress from the hub's Install WordPress card, which adds the same
+Elementor and theme. A fresh install is not evidence that a custom theme
+shipped.
+
+## Elementor sites: connect Elementor's own MCP
+
+Elementor 4.3+ ships its own MCP server, served from the site itself. When a
+site uses Elementor (the `hello-elementor` theme or the `elementor` plugin
+is active) and the user wants pages built or changed, connect it BEFORE
+hand-writing page HTML: pages then land as native, editable Elementor
+structure the owner can keep working on in the Elementor editor.
+
+1. Snapshot the site if this is the session's first change to it.
+2. Call `awesomate_elementor_mcp_connect` with the domain (Support Plus+).
+   It installs or updates Elementor, turns on the Editor V4 experiments,
+   enables MCP access and mints a WordPress application password for the
+   user's own administrator.
+3. Run the returned `claudeCodeCommand` for the user (it is a
+   `claude mcp add --transport http …` line), or write `mcpServersConfig`
+   into the project's `.mcp.json` if they prefer. Then ask them to restart
+   Claude Code; the Elementor tools appear as their own MCP server.
+4. Say plainly where the key lives and how to revoke it: Users > Profile >
+   Application Passwords in wp-admin, or Elementor > Elementor MCP > Turn
+   off MCP access for the whole thing. Never repeat the password in chat.
+
+What to expect once connected: it builds **Editor V4 (Atomic) pages and
+layouts only**. Classic Elementor pages (most migrated sites) stay editable
+in the Elementor editor but not through the MCP. Forms, popups, loops,
+headers and footers need an Elementor Pro plan on that site; the hub does
+not supply one. On Essentials the tool returns 403 `upgrade_required`; the
+owner can do the identical thing in wp-admin under Elementor > Elementor
+MCP, so say that rather than stopping.
 
 ## 0a. Tool map — reach for it when
 
@@ -130,6 +163,7 @@ install is not evidence that a custom theme shipped.
 | `awesomate_site_staging_create` / `_promote` / `_discard` | Private full copy on awesomate.dev to review changes; publish or throw away (§5a) |
 | `awesomate_run_wp_cli` | The 10 allowlisted WP-CLI verbs only (see below) — plugin/theme list, activate, install-by-slug, update; `cache flush`; `option get`; `post`/`media`/`menu`/`comment`/`user list` |
 | `awesomate_wp_settings` | Site title, tagline, timezone, date/time format, posts-per-page, search-engine visibility — THE path for any multi-word value, and it flushes the cache (Support Plus+) |
+| `awesomate_elementor_mcp_connect` | A site uses Elementor and pages need building or editing: connects this Claude Code to Elementor's own MCP server on that site (see **Elementor sites** above). Mints an application password; Support Plus+ |
 | `awesomate_wp_post` | Create/update/read a WP post or page — drafts by default (writes are Support Plus+) |
 | `awesomate_wp_media_import` | Pull an image/file into the WP media library from an https URL (Support Plus+) |
 | `awesomate_uninstall_site` | Remove a WordPress install (destructive — confirm explicitly) |
@@ -205,7 +239,7 @@ Support Plus/Pro unlocks (§4), and link the hub billing page.
 On Essentials, a PAT is read-and-advise: `awesomate_site_create`,
 `awesomate_domain_add` and every WordPress write (`awesomate_wp_post`,
 `awesomate_wp_media_import`, `awesomate_wp_settings`,
-`awesomate_run_wp_cli`) return **403 `upgrade_required`** — the server
+`awesomate_run_wp_cli`, `awesomate_elementor_mcp_connect`) return **403 `upgrade_required`** — the server
 enforces it, so no phrasing gets past it. That site and that domain are
 real; they are created and changed **in the hub UI at
 hub.awesomate.ai/sites**, by the user, with deliberate clicks. Say exactly

package/skill/awesomate-n8n/references/n8n-agents.md

@@ -27,13 +27,18 @@ tool call at a time, so the key never reaches this machine.
 
 `awesomate_n8n_agents {action:"status"}` FIRST:
 
-- `keyConfigured: false` → walk them through `setup.steps` in plain words:
-  in their n8n, **Settings → Instance-level MCP** → switch on → copy the MCP
-  API key → paste it into **n8n Agents access** at
-  hub.awesomate.ai/n8n/settings → Test & Save. Owner or admin only. Then
-  re-check status. Never ask them to paste the key into this chat.
-- `code: mcp_disabled` → MCP was switched off again in their n8n.
-- `code: mcp_key_rejected` → the key was rotated; paste a fresh one.
+- `keyConfigured: false` → send them to **"Set it up for me"** under **n8n
+  Agents access** at hub.awesomate.ai/n8n/settings (`setup.steps`). One
+  click: the hub switches on their n8n's MCP (a restart of about 20 seconds
+  if it was off), connects their owner key and emails them. There is nothing
+  to copy. **You cannot do this step for them**: only that click may connect
+  a key, so never offer to. When they say it's done, re-check status. If the
+  button can't do it on their instance, its message gives the by-hand route
+  (`setup.manualSteps`). Never ask them to paste a key into this chat.
+- `code: mcp_disabled` → MCP was switched off in their n8n. "Set it up for
+  me" switches it back on.
+- `code: mcp_key_rejected` → the hub normally re-reads a regenerated key by
+  itself. If this still shows, send them to "Set it up for me" again.
 - `missingTools` present → their n8n has no Agents module. Do not try to
   work around it; that's an Awesomate support ask.
 - `ready: true` → go. Building, testing and publishing agents work on **every