@diviops/mcp-server 0.2.3 → 0.2.5

package/README.md

@@ -91,9 +91,9 @@ The server connects via standard WordPress REST API and works with any environme
 
 > **WP-CLI note:** `WP_PATH` keeps the existing Local by Flywheel behavior by running `wp` directly on the host filesystem. For Docker-based environments (DDEV, wp-env, DevKinsta, WordPress Studio), set `WP_CLI_CMD` to the wrapper command instead. When `WP_CLI_CMD` is set, the server executes the wrapper from `WP_PATH` if provided, otherwise from its current working directory. The MCP server still validates the requested WP-CLI subcommand against its allowlist before executing either path.
 
-## Available Tools (46)
+## Available Tools (47)
 
-### Read (25)
+### Read (26)
 | Tool | Description |
 |------|-------------|
 | `diviops_test_connection` | Test WordPress connection and Divi version |
@@ -119,6 +119,7 @@ The server connects via standard WordPress REST API and works with any environme
 | `diviops_list_tb_templates` | List Theme Builder templates with conditions and layout IDs |
 | `diviops_get_tb_layout` | Get a Theme Builder layout's block markup (header/body/footer) |
 | `diviops_list_variables` | List design token variables (filter by type or prefix) |
+| `diviops_variables_scan_orphans` | Find `gvid-`/`gcid-` refs with no backing Variable Manager entry (orphans render as invalid CSS) + unused variables (defined, never referenced). Scans pages, Theme Builder layouts (header/body/footer), Divi Library items, canvas pages, and the preset registry |
 | `diviops_list_canvases` | List all canvas pages |
 | `diviops_get_canvas` | Get canvas content |
 
@@ -141,7 +142,7 @@ The server connects via standard WordPress REST API and works with any environme
 | `diviops_update_tb_layout` | Update a Theme Builder layout's block markup |
 | `diviops_create_tb_template` | Create Theme Builder template with header/footer and conditions |
 | `diviops_create_variable` | Create a design token variable |
-| `diviops_delete_variable` | Delete a variable by ID |
+| `diviops_delete_variable` | Delete a variable by ID. Returns HTTP 409 when live references exist unless `force=true` (use `diviops_variables_scan_orphans` to find reference locations). Returns HTTP 403 for Divi's customizer-bound defaults (`gcid-primary-color`, `gcid-secondary-color`, `gcid-heading-color`, `gcid-body-color`, `gcid-link-color` — managed via WP Customizer) |
 | `diviops_create_canvas` | Create a canvas page |
 | `diviops_update_canvas` | Update canvas content |
 | `diviops_delete_canvas` | Delete a canvas page |
@@ -237,6 +238,21 @@ The MCP server and WP plugin versions are incompatible. Update whichever side is
 curl -u "username:apppassword" http://site.local/wp-json/diviops/v1/settings
 ```
 
+### Preset edits not visible on the frontend
+
+After `preset_update` / `preset_create`, the preset option is updated immediately but Divi serves frontend CSS from a **per-post static cache** that neither `wp cache flush` nor `wp transient delete --all` invalidates.
+
+Cache location: `wp-content/et-cache/{post_id}/` — contains files like `et-divi-dynamic-tb-*-{post_id}-critical.css` with preset CSS baked in.
+
+To force regeneration for a specific page:
+```bash
+rm -rf wp-content/et-cache/{post_id}/
+```
+
+Next visit re-renders and writes fresh CSS. Applies to: any change that affects preset-derived CSS output (preset_update, preset_create when used by an existing page, preset_reassign in apply mode).
+
+The preset option (`et_divi_builder_global_presets_d5`) always reflects the current MCP-written state — if `wp option get et_divi_builder_global_presets_d5` shows your change but the frontend doesn't, it's this cache.
+
 ## License
 
 MIT

package/dist/index.js

@@ -620,14 +620,14 @@ server.registerTool("diviops_preset_cleanup", {
     };
 });
 server.registerTool("diviops_preset_update", {
-    description: "Update a specific preset by ID. Can rename and/or replace its style attributes.",
+    description: "Update a specific preset by ID. Can rename and/or replace its style attributes. Note: Divi serves frontend CSS from a per-post static cache at wp-content/et-cache/{post_id}/ that wp cache flush does NOT invalidate — if you're verifying a preset change on the rendered frontend, delete that dir for affected pages to force regeneration. Server-side preset state updates immediately; only the pre-rendered CSS file is stale.",
     inputSchema: {
         preset_id: z.string().describe("Preset ID (UUID or short ID)"),
         name: z.string().optional().describe("New display name for the preset"),
         attrs: z
             .record(z.string(), z.any())
             .optional()
-            .describe("New style attributes (replaces both attrs and styleAttrs)"),
+            .describe("New style attributes (replaces attrs, styleAttrs, and renderAttrs — matches VB save semantics so render cache stays in sync with edit state)"),
     },
 }, async ({ preset_id, name, attrs }) => {
     const body = { preset_id };
@@ -1316,16 +1316,21 @@ server.registerTool("diviops_create_variable", {
     };
 });
 server.registerTool("diviops_delete_variable", {
-    description: "Delete a design token variable by ID. Auto-detects storage from ID prefix (gcid-* = colors, gvid-* = numbers/strings/etc).",
+    description: "Delete a design token variable by ID. Auto-detects storage from ID prefix (gcid-* = colors, gvid-* = numbers/strings/etc). Returns HTTP 409 when live references exist unless force=true — run diviops_variables_scan_orphans to see where the references live. Returns HTTP 403 for Divi's customizer-bound defaults (gcid-primary-color, gcid-secondary-color, gcid-heading-color, gcid-body-color, gcid-link-color); those are managed via WP Customizer theme options and can't be deleted via this tool.",
     inputSchema: {
         id: z
             .string()
             .describe('Variable ID to delete (e.g. "gcid-oa-accent" or "gvid-oa-size-xl")'),
+        force: z
+            .boolean()
+            .optional()
+            .default(false)
+            .describe("Delete even if live references exist. Orphans will remain in page/preset content and render as invalid CSS on the frontend — run diviops_variables_scan_orphans afterwards to audit."),
     },
-}, async ({ id }) => {
+}, async ({ id, force }) => {
     const result = await wp.request("/variable/delete", {
         method: "POST",
-        body: { id },
+        body: { id, force },
     });
     return {
         content: [
@@ -1333,6 +1338,16 @@ server.registerTool("diviops_delete_variable", {
         ],
     };
 });
+server.registerTool("diviops_variables_scan_orphans", {
+    description: "Scan pages, Theme Builder layouts (header/body/footer), Divi Library items, canvas pages, and the preset registry for gvid-/gcid- references that have no backing entry in the Variable Manager (orphans), plus variables defined but referenced nowhere (unused). Orphans render as invalid CSS on the frontend — the $variable()$ resolver falls through with no fallback. Use after a deletion with force=true, or periodically as a hygiene check. Symmetric to diviops_preset_scan_orphans.",
+}, async () => {
+    const result = await wp.request("/variables-scan-orphans");
+    return {
+        content: [
+            { type: "text", text: JSON.stringify(result, null, 2) },
+        ],
+    };
+});
 // ── Start ────────────────────────────────────────────────────────────
 async function main() {
     // Version handshake — verify plugin compatibility before accepting tool calls.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@diviops/mcp-server",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "description": "MCP server exposing Divi 5 Visual Builder as tools for Claude",
   "type": "module",
   "main": "dist/index.js",