An agency’s WordPress sites rarely all use the same builder. One client uses Bricks, another has years of WPBakery content, and a third builds everything in Gutenberg. An AI workflow is useful only if it understands the editor and content already on each site.
EMCP Tools 3.17.0 brings dedicated native integrations to that workflow. Each supported builder gets its own tools, schemas and authoring guidance. Gutenberg block plugins also gain room of their own, separate from theme settings.
Version 3.17.0 is now available. It combines the History improvements with the builder and Widget Builder work below. Download the free release, or update Pro through Freemius.
One connection, the builder your site uses
The Page Builders screen selects one standalone integration at a time. Its tools appear in dedicated sections, while inactive builder tools stay out of discovery. This changes the EMCP tool surface; it does not uninstall plugins or convert their pages.
The catalog contains 12 standalone integrations, including the existing Elementor and BeBuilder workflows:
| Builder | Main workflow |
|---|---|
| Elementor | Widgets, containers, templates and design settings |
| Bricks | Flat element trees, native controls and existing templates |
| Breakdance | Nested layouts and breakpoint-specific controls |
| Avada Builder | Verified shortcode layouts and Core display elements |
| Divi 5 | Pages, Theme Builder and supported Theme Options |
| Thrive Architect | Native HTML elements and page-local CSS |
| Oxygen 6 | Templates, components, design data and library transfers |
| Kirki 6 | Canvas graphs, responsive styles and staged versions |
| WPBakery | Verified shortcodes, template application and page CSS |
| Beaver Builder | Native staged layouts and detached reusable templates |
| Visual Composer | Paired editable graphs and rendered HTML/CSS |
| BeTheme & BeBuilder | Sections, wraps, items and curated theme options |
Support is version-specific. The compatibility guide lists ranges and dependencies. Each integration explains what is writable, discoverable or outside scope. Installing a vendor plugin does not make every optional extension authorable.
Gutenberg stays beside the selected builder
Gutenberg does not use the standalone selection slot. Its extensions have independent toggles, so a site can use several supported packs together.
- Spectra has its own tools without requiring Astra.
- Kadence Blocks adds block editing and Design Library patterns separately from the Kadence theme.
- GenerateBlocks supports V2 insertion with matching compiled styles, independently of GeneratePress.
- Blocksy Blocks separates content from theme and Companion management. Its native theme and Companion requirements still apply.
- Otter Blocks adds pages, blocks, local patterns, styles and supported settings, with Free and Pro discovery.
That makes 18 integrations across standalone builders, Gutenberg and these five packs. It is a catalog count, not a claim that every site exposes all their tools at once.
Spectra and Kadence Blocks integrations are included in free EMCP. The other three packs require EMCP Pro. Vendor licenses remain separate: EMCP does not unlock premium blocks or patterns.
Templates and design systems have their own tools
Divi 5 has separate operations for modules, Theme Builder layouts and Theme Options. Prepare a footer assigned to one page while preserving the default templates. Credentials, executable option fields and global preset authoring are excluded.
Oxygen 6 covers template conditions, headers and footers, component masters and overrides, global design data and Design Library workflows. Matching templates start disabled. Imports remap dependencies, but do not migrate media files, menus or custom fields. Oxygen Classic is a different format and is not supported by this adapter.
Avada includes Core discovery and verified display elements. Use existing Portfolio or FAQ records and Slider groups without confusing layout work with creating source content.
Blocksy separates theme tools, Companion tools and block editing. Companion Pro Content Blocks start as disabled drafts, with explicit publication and enablement. Advanced conditions remain native-editor work.
The admin Templates page also follows its module toggle when another builder is selected. Its current library remains Elementor-specific. Builder-native libraries use their own tools; the menu fix does not make templates portable between editors.
Native content differs between builders
The integrations share a discover, edit and verify workflow, but storage models differ. Bricks uses a flat element list. Breakdance and Oxygen use nested trees. Avada and WPBakery use shortcode layouts. Thrive Architect uses native HTML and styles. Static Gutenberg blocks need attributes and the saved HTML their editor expects.
Visual Composer illustrates why this matters. Its native graph and frontend HTML are separate artifacts. The integration stages the graph with matching HTML and CSS. Saving JSON alone is not a complete update, and the adapter does not compile arbitrary React elements on the PHP server.
Beaver Builder, Kirki and Visual Composer expose staged publication. Other native saves can change content while preserving the page’s publication status. Read the adapter’s contract before editing a live page.
Skills travel with the tools
Builder-specific skills are available through runtime discovery and downloadable bundles. They explain native controls, editing sequences, responsive checks and known limits. An agent should still start with the installed schemas.
The Bricks guidance credits Gaurav Tiwari (@wpgaurav) and retains its upstream MIT attribution. Divi guidance credits Shashank Gupta / DiviLove for the referenced Divi 5 skill. Broader reference material does not expand the adapter’s actual write scope.
See Agent Skills for loading and downloading guidance.
Custom widgets can use real data
Widget Builder gains query, shortcode and remote-source controls. Custom Elementor widgets can use posts, products, terms, menus, site data, breadcrumbs and cart information. Allowlisted shortcode providers include saved Elementor templates and supported form plugins.
Remote data keys belong in Connection > Live data providers and stay outside cloud settings sync. A data-backed widget still needs deliberate field mapping, empty states and a review of what reaches visitors.
Reserved control names such as animation and _animation are rejected because they can trigger Elementor’s entrance-animation behavior and hide a widget. Structured defaults and registry synchronization also improve generated widgets.
Read the Widget Builder reference for the supported data controls.
History records more and refuses unverifiable undo
The release includes the History work prepared earlier in this cycle. Creating an Elementor page records a creation event with its initial content; undo removes the page instead of leaving an empty shell. Uploads receive creation records with file-state checks. Page settings and custom CSS preserve exact prior metadata, including absent values and escaped content.
Rollback checks the state an operation changed and verifies restoration. Incomplete database snapshots, older post snapshots without sufficient conflict information and generic attachment-deletion snapshots without file backups refuse automatic undo, even with force.
Coverage remains operation-specific. Native revisions and adapter recovery snapshots are separate workflows, and older omitted actions cannot be reconstructed. See the History reference.
A practical first session
Start on a test site with the actual vendor builder installed. Select its integration, reconnect your MCP client and inspect context and schemas. Enable the required writes, create a draft, and check both the native editor and responsive frontend before publication.
The guides record tested versions and limits. Some validation used local source bridges, so those checks do not replace installing and accepting the final release ZIP in your own environment.
Explore the integration directory, setup guide and changelog to plan the update.