FAQ

Do I need coding experience to use Respira for WordPress?

No. Respira is designed so you can work entirely through natural language. Developers can go deeper, but coding is not required.

Which AI tools work with Respira?

Respira works with AI coding assistants that support the MCP protocol, including Cursor, Claude Code, Windsurf, and similar tools.

How many tools are available now?

Respira's catalog is 230+ tools. To keep prompts lean, the MCP server surfaces a context-filtered subset per site, typically 130–170, scoped to your detected builder and active plugins, plus 21 WooCommerce tools when the add-on is active. Browser AI/WebMCP exposes a separate inventory contract.

Is it safe to let AI edit my site?

Yes. Respira uses a controlled, permission-based workflow. Your AI assistant proposes changes, and you approve them before they are applied.

Does Respira modify content directly or create duplicates?

By default, Respira creates duplicates for safety. If direct editing is enabled, Respira asks for explicit live vs duplicate confirmation before editing originals.

Is Respira free to try?

Yes. Respira offers a free trial. You can start without entering payment details.

Which page builders does Respira support?

Respira supports 16 page builders with full read and write: Gutenberg, Elementor, Divi 4, Divi 5, Bricks, Oxygen Classic, Oxygen 6, Beaver Builder, Breakdance, Flatsome, Brizy, Visual Composer, WPBakery, Spectra, Kadence Blocks, and GenerateBlocks. SeedProd is audit-only (agents read and report on landing pages), and Thrive Architect supports text edits.

Since 8.0 "Canopy" the native WordPress Site Editor is covered too, which makes the line "16 page builders plus the native Site Editor". On a block theme that means block templates and template parts, synced and unsynced patterns, block navigation, and global styles. Read-only discovery works everywhere; structural writes to those site-level objects are beta-gated per site and off by default. See Site Editor.

I see respira_mcp_update in responses. Is that an error?

No. It is an upgrade hint from the MCP server when a newer package version is available. Upgrade with:

npx -y @respira/wordpress-mcp-server@latest

To disable automatic update checks, set RESPIRA_MCP_DISABLE_UPDATE_CHECK=1.

Where did settings go after the 4.0 admin refresh?

Respira → Settings is now the single source of truth for editable plugin settings. Setup → Health & Permissions is a read-only readiness summary.

I hit Elementor 500 errors during updates. What should I do?

Update to the latest Respira for WordPress plugin and MCP server. Recent releases include hardened payload handling, safer fallback writes, and improved structured diagnostics.