@diviops/mcp-server 1.0.0 → 1.1.0

package/README.md

@@ -96,7 +96,7 @@ 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 (63)
+## Available Tools (65)
 
 ### Read (30)
 | Tool | Description |
@@ -132,11 +132,13 @@ The server connects via standard WordPress REST API and works with any environme
 | `diviops_scf_field_group_list` | List all SCF/ACF field groups (post_name = ACF key, post_title, post_status, post_modified). Queries the `acf-field-group` post type via `wp post list` (works on SCF 6.8.4+ and older ACF) |
 | `diviops_scf_field_group_get` | Fetch a single SCF/ACF field-group post by ACF key (`group_abc123` → post_name) or numeric WP post ID. For the parsed/structured field tree, use `diviops_scf_export --field-groups=<key> --stdout` |
 
-### Write (31)
+### Write (33)
 | Tool | Description |
 |------|-------------|
 | `diviops_page_create` | Create a new page with optional Divi content |
 | `diviops_page_update_content` | Full page content rewrite |
+| `diviops_page_trash` | Trash (default) or permanently delete (`force=true`) a page. Idempotent on already-trashed posts. Supports `dry_run` |
+| `diviops_page_update_status` | Update post_status (publish/draft/private/pending/future). `future` requires `date_gmt` (ISO 8601 UTC); `publish` clears stale future dates so re-publishing takes effect immediately. Supports `dry_run` |
 | `diviops_section_append` | Append a section to existing page (start or end) |
 | `diviops_section_replace` | Replace a section by admin label |
 | `diviops_section_remove` | Remove a section by admin label |

package/dist/compatibility.d.ts

@@ -2,7 +2,7 @@
  * Version compatibility between MCP server and WP plugin.
  */
 /** Minimum WP plugin version this server requires. */
-export declare const MIN_PLUGIN_VERSION = "1.0.0";
+export declare const MIN_PLUGIN_VERSION = "1.1.0";
 /**
  * Compare two semver-like version strings (supports pre-release tags).
  *

package/dist/compatibility.js

@@ -2,7 +2,7 @@
  * Version compatibility between MCP server and WP plugin.
  */
 /** Minimum WP plugin version this server requires. */
-export const MIN_PLUGIN_VERSION = '1.0.0';
+export const MIN_PLUGIN_VERSION = '1.1.0';
 /**
  * Compare two semver-like version strings (supports pre-release tags).
  *

package/dist/index.js

@@ -744,6 +744,69 @@ server.registerTool("diviops_page_create", {
         ],
     };
 });
+server.registerTool("diviops_page_trash", {
+    description: "Trash or permanently delete a page/post. Defaults to trash (reversible via WP Admin → Trash). Pass force=true to permanently delete (wp_delete_post — irreversible). Idempotent: trashing an already-trashed post is a no-op. Pass dry_run=true to preview without mutating. Replaces wp-cli `post delete --force=0|1` routing for AI-agent callers (typed input, deterministic envelope).",
+    inputSchema: {
+        post_id: z.number().int().describe("WordPress post/page ID"),
+        force: z
+            .boolean()
+            .optional()
+            .default(false)
+            .describe("When true, permanently delete (skips trash). Default false moves to trash."),
+        dry_run: z
+            .boolean()
+            .optional()
+            .default(false)
+            .describe("When true, return the change plan without mutating state."),
+    },
+}, async ({ post_id, force, dry_run }) => {
+    const result = await wp.request(`/page/trash/${post_id}`, {
+        method: "POST",
+        body: {
+            force: force ?? false,
+            dry_run: dry_run ?? false,
+        },
+    });
+    return {
+        content: [
+            { type: "text", text: JSON.stringify(result) },
+        ],
+    };
+});
+server.registerTool("diviops_page_update_status", {
+    description: "Update a page's post_status. Valid statuses: publish, draft, private, pending, future. status='future' requires date_gmt (ISO 8601 UTC, must be in the future) — server writes both post_date_gmt and the site-tz post_date so WP's scheduler picks it up. status='publish' on a previously-scheduled post clears the future date so it publishes immediately. Idempotent: same-status update is a no-op. Pass dry_run=true to preview. Replaces wp-cli `post update --post_status=...` routing.",
+    inputSchema: {
+        post_id: z.number().int().describe("WordPress post/page ID"),
+        status: z
+            .enum(["publish", "draft", "private", "pending", "future"])
+            .describe("Target post status"),
+        date_gmt: z
+            .string()
+            .optional()
+            .describe("Required when status='future'. ISO 8601 UTC datetime (e.g. '2026-06-01T09:00:00Z'). Must be in the future."),
+        dry_run: z
+            .boolean()
+            .optional()
+            .default(false)
+            .describe("When true, return the change plan without mutating state."),
+    },
+}, async ({ post_id, status, date_gmt, dry_run }) => {
+    const body = {
+        status,
+        dry_run: dry_run ?? false,
+    };
+    if (date_gmt)
+        body.date_gmt = date_gmt;
+    const result = await wp.request(`/page/update-status/${post_id}`, {
+        method: "POST",
+        body,
+    });
+    return {
+        content: [
+            { type: "text", text: JSON.stringify(result) },
+        ],
+    };
+});
 // ── Preset Tools ────────────────────────────────────────────────────
 server.registerTool("diviops_preset_audit", {
     description: "Audit all Divi presets (module + group). Each entry reports `block_ref_count` (page-content refs via modulePreset / groupPreset block markup), `group_ref_count` (in-registry chain refs from other presets — module presets via top-level `groupPresets.<slot>.presetId`, group presets via `attrs.groupPreset.<slot>.presetId`), and `referenced` (true if either > 0). Group presets that are chain-referenced also expose `referenced_by_presets` (UUIDs of the presets that wire them in — typically module presets, but type-agnostic). Use this before deleting — orphan-cleanup based only on page refs would silently wipe load-bearing chain-wired group presets (font, border, box-shadow, spacing, button). Also reports `orphan_default_pointers`: per-bucket `default` pointers that reference a UUID no longer present in `items[]` (caused by past unsafe deletes). Render-safe but blocks Divi's lazy recreate-on-VB-use path; clear via diviops_preset_set_default with unset=true on the affected module/group.",

package/package.json

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