Get the plugin
WP MCP/Integrations/Page builders

Page builders integration

BeTheme (BeBuilder) AI agent tool reference

BeTheme keeps a page's BeBuilder layout in post meta, in the format its builder-storage option asks for (base64 of a serialized array, or the array itself). WP MCP reads the layout as its sections with an outline by uid, and writes either the whole layout as a JSON array of sections or one element operation (update, add, remove or move by uid, add also from a saved template), plus publish to set the page live. A write stores the layout the way BeTheme's own save does: the visual builder's preview copy is kept in step, the stale page-object cache is dropped, and the SEO copy, local styles and CSS file are rebuilt through the theme, on the write and on the rollback. BeTheme has to be active, and once a page holds a layout a write needs the expected_hash the read returned. Every row is post meta, so the post snapshot restores it exactly.

detect-builderget-builder-contentupdate-builder-content

In practice

How BeTheme (BeBuilder) work goes with an agent.

BeTheme stores a BeBuilder page as a list of sections in the mfn-page-items meta row. Each section holds wraps, each wrap holds items, a nested wrap is an item flagged item_is_wrap, and every element carries a 9-character hex uid. Style fields named css_ are saved as selector, style and val triples, from which the theme builds the page's CSS file. WP MCP edits by uid and understands those triples, so setting a plain value changes val and leaves the stored selector and style alone. Writes go through the theme's own storage rules, not a raw guess.

Make the pricing wrap full width on mobile.

Runs get-builder-content for the outline by uid and the hash, then update-builder-content on the wrap's uid with element carrying the size fields (size, laptop_size, tablet_size or mobile_size). The layout is stored in the format the builder-storage option asks for, and the local styles and CSS file are rebuilt.

Change the section background color on the About page.

Runs update-builder-content with operation update and attrs setting a css_ field to a plain value. The stored selector and style are kept and only val changes; a style field that does not exist yet takes its selector and style from the theme's field definitions. The layout and preview copy are snapshotted first.

Add our saved hero template to the top of the landing page.

Runs get-builder-content with scope templates to list the BeBuilder template posts, then update-builder-content with operation add, to set to the empty string for the top level, and element {template: id}. Copies get new uids, and only elements of the kind the container takes are inserted.

Which colors and fonts does the theme use?

Runs get-builder-content with scope design_system, which reads the betheme option: colors, typography, layout keys and the builder storage mode. Passing element returns one option key. Keys holding API keys or secrets are never returned, and the scope is read-only.

What your AI can do

Real BeTheme (BeBuilder) operations, every write reversible.

  • Detect BeTheme (BeBuilder) pages
  • Read a page's sections with an outline by uid
  • Update, add, remove or move one element by uid, or replace the whole layout
  • Add from a saved BeBuilder template and publish the page live
  • Keep the preview copy, SEO copy, local styles and CSS file in step
  • Pin a write to the read's hash and roll back any write exactly

Example prompts

Example BeTheme prompts.

Is the homepage built with BeTheme?

Change the heading in the first BeBuilder section on /about.

Remove the old promo wrap from the services page.

Under the hood

The BeTheme calls, under the hood.

wpmcp, betheme

get-builder-content({ post_id: 27 }), sections outlined by uid, with a hash

update-builder-content({ post_id: 27, builder: "betheme", operation: "move", path: "<uid>", to: "<uid>", index: 2, expected_hash }), stored BeTheme's way, snapshotted

Safety and access

What can be undone on BeTheme, and what costs what.

Recoverable on BeTheme

  • The layout row, the visual builder's preview copy, the SEO copy and the local styles are all post meta, so a post snapshot restores them exactly.
  • The generated CSS file is not meta, so the rollback path rebuilds it too, and the file matches the restored layout.
  • Publish runs inside the same snapshot as any other write.

BeTheme limits and opt-ins

  • Writes need BeTheme to be the active theme and are refused with plugin_missing otherwise. Reads work from the stored row.
  • A page that already has a layout needs expected_hash from the latest read.
  • A section that pulls from a global section, and a wrap that pulls from a global wrap template, take their children from that template, so their contents are not edited here.
  • A section in the old format with items directly on it is refused until the page is next saved in BeBuilder. Theme options are read-only.

Free or Pro: BeTheme detection, reads, element writes, publish and the templates, theme options and catalog scopes are all Pro, with no opt-in filter. BeTheme support arrived in 0.9.0. Snapshots and rollback are the same engine on every plan.

Part of WP MCP Pro

The BeTheme integration is part of WP MCP Pro.

One Pro licence unlocks the BeTheme 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

BeTheme MCP: questions, answered.

Does BeTheme have to be active?

Yes. A write is stored the way BeTheme's own save works, including rebuilding its SEO copy, local styles and CSS file, so the theme has to be loaded. Reads work on the stored layout row.

Is an edit reversible?

Yes. The layout, preview copy and styles are all post meta, so the post snapshot restores them exactly, and the CSS file is rebuilt on the rollback too.

Will the BeTheme integration change my builder-storage setting?

No. A write stores the layout in whichever format the builder-storage option asks for, base64 of a serialized array or the array itself, and every read reports which one the site uses, as encoded or serialized.

What about global sections and wraps?

The outline marks them with the global template id. Their children are rendered from that template, so the adapter refuses to edit inside them; change the template itself or add and move the section as a whole.

Can the BeTheme integration see my API keys in the theme options?

No. The design_system read returns colors, typography and layout keys, and any key matching api-key, secret, token, password, purchase-code or recaptcha-key is never returned, even when you ask for it by name.

Which BeTheme version is it built for?

The adapter was recorded from the BeTheme 29.0.5 source. Every read reports the active theme's version and whether BeTheme is active, so a site on a different release is visible straight away.

Point your AI at BeTheme (BeBuilder).