Connect
Link Claude Code, Cursor, Codex, or any MCP client to your WordPress site through Respira.
Respira reads and writes both Divi 5 block layouts and Divi 4 shortcodes through the same MCP interface. 60+ module schemas, 13-point validation, and duplicate-before-edit safety for every change.
Workflow
Link Claude Code, Cursor, Codex, or any MCP client to your WordPress site through Respira.
Respira detects Divi 4 (shortcodes) vs Divi 5 (blocks) automatically per page.
Edits happen on a duplicate first. Your live page is never touched until you approve.
13-point validation catches nesting errors, missing columns, and structure issues before save.
Review the diff, approve the change, or restore the snapshot. Full audit trail.
Divi 5 stores pages as divi/* WordPress blocks. Respira parses, validates, and serializes the full block tree so Visual Builder content stays valid after every AI edit.
Full block definitions for sections, rows, columns, text, image, button, heading, blurb, contact forms, and dozens more. AI edits match Divi's expected structure.
Context checks, nesting rules, module-level validation, flexColumnStructure counts, variable references, and 16 common mistake patterns caught before anything hits the database.
If the AI sends a bare module, Respira auto-wraps it in Section → Row → Column hierarchy so the Visual Builder never sees invalid nesting.
Color palettes, typography tokens, and template patterns are exposed to the AI so generated layouts follow existing site style.
Pages still using [et_pb_*] shortcodes are extracted and injected through a separate pipeline, so non-migrated content stays safe.
Full parser for et_pb_* shortcodes with nesting support. Reads from post_content, _et_pb_page_layout, _et_pb_layout_content, and _et_pb_page_content.
Divi global modules are resolved during extraction so the AI sees the actual content, not opaque references.
Shortcode-wrapper sections on migrated pages are treated as opaque to prevent corruption. Mixed Divi 4/5 pages are flagged automatically.
Schemas built from Divi's registered et_pb_* modules at runtime. Every module type the site uses is available to the AI.
Automatic
Respira checks for <!-- wp:divi/ block markers and the et_builder_d5_enabled() flag first. If neither is present, it falls back to shortcode detection via _et_pb_use_builder meta. Mixed pages (both formats) are flagged automatically.
Migration toolkit
Readiness audit, mixed content detection, third-party module risk scoring, prompt packs, and a QA checklist. Respira plans the migration — Divi's native Migrator performs the conversion.
Safety
MCP inject calls require a diviVersion parameter ("4" or "5") to prevent format mismatches between extraction and injection.
If AI places <script> tags in divi/text modules, Respira warns that Divi strips them at render — before wasted save cycles.
If an empty inject is attempted, Respira falls back to the most recent WordPress revision instead of wiping the page.
Yes. Divi 5 block pages are read and written as divi/* block trees. 60+ module schemas are supported with full validation.
Yes. Divi 4 shortcode pages are extracted and injected through a separate pipeline. Multiple meta field sources are checked for compatibility.
No. Respira plans and validates migration through the Migration Copilot. The actual format conversion is performed by Divi's native Migrator tool.
Mixed pages are flagged automatically. Legacy shortcode-wrapper sections are treated as opaque to prevent corruption during AI edits.
Claude Code, Cursor, Codex, Gemini, Antigravity, and any MCP-compatible client. WebMCP also works directly in Chrome 146+.
Yes. Every edit goes through duplicate-before-edit, snapshot, and approval workflows. Full diff review and one-click rollback.
Whether the site runs Divi 5, Divi 4, or both — Respira handles the builder format so the AI can focus on content.