Page builders integration
WPBakery Page Builder AI agent tool reference
WPBakery stores a layout as shortcodes in post_content, plus two post meta rows beside them: its backend editor flag and the compiled custom CSS from each element's css attribute. WP MCP detects WPBakery pages (by the editor flag, or by [vc_row] and [vc_section] shortcodes when the backend editor was off), reads the layout as a tree with a dotted path per element, and writes either one element operation (update, add, remove or move) or a whole shortcode string. Both meta rows are kept in step with the content, and because content and meta are ordinary post data, the post snapshot captures them and rollback-operation restores the exact layout.
WPBakery Page Builder in plain language: WPBakery MCP.
In practice
How WPBakery Page Builder work goes with an agent.
WPBakery keeps a page as nested shortcodes in post_content, with two meta rows beside them: the backend editor flag _wpb_vc_js_status and _wpb_shortcodes_custom_css, the compiled vc_custom rules from each element's css attribute. The site-wide pieces are options: saved templates in wpb_js_templates, Design Options in wpb_js_ keys and the site CSS in wpb_js_custom_css. WP MCP splices edits into the stored string instead of re-serializing it, so a template or element keeps every byte it was saved with, and the custom CSS row is recompiled only when the set of css rules actually changed.
Go back to the version of the services page from before yesterday's edit.
Runs get-builder-content, whose read lists up to 20 revisions with id, date, author and hash, then update-builder-content with operation restore and path set to the revision id. It needs the current expected_hash and is snapshotted like any write, so the restore can itself be undone.
Insert our saved Contact strip template under the pricing row.
Runs get-builder-content with scope templates, which lists saved templates and, while WPBakery is loaded, its built-in ones as default:<n>, then update-builder-content with operation add and element {template: id}. The template's markup is spliced in byte for byte.
Save this row as a template called Pricing row.
Runs update-builder-content with scope templates, operation add and element {name}, plus post_id and path to name the row. It needs the hash from the templates read, snapshots the wpb_js_templates option first, and a rollback deletes the option again if the write created it.
Give the hero row 40px of top padding.
Runs update-builder-content with operation update, the row's path and a changed css attribute. Because the set of css rules changed, the _wpb_shortcodes_custom_css row is recompiled with the content; both are in the post snapshot, so one rollback restores the layout and its CSS.
What your AI can do
Real WPBakery Page Builder operations, every write reversible.
- Detect WPBakery pages, including ones saved with the backend editor off
- Read a page's element tree with a path per element
- Update, add, remove or move one element by path
- Replace the whole layout in one write
- Keep WPBakery's editor flag and custom CSS row in step
- Roll back any layout write exactly
Example prompts
Example WPBakery Page Builder prompts.
Which of my pages are built with WPBakery?
Change the heading in the second row of the WPBakery homepage.
Move the testimonials row above the pricing row on /services.
Under the hood
The WPBakery Page Builder calls, under the hood.
get-builder-content({ post_id: 31 }), element tree with dotted paths
update-builder-content({ post_id: 31, builder: "wpbakery", operation: "update", path: "0.1.0", attrs: {…} }), snapshotted, restorable
Safety and access
What can be undone on WPBakery Page Builder, and what costs what.
Recoverable on WPBakery Page Builder
- Content, the editor flag and the custom CSS row are covered by the post snapshot, so rollback-operation restores the layout and its CSS exactly.
- A templates write snapshots the whole wpb_js_templates option first, and a rollback restores it, or deletes it if the write created it.
- A publish runs inside the same snapshot as any other write.
WPBakery Page Builder limits and opt-ins
- Any write to a page that has a layout needs expected_hash from the latest read, including a whole-content replace. A blank page does not.
- Design Options and the site-wide custom CSS are read-only.
- The element catalog and the built-in default:<n> templates exist only while WPBakery is loaded.
- Publish works only on a draft, pending, private or scheduled page, and only for a user who may publish it.
Free or Pro: WPBakery detection, reads, element writes, publish, restore and the templates scope are all Pro, with no opt-in filter. On the free tier, export-content with mirror:true writes WPBakery pages to line-by-line JSON files for git, and duplicate-post copies a page's content and meta so you can stage a change on a copy first.
Part of WP MCP Pro
The WPBakery Page Builder integration is part of WP MCP Pro.
One Pro licence unlocks the WPBakery Page Builder tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.
Frequently asked
WPBakery Page Builder MCP: questions, answered.
Does WPBakery have to be active?
No. Reads and writes work on the stored shortcodes and meta directly, so nothing calls into the plugin. It does need to be active for the pages to render, of course.
Are untouched elements left alone?
Yes. An element operation rewrites only the addressed element; the rest of the layout keeps its exact markup.
Can the WPBakery Page Builder integration read WPBakery's Design Options?
Yes, read-only. The design_system scope returns the accent colors, element margin, gutter and breakpoints stored in the wpb_js_ options, noting they apply only while custom design options are on, plus the site-wide custom CSS.
What are the default:<n> templates?
WPBakery's built-in templates live in its code, not the database. While the plugin is loaded they are listed in the templates scope and can be added to a page by the default:<n> id, like any saved template.
How many revisions can it restore from?
The page read lists up to 20, newest first, each with id, date, author and a content hash. Restore takes the id of one of this page's own revisions and refuses anything else.
How does an agent learn an element's parameters?
From the catalog scope. While WPBakery is loaded it returns the element map, and with element set it returns that element's params: name, type, heading, description, default value, group and dependencies.
Is there an AI agent for WPBakery Page Builder?
Yes, through WP MCP rather than WPBakery Page Builder itself. An agent you choose, such as Claude or Cursor, can detect WPBakery pages, including ones saved with the backend editor off. WP MCP is a separate plugin, not a built-in AI feature of WPBakery Page Builder. On the undo side: Content, the editor flag and the custom CSS row are covered by the post snapshot, so rollback-operation restores the layout and its CSS exactly.
Related integrations
More integrations for the same agent.
MCP for Elementor
ProPage builders, 14 tools.
MCP for Gutenberg
FreePage builders, 4 tools.
MCP for Bricks
ProPage builders, 3 tools.
MCP for Divi (4 and 5)
ProPage builders, 3 tools.
MCP for Beaver Builder
ProPage builders, 3 tools.
MCP for Breakdance
ProPage builders, 3 tools.
Browse the full Integrations hub, or read more on WPBakery MCP and the WordPress MCP plugin.