@diviops/mcp-server 0.2.2 → 0.2.4

package/README.md

@@ -17,7 +17,7 @@ Claude Code <-> MCP Server (stdio) <-> WordPress REST API <-> Divi MCP Plugin
 
 ### 1. Install the WordPress Plugin
 
-Download and activate the **DiviOps Agent** plugin from the [releases page](https://github.com/oaris-dev/diviops-internal/releases).
+Download and activate the **DiviOps Agent** plugin — [direct zip](https://github.com/oaris-dev/diviops/raw/main/diviops-agent.zip) or browse the [public distribution repo](https://github.com/oaris-dev/diviops).
 
 ### 2. Create an Application Password
 
@@ -237,6 +237,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 };

package/package.json

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