Breakdance

Breakdance is one of the builders NIBWP turns into a set of typed, agent-callable tools. Activate Breakdance, switch the integration on, and an agent can read and build pages through the same secure MCP endpoint as everything else — scoped to your token and recorded in the audit log.

This one needs an integration more than most builders do. A Breakdance page is not stored in post content: the layout is a JSON node tree kept in post meta. An assistant working through the standard WordPress API can write to the post body all day and change nothing a visitor ever sees.

Your builder, programmable

Connecting Breakdance to your agents changes what is possible with it:

• The real node tree — Read a page as structure, replace it wholesale, or edit a single node and leave everything else exactly as it was.
• Your element registry — Breakdance publishes every registered element and its controls at runtime, so nothing is guessed from a documentation page that went stale.
• Templates that actually display — Headers, footers, popups and templates are built together with their display conditions — one without them exists and appears nowhere.
• The global design layer — Settings, selectors, presets and variables, so new work matches the site instead of inventing a second design system.
• Revisions as the undo — List them and restore one when a change was wrong.
• Oxygen 6 included — The same codebase under a different brand. Post types and storage keys are read from Breakdance’s own constants, so it behaves correctly on either.

The tools

Fourteen abilities, grouped by what they touch rather than one per operation:

A sensible order

Reading before writing is what separates a build that works from one that renders blank:

1. Check what is there — breakdance-info reports the brand mode and the real post type slugs, which differ between Breakdance and Oxygen.
2. Read the vocabulary — breakdance-elements lists what this install registers. The set depends on the license, the active subplugins and any third-party packs.
3. Read the tokens — breakdance-variables and breakdance-selectors, so the new section uses what the site already has.
4. Outline before editing — breakdance-tree with action=outline gives you node IDs without pulling down an enormous tree.
5. Change one node — breakdance-nodes merges properties rather than replacing them, so a heading change does not discard the styling around it.
6. Assign templates — A new header or template needs conditions before anyone sees it.

Worth knowing

Element slugs are namespaced — EssentialElementsHeading — and in JSON the backslash has to be doubled. Breakdance does not error on an unknown element; it renders nothing. Deleting a header, footer or template changes every page it applied to, not just one, so trashing (reversible) is preferred and permanent deletion asks for confirmation.

FAQ