@awesomate/hosting-mcp 0.40.1 → 0.40.2

package/dist/index.js

@@ -41779,7 +41779,7 @@ 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. A fresh Elementor install can take ~90 s; if the call comes back as a Cloudflare 524 timeout, call it again: every step before the password is idempotent and the second call picks up where the first stopped.",
+    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. `serverUrl` uses /wp-json/ only when the server has just proved it routes, otherwise ?rest_route= (works under any permalinks); when it is the latter, `notes` says why, and on an /index.php/ site offer awesomate_wp_settings permalinks:'postname' (changes the site's public URLs, so ask first). 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. A fresh Elementor install can take ~90 s; if the call comes back as a Cloudflare 524 timeout, call it again: every step before the password is idempotent and the second call picks up where the first stopped.",
     inputSchema: {
       domain: external_exports.string().min(3).max(253).describe("The site domain, e.g. mybusiness.awesomate.site")
     }
@@ -42902,7 +42902,7 @@ server.registerTool(
   "awesomate_wp_settings",
   {
     annotations: annotate("awesomate_wp_settings", DESTRUCTIVE),
-    description: `Change a WordPress site's core settings \u2014 THE tool for "change my site title" / tagline. Use this, never awesomate_run_wp_cli, for any value containing spaces: that tool's argument gate rejects spaces outright, so \`option update blogname "My Business Name"\` cannot work there. Fields (send only what you're changing): title, tagline, timezone (IANA, e.g. Australia/Sydney), dateFormat, timeFormat, postsPerPage (1-100), searchEngineVisible (false hides the site from search engines \u2014 confirm before setting it). Support Plus+ and audited; flushes the object cache so the change shows. Snapshot first with awesomate_snapshot_site if this is the session's first change to a live site.`,
+    description: "Change a WordPress site's core settings: THE tool for \"change my site title\" / tagline. Use this, never awesomate_run_wp_cli, for any value containing spaces: that tool's argument gate rejects spaces outright, so `option update blogname \"My Business Name\"` cannot work there. Fields (send only what you're changing): title, tagline, timezone (IANA, e.g. Australia/Sydney), dateFormat, timeFormat, postsPerPage (1-100), searchEngineVisible (false hides the site from search engines; confirm before setting it), permalinks ('postname' gives /my-page/ links, 'plain' gives ?p=123; postname also writes the .htaccess rewrite rules and the server then checks that /wp-json/ answers, reported under `permalinks.routing`). Use permalinks:'postname' when a site's links contain /index.php/ or /wp-json/ 404s; old /index.php/ links keep working through WordPress's own redirect. Support Plus+ and audited; flushes the object cache so the change shows. 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"),
       title: external_exports.string().min(1).max(200).optional().describe("Site title (blogname)"),
@@ -42911,7 +42911,8 @@ server.registerTool(
       dateFormat: external_exports.string().max(40).optional(),
       timeFormat: external_exports.string().max(40).optional(),
       postsPerPage: external_exports.number().int().min(1).max(100).optional(),
-      searchEngineVisible: external_exports.boolean().optional()
+      searchEngineVisible: external_exports.boolean().optional(),
+      permalinks: external_exports.enum(["postname", "plain"]).optional().describe("Link structure: 'postname' (/my-page/) or 'plain' (?p=123)")
     }
   },
   async ({ domain, ...fields }) => {

package/package.json

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