Builderius is one of the builders NIBWP turns into a set of typed, agent-callable tools. It is unusual among builders in that it versions everything the way source control does, and the integration works with that rather than around it.
Because Builderius keeps a template graph with versions, branches and releases, an agent can author a change as a commit rather than as an overwrite. That means the thing an agent builds is reviewable and revertable by design, which is rarely true of builder output.
Active plugin in, typed tools out. Read the template and version graph, components, fragments, releases and global settings, and author new versions by committing configs through Builderius’s own git-like versioning.
A builder with history
Connecting Builderius to your agents changes what is possible with it:
- Versioned authoring — Changes land as commits on a branch, not as an irreversible overwrite.
- The whole graph — Templates, versions, components, fragments and releases are all readable.
- Config in, config out — Export and import configuration, so a site can be described as data.
- Component reuse — Read components and build new templates from what already exists.
- Form submissions — Read submissions alongside the templates that produced them.
- Reviewable output — Because it commits, an agent change can be inspected before release.
What it exposes
Twenty-one abilities go live automatically the moment Builderius is detected. The read side covers the whole graph:
| Ability | Type | What it does |
|---|---|---|
nibwp/builderius-list-templates | read | List templates in the project. |
nibwp/builderius-get-template | read | Read a single template and its current version. |
nibwp/builderius-list-versions | read | List versions for a template, the history behind it. |
nibwp/builderius-list-components | read | List reusable components. |
nibwp/builderius-list-releases | read | List releases, the published points in the graph. |
nibwp/builderius-list-fragments | read | List fragments. |
nibwp/builderius-list-global-settings | read | Read the global settings. |
nibwp/builderius-list-form-submissions | read | Read form submissions. |
nibwp/builderius-build-config | read | Assemble a config object for a change before committing it. |
nibwp/builderius-create-template | write | Create a template by committing a config. |
nibwp/builderius-update-template | write | Commit a new version of an existing template. |
nibwp/builderius-create-component | write | Create a reusable component. |
nibwp/builderius-create-branch | write | Branch the graph so work can proceed without touching the released version. |
nibwp/builderius-import-config | write | Import a configuration into the project. |
nibwp/builderius-delete | manage | Remove an object from the graph. |
The list above is the shape of it rather than the whole set: list-starters, list-modules, get-component, create-fragment, update-global-settings and export-config round it out to twenty-one.
From hours to one prompt
Ask for the outcome and let the agent choose the calls:
Branch off the current release and add a pricing template built from existing components
nibwp/builderius-create-branch (run)
nibwp/builderius-list-components (run)
nibwp/builderius-build-config (run)
nibwp/builderius-create-template (run)
✓ committed · 4 tools · 3.8sThe work lands as a commit on a branch, so you can look at it before it becomes a release.
What you can build
A few of the things teams do with the Builderius integration:
Template authoring
Build a new template from existing components and commit it for review.
Graph audits
Report which templates have drifted from their release.
Config portability
Export a configuration and import it into another project.
Safe experiments
Branch, try something, and discard it without touching what is live.
How it stays safe
- Versioned by nature — Changes are commits, so there is always a previous version to return to.
- Branch before you build — An agent can work on a branch and leave the released version untouched.
- Every change logged — Each call is recorded with the account, the tool and the result.
- Delete is separate — Removing anything from the graph needs the manage scope, not write.
Getting started
- Activate Builderius — The integration appears in NIBWP the moment the plugin is detected.
- Connect a client — Point any MCP client at your NIBWP endpoint and approve the scopes you want.
- Walk the graph — Start with
list-templatesandlist-versionsto see how the project is shaped.
FAQ
Does it overwrite my templates?
Can I review before it goes live?
What is build-config for?
Can it delete things?
Connect Builderius
Activate the plugin, connect an MCP client, and let agents commit work for review.
Browse integrations