@awesomate/hosting-mcp 0.39.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",
@@ -41774,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",
   {

package/package.json

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