Divi is one of the builders NIBWP turns into a set of typed, agent-callable tools, whether you run it as a theme or as the Builder plugin. The moment it is detected, NIBWP reads its content and settings model and exposes it over the same secure MCP endpoint as everything else.
Divi stores page content in its own format, shortcodes in Divi 4 and a serialized structure in Divi 5. Both are readable and writable through the same ability, so an agent can work on a page without you having to care which generation it belongs to.
Active theme or plugin in, typed tools out. Read and write Divi builder content, theme options, the Global Color palette, the Library, the Theme Builder, module presets and the Role Editor.
Your builder, programmable
Connecting Divi to your agents changes what is possible with it:
- Both generations — Divi 4 shortcode content and Divi 5 serialized content through one ability.
- Global palette — Change the palette once and every module referencing it follows.
- Library at scale — Read and manage saved layouts instead of opening each one.
- Theme Builder — Inspect and change the templates that wrap your content.
- Module presets — Read and set the presets new modules inherit, so defaults stop drifting.
- Role control — Read and manage the Role Editor rather than clicking through permissions.
What it exposes
Eight abilities go live automatically the moment Divi is detected:
| Ability | Type | What it does |
|---|---|---|
nibwp/divi-info | read | Report the Divi version, whether it is the theme or the plugin, and what is active. |
nibwp/divi-content | write | Read and write per-post builder content, Divi 4 shortcode and Divi 5 serialized. |
nibwp/divi-theme-options | write | Read and change the theme options. |
nibwp/divi-colors | write | Read and set the Global Color palette. |
nibwp/divi-library | write | Read and manage saved Library layouts. |
nibwp/divi-theme-builder | write | Read and change Theme Builder templates. |
nibwp/divi-presets | write | Read and set global module presets. |
nibwp/divi-roles | write | Read and manage the Role Editor. |
From hours to one prompt
Ask for the outcome and let the agent choose the calls:
Update the palette to the new brand and fix the button preset to match
nibwp/divi-colors (run)
nibwp/divi-presets (run)
✓ applied · 2 tools · 1.6sYou describe the result; the agent picks the tools, validates each call, and reports what it changed.
What you can build
A few of the things teams do with the Divi integration:
Content audits
Read builder content across many pages to find what is out of date.
Palette rollout
Change the Global Colors and let every module follow.
Library hygiene
Report saved layouts nobody uses and tidy them up.
Template review
Read the Theme Builder assignments before changing a template.
How it stays safe
- Scoped tokens — Reading content and writing it are different scopes. You decide which to grant.
- Every change logged — Each call is recorded with the account, the tool and the result.
- Draft first — Force-draft keeps a large content job reviewable before anything goes live.
Getting started
- Activate Divi — Detection covers the theme, the Extra theme and the Builder plugin.
- Connect a client — Point any MCP client at your NIBWP endpoint and approve the scopes you want.
- Read a page first — Ask for the builder content of one page to see the shape before writing any.
FAQ
Divi 4 or Divi 5?
Theme or plugin?
Can it build a page from scratch?
Will it break my layouts?
Connect Divi
Activate the theme or plugin, connect an MCP client, and let agents operate it safely.
Browse integrations