Page builders integration
Breakdance AI agent tool reference
Breakdance stores a page's document as a JSON tree inside its _breakdance_data post meta, with generated CSS cache rows beside it. WP MCP reads that tree and writes either one node operation (update, add, remove or move by node id) or a whole tree, storing the row exactly the way the builder stores it. The layout stays byte for byte identical outside the edited nodes, including elements WP MCP does not know, and the page's generated CSS is refreshed through Breakdance when it is active. Page snapshots count elements and responsive overrides, and rollback-operation restores the exact rows.
Breakdance in plain language: Breakdance MCP.
In practice
How Breakdance work goes with an agent.
Breakdance stores a page as a JSON document wrapped in a second JSON string. The _breakdance_data row holds an object whose tree_json_string key contains the real tree, with integer node ids counted up from a _nextNodeId marker. Node types are PHP element classes such as EssentialElements\Heading. Breakdance 1.x used the same rows without the leading underscore, and WP MCP reads and writes whichever a page already has instead of adding a second row. Site-wide data (selectors, palette, variables) lives in separate options that the engine encodes twice.
What properties does the Heading element take, and set the hero heading to this text.
Runs get-builder-content with scope catalog and element set to the element's name to read its content, design and settings controls, then update-builder-content with operation update, the node id and attrs. The properties are deep-merged and null removes a key. The row is snapshotted first and the page CSS is refreshed.
Add a two-column row under the hero section.
Runs update-builder-content with operation add and a Columns node that nests two Column children, which is the shape Breakdance requires. A Column placed anywhere but directly inside a Columns element is refused with an explanation, and a write that changes nothing leaves the row untouched.
Create a btn-primary global class.
Runs get-builder-content with scope design_system for hashes.classes, then update-builder-content with scope design_system, operation add, to set to classes and an element of type class. The selectors option is snapshotted whole, written the way the engine writes it, and the global CSS is regenerated.
Add our brand teal to the Breakdance color palette.
Runs update-builder-content with scope design_system, operation add, to set to palettes and an element with a label and a value. The cssVariableName is generated the way the engine names a new color, the global settings option is snapshotted first, and the hash from the read must still match.
What your AI can do
Real Breakdance operations, every write reversible.
- Detect Breakdance pages
- Read a page's node tree
- Update, add, remove or move one node, or replace the whole tree
- Leave every untouched node byte for byte as it was
- Refresh Breakdance's generated CSS after writes
- Roll back any layout write exactly
Example prompts
Example Breakdance prompts.
List the sections on the Breakdance homepage.
Change the hero heading and subheading on /launch.
Move the FAQ section to the bottom of the pricing page.
Under the hood
The Breakdance calls, under the hood.
get-builder-content({ post_id: 52 }), node tree
update-builder-content({ post_id: 52, builder: "breakdance", operation: "move", path: "<node id>", to: "<parent id>", index: 3 }), snapshotted, restorable
Safety and access
What can be undone on Breakdance, and what costs what.
Recoverable on Breakdance
- The data row and the two generated CSS cache rows are post meta, so a post snapshot restores them exactly and the rollback rebuilds the page CSS through Breakdance.
- A design write snapshots the one option it changes (selectors or global settings), and a rollback restores the whole option and refreshes the global CSS.
Breakdance limits and opt-ins
- Design writes cover classes and palette colors only. Breakdance variables are readable but not writable, and templates are read-only.
- Design writes need the edit_theme_options capability and the hash of the list from the read.
- Page writes carry no content hash, so read and write in one pass.
- Nodes are written as the builder stores them, but the CSS rebuild runs only while Breakdance is loaded; otherwise the stale cache rows are dropped and rebuilt on a later view.
Free or Pro: Detecting Breakdance pages, reading trees, the design_system, templates and catalog scopes, and every write are Pro, with no opt-in filter. On the free tier, export-content with mirror:true writes Breakdance pages to stable JSON files you can keep in git, and snapshots and rollback work the same on every plan.
Part of WP MCP Pro
The Breakdance integration is part of WP MCP Pro.
One Pro licence unlocks the Breakdance 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
Breakdance MCP: questions, answered.
What if a page uses Breakdance elements WP MCP does not know?
They are kept exactly as stored. Only the addressed node changes.
Does Breakdance need to be active?
Reads and writes work on the stored rows. The CSS refresh goes through Breakdance, so keep it active for edits to show up styled right away.
Can it edit Breakdance global classes and colors?
Yes. Selectors and palette colors are addressed as classes/<name> and palettes/<cssVariableName>, validated against the shape Breakdance reads, and written hash-guarded and snapshotted, with the global CSS regenerated afterwards. Variables can be read but not changed.
Can the Breakdance integration edit headers, footers and popups?
It can read them: the templates scope lists template, header, footer, block and popup posts with their trees and conditions. The documented write surface is page trees plus the class and palette lists, not template editing.
Does it work on sites still running Breakdance 1.x?
Yes. Pages saved by 1.x keep their data in breakdance_data without the underscore, and WP MCP uses the row a page already has. The prefix a new page gets follows the loaded version and can be overridden with the wpmcp_breakdance_meta_prefix filter.
Is there an AI agent for Breakdance?
Yes, through WP MCP rather than Breakdance itself. An agent you choose, such as Claude or Cursor, can detect Breakdance pages. WP MCP is a separate plugin, not a built-in AI feature of Breakdance. On the undo side: The data row and the two generated CSS cache rows are post meta, so a post snapshot restores them exactly and the rollback rebuilds the page CSS through Breakdance.
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 WPBakery Page Builder
ProPage builders, 3 tools.
MCP for Beaver Builder
ProPage builders, 3 tools.
Browse the full Integrations hub, or read more on Breakdance MCP and the WordPress MCP plugin.