Block suites integration

MCP for Kadence Blocks

Kadence Blocks is a Gutenberg block library, and WP MCP's block tools are block-source-agnostic: list-block-types reads the whole block registry (so Kadence blocks appear alongside core), get-block-type returns any Kadence block's attributes, and add-block / update-block / insert-pattern edit them by markup at an index path. So Kadence is covered by the same free Gutenberg tools that handle core blocks, with no Kadence-specific integration to install. Every block edit is snapshotted first.

Get the free plugin Read the docs

list-block-typesget-block-typeadd-blockupdate-blockinsert-pattern

What your AI can do

Real Kadence Blocks operations, every write reversible.

Discover Kadence blocks through the block registry (list-block-types)
Read a Kadence block's attributes (get-block-type)
Insert and update Kadence blocks by markup at a precise path
Roll back any block edit, per change or per session

Example prompts

Just ask.

List the Kadence blocks available on this site.

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

Change the heading in the second Kadence block on the homepage.

Under the hood

The real calls.

wpmcp, kadence-blocks

list-block-types({ search: "kadence" }), surfaces kadence/* blocks

add-block({ id: 12, markup: "", path: [1] }), snapshotted

Frequently asked

Questions, answered.

Is there a Kadence-specific integration?

There does not need to be. Kadence Blocks registers standard Gutenberg blocks, and WP MCP's block tools operate on any registered block and on raw block markup, so Kadence is handled the same way as core blocks. That is verified by a regression test that drives a non-core block through list, inspect, and add.

More integrations