@diviops/mcp-server 1.5.11 → 1.5.12

package/dist/preset-cli/write-path.d.ts

@@ -18,6 +18,7 @@ import { WPClient } from "../wp-client.js";
 import type { HandshakeResult } from "../compatibility.js";
 import type { DiviopsResponse } from "../envelope.js";
 import type { ButtonPresetEntry } from "./button-emitter.js";
+import type { HeadingFontPresetEntry } from "./heading-font-emitter.js";
 /** The plugin capability the storage-path capability contract ships. */
 export declare const STORAGE_CAPABILITY = "storage_multipath_probe_v1";
 /** The REST route the CLI posts to — same route `diviops_preset_create` uses. */
@@ -57,3 +58,17 @@ export declare function applyButtonPreset(client: PresetWriteClient, entry: Butt
     serverVersion: string;
     dry_run?: boolean;
 }): Promise<DiviopsResponse<unknown>>;
+/**
+ * Apply a `divi/font` heading group preset: capability-gate, then POST
+ * to `/preset/create`. Mirrors `applyButtonPreset`'s sequence — the
+ * capability check runs BEFORE the write, and the write reuses the
+ * existing storage-routed route (no plugin route is added).
+ *
+ * The `pattern_variant` metadata is intentionally NOT in the wire body —
+ * variant selection is a client-side registry-gate decision and the
+ * server route accepts only the standard preset-create fields.
+ */
+export declare function applyHeadingFontPreset(client: PresetWriteClient, entry: HeadingFontPresetEntry, opts: {
+    serverVersion: string;
+    dry_run?: boolean;
+}): Promise<DiviopsResponse<unknown>>;

package/dist/preset-cli/write-path.js

@@ -16,6 +16,7 @@
  */
 import { WPClient } from "../wp-client.js";
 import { buildPresetCreateBody } from "./button-emitter.js";
+import { buildHeadingFontPresetCreateBody } from "./heading-font-emitter.js";
 /** The plugin capability the storage-path capability contract ships. */
 export const STORAGE_CAPABILITY = "storage_multipath_probe_v1";
 /** The REST route the CLI posts to — same route `diviops_preset_create` uses. */
@@ -87,3 +88,23 @@ export async function applyButtonPreset(client, entry, opts) {
         body,
     });
 }
+/**
+ * Apply a `divi/font` heading group preset: capability-gate, then POST
+ * to `/preset/create`. Mirrors `applyButtonPreset`'s sequence — the
+ * capability check runs BEFORE the write, and the write reuses the
+ * existing storage-routed route (no plugin route is added).
+ *
+ * The `pattern_variant` metadata is intentionally NOT in the wire body —
+ * variant selection is a client-side registry-gate decision and the
+ * server route accepts only the standard preset-create fields.
+ */
+export async function applyHeadingFontPreset(client, entry, opts) {
+    await assertStorageCapability(client, opts.serverVersion);
+    const body = buildHeadingFontPresetCreateBody(entry, {
+        dry_run: opts.dry_run,
+    });
+    return client.requestEnveloped(PRESET_CREATE_ROUTE, {
+        method: "POST",
+        body,
+    });
+}

package/package.json

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