Read the template & git-like version graph, components, releases and global settings; author templates, components and fragments by committing configs through Builderius's own versioning.
Agents understand Builderius's module model and version graph — and can author and commit real templates, something no generic AI can do.
Read and write Builderius data through typed, schema-validated calls.
Author by committing configs on a template's branch — every change is a commit.
Build valid Builderius module trees (HtmlElement, Collection, Component, SmartForm and more).
Wire WordPress data into modules with [[[wp.*]]] tokens.
Every write validates the config first, supports dry-run, and reads the result back.
No exports, no SQL, no brittle scripts — just protocol.
Ask in plain language and the Builderius integration turns it into typed calls — it builds a valid module config, validates it, and commits it on the template's branch. No exports, no SQL.
Have an agent author a Builderius template from a brief and commit it.
Create or update many templates in one agent run.
Inspect the version graph and find stale or empty templates.
Chain Builderius actions into multi-step agent workflows.
The NibWP Builderius integration exposes Builderius to any MCP-compatible AI agent — Claude, Cursor, Claude Code or your own — as typed, schema-validated tools. Instead of clicking through the Builderius canvas, you describe what you want and the agent reads your template and git-like version graph and authors real Builderius modules over the Model Context Protocol (MCP).
It runs on the NibWP Pro plan and activates the moment Builderius is detected. Every write validates the module config, supports dry-run, and reads the result back. Browse all NibWP integrations.
| Tool | Type | What it does |
|---|---|---|
| nibwp/builderius-list-templates | read | List templates with type, branch count and active commit. |
| nibwp/builderius-get-template | read | Get a template's current module config. |
| nibwp/builderius-list-versions | read | The git-like branch/commit graph for a template. |
| nibwp/builderius-build-config | read | Turn a nested module tree into a validated Builderius config. |
| nibwp/builderius-create-template | write | Create a template and commit authored content. |
| nibwp/builderius-update-template | write | Commit a new config snapshot on the template's branch. |
| nibwp/builderius-delete | destructive | Delete a Builderius record (flagged destructive). |
The agent read our Builderius version graph and committed a new template correctly — no canvas clicking.
It builds valid Builderius modules from a brief and commits them. What took an afternoon is now one prompt.
Dry-run plus read-back means I trust it on real templates — I can see exactly what it will commit.
Finally an AI that understands Builderius's branches and commits instead of dumping raw HTML.
We audit and fix templates across the whole site through the agent now, not one by one.
Zero glue code — no exports, no SQL. The agent talks to Builderius over the protocol and just does it.
Yes — once Builderius is installed, NibWP detects it and its abilities go live instantly.
Yes — it builds valid Builderius module configs and commits them through Builderius's own versioning, with dry-run and read-back.
Every write validates the config first, supports dry-run, and reads the result back; deletes are flagged destructive.
No — the Builderius integration works on Pro. A Builderius Pro Skill (design-to-build) is on the roadmap.
Activate the integration and it's live on your MCP endpoint instantly.