JHMG AI Editor for Divi 5

Divi 5 stores a page as strict block data. A general-purpose assistant can save something that looks right in the code and still cannot be opened in the builder. This plugin gives your assistant Divi 5's real rules, proven section patterns and a checker that refuses a broken layout with the exact reason, so the assistant can fix it and save a page that works.

1. Give your assistant a screenshot, the address of a page, or the page's HTML.
2. Ask it to build that page in Divi 5. It is always saved as a draft.
3. It reads this plugin's guides, picks matching section patterns, a design language and a style kit, writes the layout, and the checker tests it before it is saved.
4. Review the draft, swap in your own text and images, and publish.

1. Connect your own AI assistant (Claude, ChatGPT, Cursor or Copilot) to your site with one key. It is copy and paste, and takes about two minutes.
2. Tell it what you want in plain English, for example "change the phone number on the Contact page" or "build me a landing page for my dental clinic".
3. The plugin's built-in guides and proven section patterns steer the AI, so it builds real, good-looking Divi 5 pages instead of guessing. It uses your own Media Library images when it can.
4. Before anything is saved, a built-in checker tests the page against fixed rules. If something is wrong, the change is refused with the exact reason and the AI fixes it. If it is fine, it is saved, and the previous version is kept so you can undo.

• The checker is not AI. It follows fixed rules: same page in, same verdict out. The AI can be creative, but every save it makes is checked first, so a broken page is never saved by an AI edit.
• It knows Divi 5 well. The checker knows more than 80 Divi 5 block types (modules, sections, rows and columns) and which ones are allowed inside which.
• Rules come from real Divi 5, not guesses. The rules come from real Divi 5 page exports and, for 24 newer modules (and their child items), from Divi's own module definitions, verified by rendering them in real Divi 5.15.
• Understands Divi 5.15 components. Pages that use shared components (reusable sections, rows and modules, including ones with Slots) can be read and edited. Your AI can see which components your site has and is told when a change would do nothing because the component owns that part.
• Warns before a page is hollowed out. If a save would remove more than half of a page's text, images or modules, your AI is told and can put it back. Nothing is stopped: a deliberate rewrite is still yours to make.
• Small changes stay small. Changing one phone number replaces just that text. The rest of the page is not rebuilt or touched.
• Preview before saving. Your AI can ask what a change would do before it saves anything. It gets a list of the blocks and settings that would change, and the checker's verdict. Nothing is saved until it repeats the request for real.
• Matches your site. Your AI can look up your site's own Divi colors and presets and reuse them, and it is told when a page uses one your site does not have. It cannot create or change presets or colors: that stays in Divi's Visual Builder.
• Proven building blocks. 75 ready-made section patterns (heroes, feature grids, testimonials, contact forms and more), each one tested against the checker, plus landing-page guidance on the order of sections, headlines and calls to action.
• Consistent looks. Ten design languages (editorial, glass dark, organic warm, tech mono and more) and 40 style kits set the exact look of buttons, cards, accordions, toggles, contact forms and image corners, so a whole page matches.
• Sensible images. The AI looks in your Media Library first. When nothing there fits, it uses a built-in pack of 44 original images that ships with the plugin.
• One-click undo. The previous version of each page or Divi Project the AI changes is kept (up to the last 10). Restore it from the plugin's Dashboard with one click, or just ask your AI to undo.
• Works with the AI assistant you already use. Claude, ChatGPT, Gemini, Cursor, VS Code Copilot, or any assistant that supports MCP.
• Nothing leaves your site through the plugin. It uses no third-party services. Your AI assistant talks directly to your own site.

• "Change the phone number on the Contact page to 555-0142."
• "Make the main heading on the Home page say 'Fresh bread every morning'."
• "Build me a landing page for my dental clinic, with a booking button and three patient reviews."
• "Add a section with our opening hours under the hero on the About page."
• "Undo the last change you made to the Services page."

Read and check:

• list_divi_pages: list the pages built with Divi 5 that you can edit (pass post_type project to list Divi Projects).
• get_page_layout: read the current layout of a page or Divi Project. For a big page your assistant can read just an outline (every block with its place, size and the start of its text) or one block, which costs a fraction of reading the whole page.
• list_global_styles: list your site's own Divi colors and presets so the AI can reuse them (read-only).
• get_site_structure: list your site's custom post types, taxonomies, image sizes, Divi 5.15 components (name, kind, Slots, how many pages use each), on request the names and ids of your site's navigation lists and of your most used categories and tags (so a list on a page can name them), and Advanced Custom Fields field groups so pages fit your site (read-only: field names and the keys your posts use, never values here or theme files; available over MCP and the REST API, not in the ChatGPT Action).
• get_custom_fields: read the custom fields of one page or Divi Project you can edit, with their values, so your assistant can write copy that fits and use the right field names (read-only: keys WordPress protects, or that look like passwords, API keys or other secrets, are never shown; available over MCP and the REST API, not in the ChatGPT Action).
• list_products: list and count your WooCommerce products with their prices, stock status and categories (read-only; needs the permission to edit products; available over MCP and the REST API, not in the ChatGPT Action).
• get_product: read one WooCommerce product in full, including its variations (read-only; never downloadable files, purchase notes or custom fields).
• validate_layout: check a layout without saving anything.

• edit_page_content: change one piece of text (an email, phone number, price or sentence) without rebuilding the page or Divi Project. Add dry_run to preview the change without saving it.
• update_page_layout: save a new layout for a page or Divi Project, after the checker approves it. Add dry_run to preview what would change without saving it.
• create_page: create a new page. It is always saved as a draft for you to review and publish.
• html_to_divi: turn HTML you already have (a page your assistant or another tool wrote) into a Divi 5 layout: the structure, all the copy, the links and the images, plus the basic colors, fonts and spacing where Divi can show them and the text stays readable. It previews by default and saves a new draft only when asked. Scripts, forms, embeds and site navigation are never converted and are listed in a report (available over MCP and the REST API, not in the ChatGPT Action).
• lab_build: lets your assistant use Lab (see "Lab: answer a few questions, see a preview" below). It can read a Lab brief you started and fill in the words, telling it which parts are still empty and never overwriting what you changed meanwhile, or build a whole page from a short brief. It is always saved as a draft, after the checker approves it. New: results with a given assistant have not been confirmed yet (available over MCP and the REST API, not in the ChatGPT Action).

• list_page_history, get_page_history_entry, restore_page_version: see the saved earlier versions of a page or Divi Project and bring one back.

• get_style_guide: how to build styled Divi 5 layouts, using real Divi 5 settings.
• get_landing_guide: how to build a landing page that turns visitors into customers.
• get_site_guide: how to plan a site with several pages that link to each other.
• get_section_recipes: the 75 ready-made section patterns.
• get_image_guide: how to pick the right image for each section, including the built-in image pack.

• list_media_images: look through the images already in your Media Library (read-only; nothing is uploaded, changed or deleted).

On WordPress 6.9 and later the plugin also registers these abilities in the jhmg-ai-editor category, for any assistant or MCP adapter that can call WordPress abilities. They check the same permissions as the tools above (a signed-in user who can edit pages, and edit permission on the page itself) and nothing is public.

• Guidance: get-style-guide, get-landing-guide, get-site-guide, get-image-guide, get-section-recipes (filter by role, layout, mood, density and persuasion stage), get-design-languages and get-variety-advice.
• Checks: validate-layout and check-design.
• Pages and undo: list-divi-pages, get-page-layout, update-page-layout, edit-page-content, create-page, list-page-history, get-page-history-entry and restore-page-version. Every save is still checked first.

New in 4.19.0. The Lab tab in the plugin's admin page builds a page without writing a prompt. You answer a few questions (what the page is for, the look, the sections, your words and pictures), see a live preview, and save a draft page. The page is made from the plugin's proven section layouts and is checked before it is saved, like every other change. Your assistant can also fill in the words of a brief you started, through the lab_build tool, and it never overwrites what you changed in the meantime. Lab is new, and results with any particular assistant have not been confirmed yet.

The plugin includes a pack of 44 original images (hero backgrounds, card and section images, people placeholders and logo placeholders) made for this plugin and bundled inside it. Your AI uses your own Media Library images first and the built-in pack when nothing fits. Nothing is downloaded from other websites.

A separate, optional Pro add-on is available (details at https://divi5lab.com/plugins/divi-5-ai-editor). This plugin is complete on its own and works the same without it.

• Claude on the web (claude.ai custom connector), by signing in to your own site (turn it on in Settings; needs a public https address)
• Claude (Desktop and Claude Code), through MCP (Claude Desktop needs Node.js installed)
• Gemini CLI, through MCP
• Cursor and Windsurf, through MCP
• VS Code with GitHub Copilot, through MCP
• ChatGPT, through a custom connector that signs in with your WordPress login (needs Developer mode on a paid ChatGPT plan; set up for OpenAI's published requirements but not yet confirmed by us), or, while OpenAI still allows it, a custom GPT Action (OpenAPI)
• Any other MCP client, or any HTTP client through the REST API

The plugin stores these things in your own WordPress database:

• The API key (and which user it belongs to).
• Only if you turn on sign-in for Claude on the web: the apps that registered, and their access and refresh tokens, in a table in your own database. The tokens are stored only as one-way hashes and you can disconnect any app, or turn the feature off and remove everything, from the Settings screen.
• An activity log of AI actions: the action, the page ID, the result, the assistant's name (or, when it is not recognised, the first 80 characters of its user-agent string) and a hashed IP address (hashed with your site's own secret key, so the IP itself is not stored). You can clear it from the Settings screen.
• Whether you chose "Maybe later" or "Don't ask again" on the review reminder (one value per user, shown only on the plugin's Dashboard after the plugin has saved at least 5 changes). Nothing is sent when you choose, and the reminder's link only opens this plugin's own page on WordPress.org if you click it.
• Page history for undo: up to the last 10 previous versions of each Divi page that an AI tool changes (fewer for very large pages, about 768 KB per page at most). This includes changes made by other tools, such as an application password or the REST API: the page's earlier content is kept, with where the change came from (the name of the ability, or the name you gave the application password; never a password or key). It is kept in a table in your own database, and you can switch each source off in Settings.

No. The API key works as the WordPress user who created it, and the AI can only use this plugin's tools. Every request checks that this user can still edit pages, and every page listing, read or change, every new page and every Media Library lookup re-checks that user's WordPress permissions (pages they cannot edit are not even listed). The tools can only list, read, check, edit and undo the content of pages and Divi Projects, create pages (as drafts), read Media Library images (read-only), read your site's Divi presets and colors (read-only), read how your site is set up (post types, taxonomies, image sizes and ACF field definitions, read-only), read the custom fields of a page or Divi Project you can edit (read-only), and read your WooCommerce products (read-only). They cannot install plugins, change users, settings, menus or the front page, or run PHP or other server-side code.

No. The checker refuses any layout that contains custom CSS, a Divi Code module, script, style or iframe markup, a javascript: link or an event attribute, and the plugin has no tool that saves CSS, JavaScript or PHP or changes site settings. Anything already on a page, for example custom CSS you added in the Visual Builder, is kept: the AI cannot add or change code (it can only remove it).

From your own Media Library first. When nothing there fits, the AI uses the built-in image pack that ships inside the plugin. Nothing is downloaded from third-party websites.

No. The plugin does not send your data anywhere and uses no third-party services. Your AI assistant connects directly to your site with your key. The page content your assistant reads is handled by the AI service you chose (for example Anthropic or OpenAI), under that service's own terms.

The AI can make mistakes, but a broken page is never saved by an AI edit. The checker runs before every save. If a layout breaks a rule, it is refused, nothing is saved, and the AI gets the exact reason so it can fix it. If you do not like a change that was saved, restore the previous version from the Dashboard: undo puts back your own earlier version exactly as it was, and when your AI assistant does the restore it is told whether that version passes the checker.

The key is a long random code stored in your WordPress database and shown only to administrators on the plugin's Settings screen. Keep it private, like a password. You can make a new one at any time with the Regenerate button, which stops the old one from working.

Every save is checked by a fixed set of rules (no AI is involved in the check) and a broken layout is refused. You can ask your assistant for a preview first (a dry run shows what would change and saves nothing), new pages are always drafts, and every save can be undone from the Dashboard. The plugin cannot change your site settings, users or plugins, and cannot add custom code. If you want a stricter rule, turn on Approval mode in Settings ("Require a preview before every save"): your assistant must then preview every edit to a page's content before it can save it. Restoring an earlier version is the undo and needs no preview.

The plugin edits the Divi 5 layout data directly, so it is faster and more precise, every change is checked before it is saved, and every save can be undone. An assistant that drives a browser works from screenshots and clicks, and nothing stops it from saving a broken layout.

No. The check runs in PHP on your own server. Your assistant only reads what the plugin sends back: the tool list it loads once per conversation (about 4,000 tokens), reading the page it is editing (about 300 to 16,500 tokens depending on its size), and the details of what was wrong when a layout is refused (about 400 tokens for one unknown block). These are estimates; the real count depends on the model.

Yes. It has been tested with Gemini CLI: copy the one command from the Gemini tab on the Settings screen. Any assistant that supports remote MCP servers can connect.

Yes, for reading. Your assistant can list and count your products and read one product in full (name, description, price, stock, categories, variations), so it can answer store questions and write shop pages that match your catalogue. It never changes a product: prices and stock are not touched by this plugin.

It can read how your site is set up: custom post types, taxonomies, image sizes, on request the names and ids of your site's navigation lists (never their links) and of your most used categories, tags and other public taxonomy terms, and, when Advanced Custom Fields is active, its field groups and fields (names, labels, types and choices). It reads custom field values only when your assistant asks about one specific page or Project you can edit, never ones WordPress protects or that look like passwords, API keys or other secrets, and it never reads your theme files or functions.php. This is available to assistants that connect over MCP or the REST API, not to the ChatGPT Action.

No. It reads the ones you already have, reuses them, and warns when a layout uses one your site does not have. It never creates, changes or deletes them.

Assistants that run on your own computer (Claude Code, Claude Desktop, Cursor, VS Code, Gemini CLI) should be able to reach a local site. Use the exact http:// address your local site shows, and turn on pretty permalinks. ChatGPT and other assistants that run in the cloud cannot reach a local site; they need a public https:// address. Local tools such as Laragon, Local or MAMP work with the assistants that run on your computer.

Claude Desktop connects through a small helper that needs Node.js. Install the LTS version from nodejs.org, then fully quit Claude Desktop (Cmd+Q) and open it again. The Claude tab on the Settings screen has the details.

Some hosts run a firewall rule (for example ModSecurity's "too many 404 responses from same IP") that bans an address after about ten "not found" answers. The plugin does not cause 404s on its own address: when an assistant opens the connection with a GET request, it answers 405 (Method Not Allowed), which is what the MCP specification asks for and which these rules do not count. Some connection helpers, such as the mcp-remote helper that Claude Desktop uses, also look for sign-in information at addresses like /.well-known/oauth-protected-resource. If Claude sign-in is switched off, there is nothing at those addresses, so WordPress answers 404, and several reconnects in a row can still add up. If you get banned, ask your host to allow your own IP address, or to raise the limit for it. Another option is a small connector that a user, Brandon McCloskey (Web Design by Brandon), has shared as a public GitHub Gist called "wp-mcp-bridge" (MIT licence, needs Node.js 18 or newer). It only sends requests to the connection address, so it never causes 404s. It is not made or checked by us, and it handles your API key, so read any script like this before you use it.

The plugin has no AI of its own, so it adds no AI cost. Your own assistant does the thinking, and its usage counts against whatever plan or API account you already use with it. A small edit costs very little; building a whole page costs more, because your assistant writes the layout. The plugin's checking runs on your server and is free.

Divi AI is Elegant Themes' own AI inside the Divi builder. This plugin does something different: it lets the AI assistant you already use (Claude, ChatGPT, Gemini, Cursor, Copilot) read and edit your Divi 5 pages from outside the builder, in plain English. Every change is checked before it is saved and can be undone.

It is built for one job: editing Divi 5 layouts safely on a live site. It knows the Divi 5 page format, refuses any layout that is broken before it is saved, offers a preview of every change, makes new pages drafts, and keeps an undo history. It does not run code on your site and does not change your site settings.

Divi has announced its own MCP, which is not released yet, so this plugin has not been tested against it. A builder builds pages. This plugin is designed to add what a builder does not: ten design languages and 75 proven section patterns to design from, a deterministic checker that refuses a broken layout with the exact reason, an advisory design check (readability, Divi's stock look, repeated sections), and undo for every change, even ones made by other tools. The idea is to use both: ask your assistant to read this plugin's design guidance before it builds, build with any tool, then run the design check and fix what it finds.

Yes. The plugin adds a Model Context Protocol (MCP) server to your own WordPress site, with 22 tools made for Divi 5 pages and Divi Projects. Any MCP client can use it: Claude, Cursor, Windsurf, VS Code with GitHub Copilot, Gemini CLI and others. ChatGPT connects through a custom connector that signs in with your WordPress login and gets every tool (the older custom GPT Action offers most of them).

Yes, through your AI assistant. Give the assistant a screenshot or the address of a page and ask it to build that page in Divi 5. It uses this plugin's guides and section patterns, writes a layout, and the checker tests it before it is saved as a draft. The plugin itself does not look at images or fetch websites, and photos are never copied, so expect a close match to the design with your own images and text swapped in.

Yes. On the Settings screen, turn on sign-in for Claude and copy the address it shows. In claude.ai open Customize → Connectors, choose "Add custom connector" and paste the address. Claude opens your own site: you sign in to WordPress and press Allow. There is no Node.js, no config file and no API key to paste. Claude then works as you, with exactly the permissions your account has, and every save is still checked and undoable. You can disconnect it from the Settings screen at any time. It needs your site to be reachable over public https (Claude connects from the internet), so it does not work on a local site; the other ways of connecting are unchanged. It is off until you turn it on.

Yes, for the content. Give your assistant the HTML (for example a page it wrote for you) and it can convert it with html_to_divi: the structure (sections, columns for card grids, headings, text, buttons, images), every word and every link. It previews first and tells you what was not converted; with one more step it saves a draft. Scripts, forms, embedded videos, site navigation and CSS code are never converted; it carries the basic colors, fonts and spacing of the HTML where Divi can show them, and never a color that would make text hard to read; linked stylesheets are not fetched, so a page that keeps its styling in an external file comes out plainer; and images become placeholders for you to replace with your own. It does not fetch web addresses. For a pixel-accurate copy of a live web page you need a dedicated URL-to-Divi converter instead.

Yes. Ask your assistant to rename the page and it uses the update_page_layout tool with a new title (the page can be a Divi page or a Divi Project). This changes the WordPress page title: what shows in the page list and, by default, the browser tab. It is not the same as the big headline (the h1) inside the page layout, which is part of the layout and is changed separately; if the two match, your assistant should ask whether you want both changed. It changes only the title: not the page address (slug). A title change is not covered by Undo, so your assistant tells you the old title when it changes one, and a title change is not listed under "Recent AI edits" on the dashboard, because that list shows saved versions you can restore and a title change has none. You can ask for a preview first.

No. Divi 4 stores pages as shortcodes. This plugin is made for the Divi 5 page format.

Not yet. The checker only knows Divi's own modules, so it refuses to save a page that contains a module from another plugin (for example Divi Pixel or Divi Plus), even for a text change. Your assistant can still read such a page, and it can edit every other page. Nothing is changed on a refused save, and the reply tells your assistant exactly which block was not recognised.

It works on any standard WordPress site, including staging sites. Multisite is not officially supported yet.

No. The plugin adds no scripts or styles to your public pages. It only adds its admin screen and the connection endpoints your AI assistant uses.