Divi 5 MCP: edit pages and scoped Theme Builder layouts.

Divi 5 content your team can keep editing

The Divi 5 integration covers three distinct jobs: page composition, Theme Builder templates and theme configuration. EMCP Pro exposes native module schemas and document trees for page work, plus dedicated tools for assignments and curated option updates.

Work with the native design model

Create reusable library layouts or header, body and footer layouts for the Theme Builder. Inspect condition choices before assigning a template, and keep matching focused on the intended pages. Theme Options have their own schema and concurrency hash, so a page edit does not require replacing global configuration.

Connect your AI to the right tools

Open EMCP Tools > Page Builders and select this standalone builder. Gutenberg and enabled block packs remain available. Reconnect your MCP client, read context and schemas, and enable the write tools needed for the task. Start with a draft and inspect the native editor. Available in EMCP 3.17.0. Check compatibility before updating the vendor builder; an unsupported version can prevent its tools from appearing.

Read the Divi 5 tool reference for operations and tested boundaries. The page-builder setup guide explains selection and Gutenberg coexistence.

Version-specific authoring guidance

The bundled skill includes EMCP workflows and credits Shashank Gupta / DiviLove for the referenced Divi 5 skill. Installed module schemas take precedence over examples for another Divi version.

Walkthrough: a footer for one Divi 5 landing page

With EMCP Pro and supported Divi 5.13.x active, try: “Prepare a footer for this landing page only. Keep the default header and every other page’s assignments unchanged. Show me the proposed condition before enabling it.”

1. Read divi-get-theme-builder and divi-list-template-conditions. Record the current template assignments and theme_builder_hash, and identify the intended page by its ID.
2. Create an unattached footer with divi-create-theme-layout. Discover module schemas before editing its native tree. Create a disabled template and attach the footer with only the supported condition for the selected page, using the current hash for each change.
3. Re-read assignments before enabling the reviewed template. Inspect the target page and another page that should retain its original footer in the native editor and frontend.

This illustrates the documented Divi workflow; it is not a live test result. The adapter does not convert Divi 4 shortcode layouts, and global preset authoring is outside its write scope.