Divi MCP · Pro
Divi MCP: edit Divi layouts with any AI agent.
A Divi MCP server lets an AI agent open a Divi page the way the builder stores it and change it for you. WP MCP is a self-hosted WordPress plugin that does this for both Divi 4 and Divi 5, from Claude, Cursor or any MCP client, with a snapshot before every write.
Self-hosted · snapshot before every write · one-click undo
› Change the hero heading on the Divi 5 homepage to 'Book a free survey'
get-builder-content block tree, paths, content hash
⛨ post_content and Divi flags saved
update-builder-content operation update, path 0.0.1, hash checked
✓ Heading changed. Every byte outside that block is untouched.
What it is
What a Divi MCP server does.
MCP, the Model Context Protocol, is how an AI client calls tools on another system. A Divi MCP server is the piece that sits on your WordPress site and turns Divi layouts into tools an agent can call: find the Divi pages, read a layout, change a module, put it back if the change was wrong.
The hard part is that Divi has two storage formats. Divi 4 keeps a layout as shortcodes in post_content. Divi 5 keeps it as block markup, every block in the divi namespace inside one placeholder block. WP MCP reads both, and on Divi 5 it parses the layout into a tree and gives every block a dotted path, because the markup carries no block ids of its own.
Most requests on a Divi site are small and repetitive: a phone number in forty modules, a button label that should read differently, a footer that needs a new line. Done by hand, each one means opening the Visual Builder page by page. An agent connected through WP MCP does the same job from a sentence, and because Divi 5 edits are addressed by block path, a change to one module cannot disturb the rest of the layout. Divi 4 sites get reliable reads and whole-layout replacement, so you can still audit before deciding to move to Divi 5.
Read and change
What WP MCP can read and change in Divi.
It can read
- Which pages are built with Divi, and whether each is Divi 4 or Divi 5
- A Divi 5 layout as a block tree with a path per block and a content hash
- A Divi 4 layout as its stored shortcodes
- The Divi Library and the Theme Builder header, body and footer templates
- The Divi 5 module catalog, when Divi 5 is loaded
It can change
- Update, add, remove or move one Divi 5 block by its path
- Replace a whole Divi 5 layout in one write
- Replace a Divi 4 shortcode layout whole
- Edit a library or Theme Builder template by its post id
These are the real ability and operation names the agent calls. TheDivi (4 and 5) AI agent tool reference page lists the calls in detail.
Example prompts
Three things to ask first.
List every page built with Divi and tell me which ones are still on Divi 4.
On the Divi 5 pricing page, change the middle plan's button text to 'Start free' and keep everything else as it is.
Show me the Theme Builder footer template and update the copyright line in it.
Which pages are still on Divi 4?
detect-builder and get-builder-content report the format for each page, so you get a list without opening a single one in the builder.
On the Divi 5 services page, change the second blurb title to "Fixed-price audits".
The agent reads the block tree, finds the path, and update-builder-content changes that block with the content hash from the read. The page is snapshotted first.
Show me the Theme Builder footer and fix the year in the copyright line.
The footer template is read by its post id, edited in one write, and can be put back with rollback-operation.
Safety
Every Divi write has a way back.
A Divi layout lives in post_content with two builder flags beside it, all ordinary post data, so the standard post snapshot captures the whole layout before a write. A Divi 5 element write splices the original string by byte offsets, so every byte outside the touched block is kept exactly, and attributes go back through WordPress core's own block encoder.
Snapshot before every write
No tool that writes can skip it. The before-state is saved first, the change is applied second.
One-click undo
Restore a single change with rollback-operation or a whole agent run with rollback-session, from the agent or from wp-admin.
Content-hash guarded
A Divi 5 page that already holds a layout needs the hash the read returned. If someone edited the page in the meantime, the write is refused instead of overwriting their work.
Free or Pro
Part of WP MCP Pro.
The three builder tools (detect-builder, get-builder-content, update-builder-content) are part of WP MCP Pro. The free plugin still covers the rest of the site, including Gutenberg block editing, posts, pages, media, menus and the full snapshot and rollback engine, so you can try the safety model before you pay for builder editing.
WP MCP Pro starts at $49 a year for one site. See pricing for what each tier includes.
How to connect
Connect Divi MCP in four steps.
- 01Install WP MCP
Upload the free wpmcp plugin and activate it. It needs WordPress 6.9 or newer and PHP 8.1 or newer, and it runs entirely on your own server.
- 02Check the requirement
Divi pages on the site. Divi 4 reads and whole-layout writes work on the stored shortcodes; Divi 5 element editing, templates and the module catalog need Divi 5 loaded.
- 03Connect your client
Add the site to Claude Code, Claude Desktop, Cursor or any MCP client with a WordPress application password, or the WP-CLI stdio bridge locally. OAuth 2.1 with full or read-only access is there too, once the site owner switches it on.
- 04Ask for the change
Describe what you want done in Divi. WP MCP snapshots the target, makes the change, and leaves a Restore button next to it in wp-admin.
Step-by-step guides: Claude,Claude Code andCursor. The docscover the safety model in full.
Frequently asked
Divi MCP: questions, answered.
What is Divi MCP?
Divi MCP means driving the Divi builder from an AI agent over the Model Context Protocol. With WP MCP installed, Claude, Cursor or another MCP client can detect Divi pages, read a layout and change it, on your own server, with every write snapshotted first.
Does Divi MCP work with Divi 5?
Yes. Divi 5 is where the editing is most precise: WP MCP reads the layout as a block tree and edits one block at a time by path. Divi 4 layouts are shortcodes and are replaced whole, or you can open the page in the Divi 5 builder to convert it first.
Can the agent undo a Divi change?
Yes. The layout and the Divi flags are ordinary post data, so a snapshot is taken before each write and rollback-operation restores the exact layout. rollback-session unwinds a whole run of changes.
Is Divi MCP free?
Divi editing is part of WP MCP Pro. The free plugin includes Gutenberg editing and the snapshot engine, so the safety model can be tested on a free install first.
Does WP MCP generate Divi layouts from nothing?
It writes what the agent composes: a whole layout, or single blocks added by path. On Divi 5 the module catalog is readable, so the agent builds from the modules your site actually has rather than guessing names.
Will WP MCP convert my Divi 4 pages to Divi 5?
No. Divi 4 layouts are read and replaced whole as shortcodes. Element-by-element editing is a Divi 5 feature, and opening a page in the Divi 5 builder converts it first.
What happens if I edit the page while the agent is working?
A Divi 5 write needs the content hash from the read. If the page changed since then, the write is refused and nothing is overwritten, so the agent re-reads and tries again.
Does Divi MCP work with Claude, Claude Code and Cursor?
Yes. Claude Code and Cursor connect to WP MCP over HTTP with a WordPress application password, and Claude Desktop uses the desktop bundle from the WP MCP Connection screen. Clients that can only sign in with OAuth, such as the claude.ai custom connector, need OAuth switched on first with one line in wp-config.php, because it ships off. Once connected, the Divi tools are available in every client the same way.
Keep exploring
MCP for Divi (4 and 5) →
Read and edit Divi layouts, element by element on Divi 5 and whole-layout on Divi 4, with templates and the module catalog readable, every write reversible.
Divi AI vs MCP: What Each Does and When to Use It →
Divi AI vs MCP compared: what Divi AI and the Divi AI Agent do, what an MCP connection adds, Divi 4 versus Divi 5, undo, and which one fits which job.
Avada MCP →
An Avada MCP server gives an AI agent a safe way into Avada's Fusion Builder layouts.
WPBakery MCP →
A WPBakery MCP server turns the vc_row shortcodes behind your pages into something an AI agent can read and edit safely.
Bricks MCP →
A Bricks MCP server lets an AI agent read and write the element data behind a Bricks Builder page.
Beaver Builder MCP →
A Beaver Builder MCP server lets an AI agent work on the rows, columns and modules of a Beaver Builder page.
Browse all integrations, comparefree and Pro, read the docs, or see how the WordPress MCP server works.