launch week Respira for WordPress is live on DevHunt until Monday. Live on DevHunt this week. See the launch

Divi MCP server, with undo on every edit.

A Divi MCP server lets Claude, ChatGPT or Cursor read and edit Divi 4 and Divi 5 pages on a live WordPress site. With Respira every edit lands on a copy first, and you can undo it for 90 days.

Start free Connect in one command

7 days free. No card. Runs on the AI subscription you already have.

Support
Full
Divi tools
Core set
Latest release touching it
9.1.32
Releases touching it
173

Respira is an independent MCP server. Not affiliated with, endorsed by, or sponsored by Elegant Themes, Inc. Divi is a trademark of Elegant Themes, Inc.

What works today. What still needs you.

Read from the current MCP server release, first-class reads and writes across the builder structure.

Works now

  • Divi 5 block-based layouts (divi/* blocks) read and write through native block tools.
  • Divi 4 shortcode pages: parser walks post_content, _et_pb_page_layout, _et_pb_layout_content, _et_pb_page_content, four meta sources for maximum compatibility.
  • 60+ Divi 5 module schemas (sections, rows, columns, text, image, button, heading, blurb, contact forms, dozens more).
  • 13-point payload validation: context checks, nesting rules, flexColumnStructure counts, variable references, 16 common mistake patterns caught BEFORE write.
  • Auto-wraps bare modules in Section → Row → Column so the Visual Builder never sees invalid nesting.
  • Color tokens map to Divi 5's native et_global_colors option. Typography / spacing / breakpoints use Respira-managed options (respira_divi_typography_variables, etc) since Divi has no native equivalents.
  • Divi Migrator (Divi's own D4→D5 converter) is detected and surfaced through the Migration Copilot at /divi-5-migration-copilot.
  • Divi 5 writes are native by default. Every agent write to a Divi 5 page (build_page, inject_builder_content, update_element, update_module, batch_update, apply_builder_patch and the add_* shortcuts) takes allow_inline_styles and allow_code_modules, both false unless you say otherwise. A style Divi 5 has a design setting for is written as that attribute, whether it arrives as a settings key, a CSS name or a style="" on the module's wrapper: text transform, italic, underline, border width, style and colour, opacity, height, z-index, overflow and more. A style with no native place is not written and comes back as unmapped_styles, one entry per style with the element, the property, the value and the reason. A write that adds a divi/code module is refused and names the native module to use. What a page already stores is left as it is, and Divi 4 is unchanged.

Where a human still steps in

  • Respira does NOT convert Divi 4 to Divi 5 on its own. Use Divi's native Migrator; Respira helps plan and validate.
  • A colour on part of a sentence, a