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. The screen has two numbered parts:
- 1. Standalone builder is a set of radio cards, one per integration. Each card carries a status: Active (the saved choice), Detected (installed and supported, not selected) or Not detected. A Not detected card cannot be picked and lists what it needs; the server also refuses an undetected builder. Pick one card, or choose Use Gutenberg only for no standalone builder. The Show detected only toggle hides the cards you cannot use.
- 2. Gutenberg block plugins has one switch per block pack. Switch on any combination.
Changes collect in the save bar at the bottom of the screen: choose Save changes, then reconnect your AI client. 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. If the saved builder is later deactivated, the screen warns that it is selected but not active, and only the Gutenberg tools stay on until you activate it again or pick another.
Gutenberg is not a card. The notice Gutenberg is always on at the top of the screen means the core block tools work beside whatever you select; it reads Gutenberg is unavailable only while the Classic Editor plugin is active. Spectra, Kadence Blocks, GenerateBlocks, Blocksy Blocks and Otter Blocks have independent switches 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.
Standalone compatibility
Section titled “Standalone compatibility”These are version-specific adapter contracts, not claims about the latest vendor versions. The Bricks row includes the EMCP 3.18.0 compatibility update. Editions and optional extensions can affect the available catalog.
| Integration | Version or dependency | Main workflow |
|---|---|---|
| Elementor | Active Elementor; premium features need Elementor Pro | Containers, widgets, templates and design settings |
| Bricks | Active Bricks 2.3.13 through 2.4.x (EMCP 3.18.0+); EMCP Pro | Flat trees, existing templates and design discovery |
| Breakdance | 2.8.3 through 2.8.x in Breakdance mode; EMCP Pro | Nested native trees and responsive controls |
| Avada | Active Avada theme and Builder 3.16.1 through 3.16.x; EMCP Pro | Native shortcode trees and Core display elements |
| Divi 5 | Active Divi 5.13.x; EMCP Pro | Pages, Theme Builder and supported Theme Options |
| Thrive Architect | Architect 11.0.x; EMCP Pro | Native HTML elements and page CSS |
| Oxygen 6 | 6.1.3 through 6.1.x in Oxygen mode; EMCP Pro | Templates, components and design data |
| Kirki 6 | 6.3.1 through 6.3.x with visual builder; EMCP Pro | Canvas graphs and staged versions |
| WPBakery | 9.0.1 through 9.0.x; EMCP Pro | Verified shortcodes, CSS and snapshots |
| Beaver Builder | 2.11.1 through 2.11.x; tested with Pro 2.11.1; EMCP Pro | Staged layouts and detached templates |
| Visual Composer | Website Builder 45.16.2 through 45.16.x; EMCP Pro | Paired graph, HTML and CSS staging |
| BeTheme & BeBuilder | Active BeTheme; EMCP Pro | Sections, wraps, item schemas and curated theme options |
Independent block packs
Section titled “Independent block packs”| Pack | EMCP edition | Scope |
|---|---|---|
| Spectra | Free | Discovery and mixed-page editing; no Astra requirement |
| Kadence Blocks | Free | Block editing and Design Library patterns |
| GenerateBlocks | Pro | V2 insertion with matching styles/CSS; verified on 2.4.0 |
| Blocksy Blocks | Pro | Native blocks and embeds; Blocksy theme and Companion required |
| Otter Blocks | Pro | Otter 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.
Start an editing session
Section titled “Start an editing session”- Activate the supported native builder and required companions.
- Select the standalone integration or enable the independent pack.
- Open EMCP Tools → Tools and select the integration’s tab, named after the builder or pack. The tab appears only after the builder is selected or the pack is switched on. Switch on the tools needed for the task and choose Save changes in the save bar. Write tools start disabled. On a new EMCP install every Pro tool starts disabled, read tools included, and Bulk Actions → Reset to defaults returns to that state. Existing saved choices are preserved on upgrade.
- Reconnect the MCP client. Long-lived WP-CLI processes retain loaded PHP until restarted.
- Read context, element or block schemas and the current document. Load the bundled skill where available.
- Create a draft or edit reviewed content using its latest hash. Re-read after each mutation.
- Check the native editor and frontend at desktop and mobile widths before publication.
Save and publication behavior
Section titled “Save and publication behavior”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.
Theme and builder ownership
Section titled “Theme and builder ownership”On EMCP Tools → Tools, Astra, Kadence and GeneratePress settings stay on the Themes tab. Their block plugins have independent integration tabs, where a Compatibility section keeps the older read and write dispatcher names working. Blocksy settings stay on Themes (Blocksy Theme), Companion features live on Plugins (Blocksy Companion: Extensions and Blocksy Companion: Content Blocks), and Gutenberg content is managed through the Blocksy Blocks tab. BeTheme settings and BeBuilder content share the BeBuilder tab.
The Templates screen 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.
Missing tools or unsupported content
Section titled “Missing tools or unsupported content”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.