Get the plugin
WP MCP/Integrations/Block suites

Block suites integration

Kadence Blocks AI agent tool reference

Kadence Blocks is a Gutenberg block library whose blocks carry a uniqueID that its CSS is keyed by. WP MCP Pro adds a dedicated block suite pair, block-suites-read and block-suites-write, that knows this: get-block-schemas returns each kadence/* block's registered attributes, and insert-block and update-block check every attribute against that schema before any snapshot, refusing unknown attributes, wrong types and enum misses. Each block gets a unique id in the shape Kadence's editor generates, with the old id rewritten inside the block's own markup so its styles still match. list-patterns and import-pattern browse registered patterns by the suites they use and insert one in a single undoable write, bringing its remote images into the Media Library first. Every block write goes through the surgical block engine with an expected_hash freshness check and one post snapshot per call. The same pair also reads and writes the plugin's own settings: get-settings returns the four JSON stores Kadence Blocks keeps (global settings, the color palette, per block visibility and per block defaults), and update-settings merges keys into one or more of them, with null removing a key, the way its settings screen saves them. A store that holds something Kadence cannot decode is never overwritten, values containing markup are refused, and the options a batch touches are snapshotted as one undo point. API keys and secrets live in options of their own that these ops never read. get-page-styles explains that Kadence builds block CSS while the page renders and stores none per post, and lists the uniqueIDs the post's CSS is keyed on.

block-suites-readblock-suites-writelist-block-typesadd-blockupdate-block

In practice

How Kadence Blocks work goes with an agent.

Every Kadence block carries a uniqueID, and Kadence builds each block's CSS from its attributes while the page renders, keyed on that id. The failure an outside writer meets is not a stale cache but a bad id: a pasted block with a missing, duplicated or foreign id loses its styles. Kadence ids also have a post-scoped shape, with the post id as a prefix. WP MCP Pro generates ids in that form, replaces the old id inside the block's own markup, and validates every attribute against the registered schema first.

What attributes does the Kadence advanced heading take?

Runs block-suites-read with get-block-schemas for the kadence-blocks suite and the block name. It returns the full registered attribute definitions, type, default and enum, from block.json. Read only.

Add a three-column row layout with an info box in each column on /services.

Runs block-suites-write insert-block with the nested markup. Each Kadence block gets a unique id, such as 12_a1b2c3-d4, and the __UNIQUE_ID__ placeholder is replaced inside its markup. The post is snapshotted, with one snapshot for the whole subtree.

Set the info box padding to 40 pixels and rename its title.

Runs update-block with attrs and inner_html. Attributes merge into the block's existing ones, a null value removes one, and the uniqueID cannot be changed. An unknown attribute or wrong type is refused before any snapshot.

Browse Kadence patterns for testimonials and import one above the footer.

Runs list-patterns filtered to the kadence-blocks suite, then import-pattern at a path. Ids in the pattern are made unique within the post, and its remote images are sideloaded into the Media Library first.

What your AI can do

Real Kadence Blocks operations, every write reversible.

  • List the active block suites and read each Kadence block's attribute schema
  • Insert and update Kadence blocks with every attribute validated first
  • Give each block a correct, unique uniqueID so its generated CSS applies
  • Browse registered patterns by suite and import one as a single undoable write
  • Import patterns from the WordPress.org Pattern Directory, on request only
  • Read Kadence Blocks settings, palette, block visibility and block defaults, secrets left out
  • Change those settings in one validated, snapshotted batch (opt-in)
  • List the uniqueIDs a post's Kadence CSS is keyed on
  • Roll back any block or settings write exactly, per change or per session

Example prompts

Example Kadence Blocks prompts.

List the Kadence blocks on this site and the attributes the row layout takes.

Add a Kadence row layout with three info boxes under the hero on /services.

Show me the Kadence Blocks global settings and turn on the performance optimizer.

Under the hood

The Kadence Blocks calls, under the hood.

wpmcp, kadence-blocks

block-suites-read({ operation: "get-block-schemas", args: { suite: "kadence-blocks" } }), registered attributes per block

block-suites-write({ operation: "insert-block", args: { suite: "kadence-blocks", id: 12, expected_hash, path: [1], markup: "<!-- wp:kadence/rowlayout ... -->" } }), schema-checked, unique ids, snapshotted

block-suites-read({ operation: "get-settings", args: { suite: "kadence-blocks" } }), four stores; API keys never read

block-suites-write({ operation: "update-settings", args: { suite: "kadence-blocks", settings: { settings: { performance_optimizer_enabled: true } } } }), opt-in; merged; one undo point

Safety and access

What can be undone on Kadence Blocks, and what costs what.

Recoverable on Kadence Blocks

  • insert-block, update-block and import-pattern each take one snapshot of the whole post.
  • rollback-operation restores the exact previous content, per change or for the whole session.
  • There is no stylesheet to rebuild after a rollback, because Kadence generates its CSS at render time.

Kadence Blocks limits and opt-ins

  • Unknown attributes, wrong types and values outside an enum are refused, so the agent must use the names in get-block-schemas.
  • A block's uniqueID cannot be changed by update-block, because its CSS is keyed on it.
  • Images sideloaded for an imported pattern stay in the Media Library after a rollback.
  • Kadence's own cloud pattern library is not used, because it sends the site's license key and email. Patterns come from the registry or, on request, the WordPress.org Pattern Directory, which has core blocks only.

Free or Pro: The dedicated Kadence Blocks support is part of WP MCP Pro. It is the block-suites-read and block-suites-write pair, and it appears while Kadence Blocks or another supported suite is active. The free plugin edits Kadence blocks only as raw markup through the Gutenberg tools, without schema checks or Kadence-style ids. It does not need a Kadence license either way.

Part of WP MCP Pro

The Kadence Blocks integration is part of WP MCP Pro.

One Pro licence unlocks the Kadence Blocks tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.

Frequently asked

Kadence Blocks MCP: questions, answered.

Is there a free way to edit Kadence blocks?

Yes. The free Gutenberg tools (list-block-types, get-block-type, add-block, update-block) work on any registered block, Kadence's included, by raw markup. The Pro block suite pair adds schema validation, correct unique ids, settings and pattern import on top.

When do the pattern tools appear?

list-patterns and import-pattern live on the block suite pair, which registers only while at least one supported suite (Kadence Blocks, GenerateBlocks, Spectra, Otter Blocks or the Blocksy companion) is active. The WordPress.org Pattern Directory is contacted only when you ask for source "directory".

Which Kadence Blocks settings can the agent change?

The four stores get-settings returns: settings, colors, block_visibility and block_defaults. Keys are merged into the stored object and null removes one. Writes are off until the site turns on the wpmcp_enable_block_suite_settings_write filter and need manage_options. API keys such as reCAPTCHA or mail keys are kept in other options, which these ops never read or write.

Is there a Kadence Blocks page stylesheet to rebuild after a Kadence edit?

No. Kadence builds each block's CSS from its attributes while the page renders, so a block write shows on the next view. rebuild-page-styles refuses for Kadence with no_page_style_cache for that reason.

What does a Kadence unique id look like?

It is the post id, an underscore, and nine characters taken from a UUID (one of them a hyphen), for example 12_a1b2c3-d4. WP MCP keeps an existing id when it is well formed, unused in the post and scoped to this post, and replaces it otherwise. An id copied from another post is re-scoped to this one.

What is the __UNIQUE_ID__ placeholder?

It lets an agent write a block before it knows its id. Put __UNIQUE_ID__ in the attribute and in the markup, and WP MCP swaps in a generated id in both places. list-suites also reports the placeholder and the id attribute name for each suite, so an agent can check it.

Does the Kadence Blocks integration work with Kadence Pro or the Kadence theme?

The block pair works with Kadence Blocks alone. It does not need the Kadence theme or Kadence Pro. Theme palette and header settings are a free separate integration, and Kadence Pro Elements is a Pro one, so an agent can use whichever parts the site has.

Point your AI at Kadence Blocks.