Page builders integration

MCP for Beaver Builder

Beaver Builder keeps a page as a node map in post meta: the published layout, the editor's working draft, their settings twins, and an enabled flag. WP MCP reads the node tree and writes either one operation addressed by node id or a whole tree, doing what Beaver Builder itself does when it publishes: the new map goes to the published layout and, when the page has a draft, to the draft too, so the editor opens on what is live, and the layout asset cache is cleared. A page whose draft holds unpublished editor changes is refused until that draft is published or discarded, so an agent never silently throws away someone's work. Every row is post meta, so the post snapshot restores it exactly.

Get the free plugin Read the docs

detect-builderget-builder-contentupdate-builder-content

What your AI can do

Real Beaver Builder operations, every write reversible.

Detect Beaver Builder pages
Read a page's node tree
Update, add, remove or move one node by id, or replace the whole tree
Keep the published layout and draft in step and clear the asset cache
Refuse pages with unpublished editor changes instead of overwriting them
Roll back any layout write exactly

Example prompts

Just ask.

Is the About page built with Beaver Builder?

Update the button text in the hero module on the Beaver Builder landing page.

Remove the empty column from the second row of /contact.

Under the hood

The real calls.

wpmcp, beaver-builder

get-builder-content({ post_id: 44 }), node tree

update-builder-content({ post_id: 44, builder: "beaver-builder", operation: "update", path: "<node id>", attrs: {…} }), snapshotted, restorable

Frequently asked

Questions, answered.

What happens if someone is mid-edit in Beaver Builder?

If the page's draft differs from its published layout, the write is refused. Writing over the draft would discard those changes and writing beside it would be overwritten on the next publish, so the draft has to be published or discarded first.

Is the rendered text copy updated?

post_content keeps the text copy Beaver Builder rendered on its last publish; rendering a new one needs the plugin's front end, so it is left alone. The layout itself is what the page renders from.

More integrations