Page builders · 10 modules
WordPress Page Builder MCP for supported native builder structures.
A WordPress page builder MCP works on the document model the builder uses. Compare the operations below by read/write scope, edition and installed version. Schema-aware saves still need native-editor and rendered checks; they do not guarantee layout quality or compatibility.
What goes wrong without a plugin-aware module
- Generic HTML that the native editor cannot safely maintain
- One-off styling that bypasses shared classes, presets, variables, or components
- Template and global-style changes made without reviewing their dependency radius
Modules
10 modules compared
Each module loads only when its plugin is active. Elementor editing starts in Free; the other builders need Pro. Open a module for its full ability list, requirements and safety notes.
| Module | Edition | Abilities | Inspect / change / destructive | Covers | Guide |
|---|---|---|---|---|---|
| Elementor | Free 18 + Pro 52 | 70 | 28 / 28 / 14 | document content, element schemas, add, edit, and delete elements, atomic widgets | Elementor MCP |
 Bricks | Pro | 49 | 21 / 19 / 9 | content trees, elements, templates and conditions, components | Bricks MCP |
 Breakdance | Pro | 33 | 16 / 0 / 17 | element trees, element type schemas, templates, template conditions | Breakdance MCP |
 Divi | Pro | 47 | 17 / 22 / 8 | module content, module and style schemas, Theme Builder templates, template conditions | Divi MCP |
 Oxygen | Pro | 37 | 17 / 2 / 18 | element trees, element schemas, templates and conditions, global classes | Oxygen MCP |
 Beaver Builder | Pro | 21 | 9 / 7 / 5 | layouts, nodes, modules, structure schemas | Beaver Builder MCP |
 WPBakery | Pro | 18 | 8 / 6 / 4 | page inspection, serialized content, elements, element schemas | WPBakery MCP |
| Flatsome | Pro | 11 | 6 / 3 / 2 | setup health, shortcode tree reads, whole-tree writes, element insert, edit, move, delete | Flatsome MCP |
 Etch | Pro | 60 | 23 / 21 / 16 | content and nodes, components, templates, styles and stylesheets | Etch MCP |
 Mosaic | Pro | 41 | 17 / 16 / 8 | element trees, components and overrides, templates and assignments, collections | Mosaic MCP |
Counts are documented operations per builder, not a measure of output quality. Gutenberg and core block editing are in the free block workflow; converting a page between builders is covered by the page builder converter.
Worked example
Rename the pricing heading on an Elementor landing page without turning it into markup Elementor cannot reopen.
Elementor, because its editing starts in GoBuildWP Free; the same find, inspect, edit shape applies to the Pro builder modules with their own calls.
wppilot/elementor-check-setupFreeReports the Elementor and Elementor Pro versions, whether the v4 atomic runtime is present, and the kit's enabled breakpoints, so the edit targets the widgets this install really runs.
wppilot/elementor-find-elementsFreeSearches the document for the text "Pricing" and returns the matching element id and its path, instead of pulling the whole page into the conversation.
wppilot/elementor-get-widget-paramsFreeReturns only the settings a build sets on that heading (text, link, tag, size) rather than the full control list, which for one heading runs to 186 controls.
wppilot/elementor-edit-elementFreeMerges the new title into the existing settings. An unknown control id or an invalid option aborts the write and returns the element's schema in the error, so a wrong guess never lands on the page.
wppilot/elementor-clear-document-cacheFreeOnly needed when the heading sits in an Elementor Pro template: clears that template's cached render so other pages stop showing the old text.
What to check yourself. Reload the page in Elementor's editor and select the heading. It should still be a Heading widget with the new wording in its own field, not an HTML widget holding a copy of it, and the tablet and mobile views should keep whatever sizes the designer set.
Why it matters
What plugin-aware changes for page builders
Visual builders use different native document models: JSON trees, blocks or nested shortcodes, often with shared styles and templates. Inspect the owning builder and operation before writing. Write markup straight into post content and the page may render acceptably while becoming uneditable in the builder that owns it, which is the failure that only surfaces the next time a person opens the editor.
A first safe workflow
Start with a read. Ask the agent to describe the existing structure of one page, in the builder's own terms, and check its answer against what you see in the editor. If the description is wrong, nothing written afterwards will be right. Once it matches, the first write should be a single element on a page nobody has bookmarked, reviewed in the builder before it is reviewed on the front end.
How to tell it worked
Reopen the page in the builder itself, not just the front end. Confirm the element tree still parses, that shared classes and global styles are intact, and that the layout holds at the breakpoints the theme actually defines. If the change touched a template or a global, check a second page that uses it.
Choosing between builder modules
Check the builder's major version before anything else
Each builder module targets the current generation of its builder, and an older generation that stores pages differently is not edited at all. That makes the installed version the first fact to establish, before comparing features:
- Divi needs Divi 5. Divi 4 shortcode layouts are not edited.
- Oxygen needs Oxygen 6. Oxygen Classic stores pages as shortcodes and is not supported, and its Gutenberg and WooCommerce companions do not work on Oxygen 6 either.
- Breakdance needs a recent release and does not load while its engine runs in Oxygen mode.
- Beaver Builder needs a recent release, on a post type the builder is enabled for; global node templates need a paid edition.
- Bricks loads only while the Bricks theme is active, and Mosaic refuses a major release GoBuildWP does not support yet.
- Elementor, WPBakery, Flatsome and Etch each have their own setup check that names the release in use.
Elementor starts in Free; the other builders need Pro
Elementor's Free tools include reading and editing elements and supplying a complete element tree through elementor-set-content. Pro adds higher-level composition through elementor-build-page, templates, global classes, variables and popups. Whole-page writing alone is not the edition boundary. Other builder modules in this category require Pro; core WordPress block tools remain in Free. Match the requested operation to the reference and the installed builder version.
How each builder's storage changes your recovery options
Builders keep pages in very different shapes, and the change ledger can only restore what it could snapshot. Before bulk work, know where your builder sits:
- Mosaic writes land in its own tables and are all recorded without a before-image. Back those tables up before a large change.
- Divi Theme Builder templates, once created or deleted, and deleted Library items cannot be rolled back. Etch components and templates are the same once deleted.
- Deleting an Oxygen template or block leaves pointers to it in other templates and canvases, so search for references first.
- WPBakery addresses elements by position, so any add, move or delete renumbers the page. The agent has to read the content again before targeting the next element.
Moving a page from one builder to another
Sites change builders, and rebuilding every page by hand is the usual cost. GoBuildWP Pro includes a page builder converter. list-convertible-documents reports which conversion pairs exist on this install, since a pair is offered only when both builders are present. convert-preview translates a page into a neutral model and reports what would carry over exactly, what would be approximated, what falls back to raw markup and what cannot be carried at all, without writing anything.
convert-document then creates a new draft in the target builder and never touches the source page. If the preview showed dropped elements, or more than a quarter of the page reduced to raw markup, it refuses until the loss is explicitly accepted. Every conversion loses something, so treat the draft as a starting point: open it in the target builder, fix what the report named, and only then swap it in. rollback-change removes a draft you decide against.
When the builder has its own agent connection
Elementor ships an MCP server of its own for its atomic elements, and Breakdance documents an Agent Connector plugin that uses an application password. Either can be connected alongside GoBuildWP, and each is configured separately. The record differs by route. From GoBuildWP Free 1.18.0, writes made through Elementor's own MCP abilities are recorded on GoBuildWP's Changes screen: mapped element, composition, page-settings, global class and variable writes can retain supported partial before-images; inspect target resolution, capture and the actual rollback entry, while Elementor's create-page, component and default-style writes are recorded as irreversible. Those Elementor calls skip GoBuildWP's confirmation and Pro's approval queue unless the Other MCP servers setting is on, which needs WordPress 7.1. Edits made through Breakdance's connector are not among the writes GoBuildWP maps, so do not expect them in the ledger. If you use both, decide which one makes structural changes and keep the other to reading.
A first prompt for an existing builder page
“Run the setup check for this page's builder and tell me the builder, its version, whether GoBuildWP supports it, and which of my next changes the change ledger could undo. Then describe the structure of this page in the builder's own terms.” Compare that description with the editor before approving a write. Each builder's guide, such as the Elementor MCP guide or the Bricks MCP guide, covers the editing workflow in detail.
FAQ
Page builders and AI, answered
Can an AI agent edit a page built in Elementor or Bricks without breaking it?
It can make changes the builder can reopen, which is the precondition, not a guarantee. The builder modules read the element tree and each element's settings schema first and write through the builder's own document model rather than HTML in post content. A valid setting can still be the wrong one, a template or global edit reaches other pages, and unsupported builder versions are refused, so reopen the page in the builder afterwards and use staging or a working copy for a live page.
Does GoBuildWP need the builder's own Pro licence?
GoBuildWP needs whatever the builder itself needs. If a capability only exists in the builder's paid edition, the ability that depends on it is not usable on a site running the free edition, and integration health reports that rather than failing mid-call.
What should be checked after an AI-built page?
Open it in the builder, not just the front end. A page can render correctly to a visitor while the editor reports a structure it cannot parse, and that only becomes visible the next time someone tries to change it.
Start in Read Only, then add what the site runs
Connect your AI client to the free MCP foundation and check what it can see. Add Pro when a job needs the module for your installed plugin.