Skip to content

Page builder integrations

EMCP 3.17.0 gives each supported builder its own integration, tool sections and authoring guidance. Use the native content format and schemas supplied by the builder installed on your site.

One standalone builder, independent Gutenberg packs

Section titled “One standalone builder, independent Gutenberg packs”

Open EMCP Tools > Page Builders and select one available standalone integration. Only one standalone integration can be selected at a time. This controls EMCP’s tools; it does not uninstall other plugins or convert their pages.

Gutenberg stays available alongside that selection. Spectra, Kadence Blocks, GenerateBlocks, Blocksy Blocks and Otter Blocks have independent toggles and can run together. Native dependencies still apply: Blocksy Blocks requires the Blocksy theme and Companion.

The catalog contains 12 standalone integrations, Gutenberg, and five block packs. Kirki here means the Kirki 6 visual builder. BeBuilder remains tied to the active BeTheme installation.

These are the adapter contracts for this release, not claims about the latest vendor versions. Editions and optional extensions can affect the available catalog.

IntegrationVersion or dependencyMain workflow
ElementorActive Elementor; premium features need Elementor ProContainers, widgets, templates and design settings
BricksActive Bricks 2.3.13 through 2.3.x; EMCP ProFlat trees, existing templates and design discovery
Breakdance2.8.3 through 2.8.x in Breakdance mode; EMCP ProNested native trees and responsive controls
AvadaActive Avada theme and Builder 3.16.1 through 3.16.x; EMCP ProNative shortcode trees and Core display elements
Divi 5Active Divi 5.13.x; EMCP ProPages, Theme Builder and supported Theme Options
Thrive ArchitectArchitect 11.0.x; EMCP ProNative HTML elements and page CSS
Oxygen 66.1.3 through 6.1.x in Oxygen mode; EMCP ProTemplates, components and design data
Kirki 66.3.1 through 6.3.x with visual builder; EMCP ProCanvas graphs and staged versions
WPBakery9.0.1 through 9.0.x; EMCP ProVerified shortcodes, CSS and snapshots
Beaver Builder2.11.1 through 2.11.x; tested with Pro 2.11.1; EMCP ProStaged layouts and detached templates
Visual ComposerWebsite Builder 45.16.2 through 45.16.x; EMCP ProPaired graph, HTML and CSS staging
BeTheme & BeBuilderActive BeTheme; EMCP ProSections, wraps, item schemas and curated theme options
PackEMCP editionScope
SpectraFreeDiscovery and mixed-page editing; no Astra requirement
Kadence BlocksFreeBlock editing and Design Library patterns
GenerateBlocksProV2 insertion with matching styles/CSS; verified on 2.4.0
Blocksy BlocksProNative blocks and embeds; Blocksy theme and Companion required
Otter BlocksProOtter 3.2.5 through 3.2.x; vendor Pro optional

EMCP’s license and vendor licenses are separate. A free EMCP adapter does not unlock premium patterns. An EMCP Pro adapter can support a vendor’s free plugin, as Otter does.

  1. Activate the supported native builder and required companions.
  2. Select the standalone integration or enable the independent pack.
  3. Open its Tools tab and enable the operations needed for the task. New write tools start disabled; existing saved choices are preserved.
  4. Reconnect the MCP client. Long-lived WP-CLI processes retain loaded PHP until restarted.
  5. Read context, element or block schemas and the current document. Load the bundled skill where available.
  6. Create a draft or edit reviewed content using its latest hash. Re-read after each mutation.
  7. Check the native editor and frontend at desktop and mobile widths before publication.

Beaver Builder, Kirki and Visual Composer expose staging and publication workflows. Gutenberg pack edits use ordinary content saves, which can affect a published page immediately. Other builders preserve status while changing native content. Read each adapter’s contract before editing a live page.

Native revisions and adapter recovery snapshots are separate from the History ledger. They do not imply universal transactions or automatic rollback.

Astra, Kadence and GeneratePress settings stay in Themes. Their block plugins have independent integration tabs. Blocksy settings stay in Themes, Companion features live in Plugins, and Gutenberg content is managed through Blocksy Blocks.

The Templates admin page follows its module state even when another builder is selected. Its current library remains Elementor-specific. Each builder’s native library tools are separate; templates are not automatically portable between builders.

Check installed versions, dependencies, integration selection, tool switches and native permissions. A discovered element is not necessarily writable: several adapters author a verified subset. Use returned scope and errors rather than forcing direct metadata changes. Reconnect after code or selection changes.