Get the plugin
WP MCP/Guides/Guide

By · Published

Divi AI vs MCP: what each does and when to use it

Divi AI and an MCP connection both let an AI work on a Divi site, and people searching for “Divi AI” usually want to know which one does what. They are different kinds of tool. Divi AI is built into the builder by Elegant Themes. MCP is an open protocol that lets an AI client you choose connect to your WordPress site and call tools on it. This guide compares them on what they do, where they work, how they handle mistakes, and which fits which job.

Every claim about Divi below is from Elegant Themes’ own pages as they read in November 2026. Prices are left out on purpose: plans and AI allowances change, and a number copied into an article goes stale quickly.

What is the difference between Divi AI and MCP? Divi AI works inside the Divi builder, with models Elegant Themes picked, on the page in front of you. An MCP connection lets an outside client such as Claude or Cursor call tools on your site, so one agent can work across Divi layouts, Theme Builder templates and the rest of WordPress. One is a feature of the builder. The other is a connection to your site.

What Divi AI does

According to Elegant Themes’ Divi AI page, the built-in AI covers these kinds of work:

  • Text: write and improve copy, change its tone and length, translate it and fix grammar.
  • Images: generate images from a prompt, edit existing ones, extend an image past its frame and upscale it.
  • Code: write HTML, CSS and JavaScript in the Code module and the CSS fields.
  • Layouts: generate new pages and sections, styled and filled with content and images.
  • Whole sites: Divi Quick Sites generates a full site from a few prompts.

The strength is that it lives where you already design. There is no API key and nothing to install on your computer.

What the Divi AI Agent adds in Divi 5

Divi 5 adds the Divi AI Agent, a chat window you open from the AI icon in the Visual Builder. Elegant Themes’ article on what the agent can do says it has more than 190 tools for Divi and WordPress, and lists:

  • Reading, adding, editing, moving, cloning and removing sections, rows, columns and modules.
  • Presets, global variables and global colors.
  • Pages, posts, menus, Theme Builder templates, Theme Options and the Divi Library.
  • Images from a prompt or from Unsplash, loops and dynamic content.

The same article states two limits worth knowing. Requests made outside the builder use a narrower set of abilities than requests made inside it. And destructive tools pause and ask you to approve them before they run, which is a sensible default.

Elegant Themes also says agent usage is metered separately from the flat Divi AI plan, with a monthly allowance. Check the pricing page before you plan large jobs around it.

Where MCP fits

MCP, the Model Context Protocol, is how an AI client discovers and calls tools on a server. If the idea is new, read what an MCP server is. For Divi, the server on your site exposes layouts as tools, and the client decides which ones to call.

As of November 2026, Divi does not offer MCP itself. The agent article says the Divi AI Agent does not connect to outside tools through MCP and that MCP support has not shipped, and the Divi 5.15 release notes list surfacing Divi’s AI tools as an MCP under what is coming next.

WP MCP is an independent WordPress plugin, not made by or affiliated with Elegant Themes. It serves an MCP endpoint at https://your-site.com/wp-json/mcp/wpmcp-server, and its Pro tier adds three builder tools that cover Divi: detect-builder, get-builder-content and update-builder-content. The full list is on Divi MCP and the Divi integration reference.

How it handles the two Divi formats:

  • Divi 5 stores a layout as block markup. WP MCP parses it into a tree, gives every block a dotted path such as 0.1.0, and changes one element at a time: update, add, remove or move by path. Every byte outside the touched block is kept as it was.
  • Divi 4 stores a layout as shortcodes. WP MCP reads it and replaces the whole layout in one write. Opening a page in the Divi 5 builder converts it, after which element edits work.
  • Templates and catalog: with scope set, the read returns the Divi Library, the Theme Builder header, body and footer templates, and the Divi 5 module catalog.

A read of a Divi 5 page looks like this:

{
  "jsonrpc": "2.0", "id": 4, "method": "tools/call",
  "params": {
    "name": "wpmcp-get-builder-content",
    "arguments": { "post_id": 21 }
  }
}

The reply carries the block tree with a path per block and a content hash. The agent then calls update-builder-content with builder set to divi, an operation such as update, the block’s path, the new attrs and the expected_hash from the read. If someone edited the page in the meantime, the hash no longer matches and the write is refused instead of overwriting their work.

Side by side

Divi AI and the Divi AI Agent MCP connection with WP MCP
Where you work Inside the Divi builder In Claude, Cursor or another MCP client
Which model Chosen by Elegant Themes Chosen by you
Divi versions Divi AI in the builder; the agent is a Divi 5 feature Divi 5 element by element; Divi 4 whole layout
Scope The page in the builder, plus site items the agent can reach Divi layouts, templates and the rest of WordPress
Best at Copy, images, code snippets, new layouts, quick sites Repeated edits across many pages, mixed jobs across the site
Billing Divi AI plan, with agent usage metered WP MCP Pro for the builder tools, plus your own AI client
Undo The builder’s own history; approval before destructive tools A snapshot before every write, undo per operation or per session
MCP Not shipped as of November 2026 The whole connection is MCP

Undo and safety

This is where the two differ most on a live site.

When you work in the builder, you see each change as it happens and you save when you are happy. An MCP agent can change many pages in one session while you are not watching, so recovery matters more.

WP MCP snapshots every supported write before it runs. A Divi layout lives in post_content with Divi’s builder flags beside it, all ordinary post data, so the standard post snapshot captures the whole layout. You can list the changes and undo one from the AI:

{
  "jsonrpc": "2.0", "id": 9, "method": "tools/call",
  "params": { "name": "wpmcp-list-operations", "arguments": {} }
}
{
  "jsonrpc": "2.0", "id": 10, "method": "tools/call",
  "params": { "name": "wpmcp-rollback-operation", "arguments": { "operation_id": "OPERATION_ID" } }
}

rollback-session unwinds everything one agent session did, and the wp-admin history screen has a Restore button per operation. The free plugin keeps the last 20 operations of history, and an active Pro licence makes it unlimited. A few kinds of change cannot be snapshotted, such as package updates and raw database writes, and WP MCP says so in its response. More in undoing changes in WordPress.

Elegant Themes’ agent article describes approval before destructive tools, but it does not describe how to roll back an agent’s edits after they run. If you let any agent change live pages, test the undo path on a copy first.

Which one should you use?

Use Divi AI when:

  • You are in the builder and want copy, an image, a CSS snippet or a new section right there.
  • You want a first draft of a whole site from Divi Quick Sites.
  • You want no setup outside Divi.

Use an MCP connection when:

  • The job spans many pages: the same phone number in forty modules, a button label across every landing page, a footer line in the Theme Builder template.
  • You want to pick the model and keep working in Claude Code, Claude Desktop or Cursor. The client comparison shows how they differ.
  • The task is wider than Divi: posts, SEO fields, forms, media and WooCommerce in one conversation. WP MCP has 407 tools in total (274 free and 133 Pro), though a site sees fewer when optional plugins are inactive.
  • You need an undo for each operation or for a whole session.

They also work well together. Draft a layout with Divi AI in the builder, then ask an agent to roll the same change out across the site, with a snapshot before each write.

Connecting a client to WP MCP

If you want to try the MCP route on a Divi site:

  1. Install the WP MCP plugin on WordPress 6.9 or later with PHP 8.1 or later. The Divi tools need WP MCP Pro; pricing lists the plans.
  2. Create a WordPress application password for a dedicated user. The application password guide shows how.
  3. Point your client at https://your-site.com/wp-json/mcp/wpmcp-server with that password. Claude Code takes it in one command.
  4. Ask for something read-only first, such as “List my Divi pages and tell me which are still on Divi 4.”
  5. Then try a small write on a test page, and undo it.

The Bricks and Divi walkthrough goes through a full read, edit, verify and rollback.

The short answer

Divi AI is a feature of the builder, strongest for copy, images, code and new layouts on the page you have open, and the Divi AI Agent extends it to edits across a Divi 5 site from a chat in the builder. MCP is a connection that lets an agent you choose work across Divi and the rest of WordPress, which suits large and repeated jobs, provided you can undo. Elegant Themes has said MCP for Divi is coming; WP MCP offers it now, as an independent plugin.

For the Divi tools in WP MCP, start at Divi MCP. If you also run Elementor sites, Elementor AI vs MCP makes the same comparison there.

Common questions

What is Divi AI?

Divi AI is the AI built into the Divi builder by Elegant Themes. Per its own pages it writes and edits text, creates and edits images, writes HTML, CSS and JavaScript, generates layouts and sections, and builds whole sites with Divi Quick Sites. Divi 5 adds the Divi AI Agent, a chat in the Visual Builder that can edit the layout and manage parts of the site.

Does Divi AI support MCP?

Not yet, as of November 2026. Elegant Themes' help article on the Divi AI Agent says it does not connect to outside tools through MCP and that MCP support has not shipped, and the Divi 5.15 release notes list surfacing Divi's AI tools as an MCP under what is coming next. Check their pages for the current state.

What is the difference between Divi AI and MCP?

Divi AI works inside the Divi builder with the models Elegant Themes chose. MCP is an open protocol that lets an outside AI client you pick, such as Claude or Cursor, connect to your site and call tools. With WP MCP the agent can work on Divi pages and on the rest of WordPress in one conversation.

Can I use Claude or ChatGPT to edit Divi pages?

Yes, through an MCP server on the site. WP MCP Pro reads Divi 4 and Divi 5 layouts and edits Divi 5 pages one element at a time. Claude Code, Claude Desktop and Cursor are well tested with WP MCP. ChatGPT needs OAuth and is not fully tested.

Does WP MCP work with Divi 4?

Yes, with a difference. Divi 4 stores a layout as shortcodes, so WP MCP reads it and replaces the whole layout in one write. Element-by-element edits by path need a Divi 5 layout. Every write on either version is snapshotted first and can be undone.

Can I undo what an AI agent changed in Divi?

With WP MCP, yes. A Divi layout is ordinary post data, so the post snapshot taken before every write captures it, and rollback-operation or rollback-session puts it back. The free plugin keeps the last 20 operations of history; with an active Pro licence it is unlimited. Elegant Themes' agent article does not describe its own undo, so test it before you rely on it.

All WP MCP guides, or see every plugin integration. Topic: Other page builders.