Respira Integrations

Pick your AI co-pilot. Keep the same seatbelt.

Respira works across desktop and browser AI clients through one consistent safety model. Your team can switch assistants without changing how safety, approvals, and rollback work.

Duplicate-before-edit Approval workflow Snapshot-backed rollback 12 builder support

Featured Setup Guides

First-party integration pages

Elementor + Angie logo

Elementor + Angie

Zero-setup Respira inside Elementor’s Angie chat interface.

Open guide
Cursor + WordPress logo

Cursor + WordPress

Fast editor-native MCP workflow with project-level setup and safe write flow.

Open guide
Claude + WordPress logo

Claude + WordPress

Claude Desktop and Claude Code paths with the same Respira safety contract.

Open guide
Codex + WordPress logo

Codex + WordPress

Terminal-first setup for teams that ship from CLI and want precise control.

Open guide
Divi 5 + Divi 4 logo

Divi 5 + Divi 4

Divi-specific migration and compatibility workflows for AI-assisted editing.

Open guide

How It Maps

One workflow, multiple clients

Surface Best for Setup shape Safety behavior
Cursor Editor-native iteration .cursor/mcp.json Duplicate-first + approvals
Claude Desktop + CLI workflows claude_desktop_config.json or claude mcp add Duplicate-first + approvals
Codex Terminal-first teams codex mcp add or config.toml Duplicate-first + approvals

Compatibility

Also works with any MCP-compatible assistant

If your assistant can run an MCP server process, it can use Respira. The integration guides above are optimized paths, not hard limitations.

Start with setup wizard

Use one command to generate config and verify your site connection.

npx @respira/wordpress-mcp-server --setup
See Pricing