Build Breakdance sites with AI — pages and their elements, headers, footers, popups, templates and global blocks, display conditions, global settings, selectors, presets and variables. Works on Oxygen 6 too.
A Breakdance page is a JSON node tree in post meta, not post content. An assistant editing the post body changes nothing a visitor sees — which is why generic AI tools appear to work on Breakdance sites and quietly do nothing.
Read a page as structure, write it back, or change one node and leave the rest untouched.
Breakdance publishes every registered element and its controls at runtime, so nothing is guessed from documentation that went stale.
All of them, built and assigned — a template with no display conditions is invisible, and that is checked.
Settings, selectors, presets and variables, so new work matches the site instead of inventing a second design system.
List them, restore one, and get a bad change back.
Trashing is reversible and ungated; permanent deletion asks for confirmation first.
Ask in plain language and the Breakdance integration turns it into typed calls against the node tree — no builder screens, no copy-paste, no rebuilding a page to change a heading.
Sections, headings and buttons placed as a real tree, not pasted markup.
Edit a header once and every page it applies to follows.
Find pages using elements that no longer exist, or hardcoded values that have variables.
Read a page as structure and rebuild it somewhere else without opening the builder.
The NibWP Breakdance integration exposes a Breakdance site to any MCP-compatible AI agent — Claude, Cursor, Claude Code and others. Pages, elements, templates and the global design layer become typed tool calls.
The reason this needs an integration at all: a Breakdance page is a JSON node tree stored in post meta, not in post content. An assistant working through the standard WordPress API can write to the post body all day and change nothing a visitor sees. Reading and writing the tree is the only way in.
Breakdance publishes its element registry at runtime, so the integration reads what your install actually has — which depends on the license, the active subplugins and any third-party element packs — rather than a static list that drifts with every release.
Single nodes can be added, updated, moved, duplicated or removed without touching the rest of the page, so an assistant changing a heading does not discard the hand edits around it. Revisions are covered, which means a change can be undone.
| Tool | Type | What it does |
|---|---|---|
| nibwp/breakdance-info | read | Version, brand mode, post types and counts. |
| nibwp/breakdance-elements | read | Every registered element with its control schema. |
| nibwp/breakdance-tree | write | Read a page as a tree or an outline, render it, or replace it. |
| nibwp/breakdance-nodes | write | Add, update, duplicate, move or remove a single node. |
| nibwp/breakdance-pages | write | Find Breakdance pages, create them, enable the builder. |
| nibwp/breakdance-templates | write | Headers, footers, popups, templates and global blocks. |
| nibwp/breakdance-conditions | write | Where each template actually displays. |
| nibwp/breakdance-global-settings | write | Site-wide typography, colors and breakpoints. |
| nibwp/breakdance-selectors | write | Global CSS classes and selectors. |
| nibwp/breakdance-presets | read | Saved design presets. |
| nibwp/breakdance-variables | read | Design tokens and their collections. |
| nibwp/breakdance-forms | read | Form submissions. |
| nibwp/breakdance-revisions | write | List and restore revisions. |
| nibwp/breakdance-delete | destructive | Trash or permanently delete, and clear a page. |
Yes. Once Breakdance is active, NibWP detects it and its abilities go live in your connected AI client — no configuration needed.
Yes. Oxygen 6 is the same builder under a different brand, and every post type and storage key is read from Breakdance's own constants rather than hardcoded, so it behaves correctly on either.
Not unless you ask it to. Single-node edits change one node and leave the rest alone, and properties merge rather than replace. Replacing a whole page is a separate, explicit action.
Because a Breakdance page is not post content. The layout is a JSON node tree in post meta, so an assistant writing HTML into the post body changes nothing a visitor ever sees.
Yes — revisions are covered, so a page can be restored to how it was. Check a page has revisions before a large structural change.
Activate the integration and it's live on your MCP endpoint instantly.