Edit WPBakery, Avada, and Oxygen pages with your AI agent

Builder pages are where a careless find-and-replace does the most damage. WP MCP Pro reads them the way the builder stores them and changes one element at a time. The same three tools cover WPBakery, Avada, Oxygen 6 and classic Oxygen, as well as Bricks, Divi, Beaver Builder, Breakdance and Thrive Architect.

What you need

• WP MCP Pro, connected to your AI client.
• Pages built with one of those builders. WPBakery and Avada pages can be read and written even while the plugin is inactive; classic Oxygen writes need Oxygen active (see below).

Step 1: Find out what built the page

› Which builder was used for the homepage and for /services?

detect-builder checks the markers each builder leaves: WPBakery’s editor flag or a [vc_row] shortcode, Avada’s fusion_builder_status flag or a [fusion_builder_container] shortcode, Oxygen 6’s _oxygen_data, and classic Oxygen’s ct_builder rows.

Step 2: Read the layout

› Show me the sections and elements on /services.

get-builder-content returns the layout as a tree with a path per element.

Step 3: Change one element

› Change the heading in the second row to "What we do", and move the
  testimonials row above pricing.

update-builder-content takes the post_id, the builder (wpbakery, avada, oxygen or oxygen-classic), and one operation (update, add, remove or move) addressed by path. Everything outside the edited element keeps its exact bytes. Each builder’s side data is kept in step:

• WPBakery: its editor flag and compiled custom CSS row.
• Avada: its builder flag, and its per-page dynamic CSS is invalidated so the page recompiles its styles.
• Oxygen 6: its generated CSS is refreshed through Oxygen when it is active.
• Classic Oxygen: Oxygen’s own serializer generates and signs the shortcode copy from the new tree, and an Oxygen revision is added. Because that signature uses your site’s key, a classic write needs Oxygen loaded, and a page still in the pre-4.0 format is read-only until it is saved in Oxygen 4.

Step 4: Undo if you need to

Every write is an ordinary post snapshot, so rollback-operation (or the Restore button on the WP MCP history screen) puts the layout and its side data back exactly, and the builder’s CSS is refreshed again after the rollback.