Run an MCP server for Divi.

Live status

What ships today for Divi

Everything below is read from this repo at build time: tool registrations come from the MCP server adapter files; changelog entries are filtered from the same source the /releases timeline uses.

Last 5 releases mentioning Divi

• 7.4.11 Jun 17, 2026
  • Divi 5 Custom CSS edits stop reporting a false warning. update_module wrote the top-level css group correctly but flagged it unknown_attribute_group, which read as a silent drop. css is a universal Divi 5 group and is no
  • build_page no longer rejects real full pages. The 200-element limit blocked a typical multi-section page (a 14-section Divi page is ~200+ nodes). Raised to 1000 (still filterable)
• 7.4.9 Jun 16, 2026
  • Divi 5 Heading no longer renders "This content cannot be displayed." When a heading's text was supplied via a generic content field, the level detection grabbed that text and wrote it into the heading-level attribute (wh
• 7.4.8 Jun 16, 2026
  • Divi 5 no longer writes "Unknown Module" blocks from invented type names. When an AI described a page using made-up layout names (hero_section, feature_grid, cta_section) instead of real Divi types, Respira wrote them ve
• 7.4.6 Jun 15, 2026
  • In-place Divi 5 edits no longer collapse settings-shaped multi-element content. validate_render_critical_attrs is now settings-aware, so the validated inject path (used when an agent rebuilds an existing page) accepts th
• 7.4.5 Jun 14, 2026
  • FIX: Divi 5 builds collapsed to plain text / a raw code block instead of native editable sections and modules. A new normalization pass lifts loose content synonyms (heading text, button text + url, paragraph content, ne
  • FIX: native Divi 5 modules could render as empty containers. The normalized content is now written to the settings bucket (which the complexifier expands into the title.innerContent.desktop.value / content.innerContent.d
  • FIX: a build whose attributes.content was a scalar string (e.g. divi/text) could fatal in the Divi 5 attribute-group deep-merge. The merge now runs only when the existing group is itself an array.

View all 84 releases that touched Divi →

Tools

Divi uses the universal toolset

Divi edits run through Respira's universal tools: respira_find_element, respira_update_element, respira_update_page (for full-page replacement only), respira_get_snapshot, and respira_create_page_duplicate. See the complete tool catalog.

Example prompts

Three prompts you can paste right now

Each one assumes Respira is connected to your WordPress site through the MCP server below. Copy a prompt, paste into your MCP client, run.

Read the Divi 5 global color palette. Find every page where a heading uses a custom hex color instead of a palette reference. Suggest the closest palette entry for each and show me the list before changing anything.

For every Divi 4 page in the "/offers/" path, find the et_pb_button shortcodes and replace the button text "Buy now" with "Start free trial". Snapshot each page first.

Run the Migration Copilot dry-run for the page slug "pricing". Report what would convert cleanly, what needs review, and what would fail.

Setup

Connect Respira's MCP server

Drop this into your MCP client config (Claude Desktop, Cursor, Codex, Windsurf — any MCP-compatible client). Generate an API key from your Respira dashboard first.

{
  "mcpServers": {
    "respira-wordpress": {
      "command": "npx",
      "args": ["-y", "@respira/wordpress-mcp-server"],
      "env": {
        "WORDPRESS_URL": "https://yoursite.com",
        "WORDPRESS_API_KEY": "respira_your_api_key_here"
      }
    }
  }
}

macOS Claude Desktop: this belongs in claude_desktop_config.json, not config.json. On some versions the "Edit Config" button opens config.json — a separate preferences file in the same folder that is not read for MCP servers — so the paste appears to do nothing. If the server doesn't show up after restarting, edit the right file directly: open -a TextEdit ~/Library/Application\ Support/Claude/claude_desktop_config.json