Respira 4.0.4 · MCP Server 3.3.4

WordPress MCP with page-builder superpowers for production teams

Respira for WordPress is an MCP execution layer for real sites. It keeps official WordPress MCP compatibility, then adds builder-aware tooling, WooCommerce operations, and approval-mediated publish flow.

Official WordPress MCP gives AI core access. Respira gives it page-builder superpowers (Divi 200+ modules, Elementor widgets, Bricks, etc.) with duplicate-before-edit safety so nothing ever breaks. Works on any hosting — self-hosted or managed.

Every write runs duplicate-before-edit, then approval. That keeps live URLs stable while assistants work fast.

Desktop MCP

82 + 21

103 total tools when WooCommerce add-on is active

WebMCP + Abilities

85 + 21

106 ability tools, including v2 read shortcuts

Builder Coverage

11 builders

Elementor, Divi, Gutenberg, Bricks, Oxygen, and more

Respira MCP 3.3.4 stays aligned with WordPress MCP Adapter v0.4.x lifecycle behavior while preserving compatibility for older adapter installs.

Setup line

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

Discovery

MCP for WordPress page builders

Teams search for terms like Elementor MCP or Divi MCP because core WordPress access is not enough for builder-heavy sites. Respira is the MCP layer for every supported builder in our stack, with one consistent safety workflow.

Canonical builder coverage: Elementor, Divi (Divi 4 + Divi 5), Bricks, WPBakery, Gutenberg, Oxygen, Beaver Builder, Brizy, Visual Composer, Thrive Architect, Breakdance.

Elementor MCP

elementor.com

Respira acts as an Elementor MCP server for widget-aware reads and safe writes.

  • Reads containers, sections, and widget context from Elementor data.
  • Applies targeted updates without flattening layout structure.
  • Supports replicate-and-adjust workflows for landing pages and templates.
  • Safety: duplicate-before-edit, then approve.
Open dedicated guide

Divi MCP (Divi 4 + Divi 5 / Divi5 MCP)

elegantthemes.com

Respira acts as a Divi MCP server for both Divi 4 and Divi 5 module structures.

  • Works with module-heavy pages, including large Divi design systems.
  • Preserves module hierarchy and builder-specific data models.
  • Supports precise content updates and reusable pattern replication.
  • Safety: duplicate-before-edit, then approve.
Open dedicated guide

Respira acts as a Bricks MCP server with structure-aware extraction and patching.

  • Reads Bricks element trees and content-bearing nodes accurately.
  • Applies changes in context instead of blunt HTML replacement.
  • Useful for redesign passes while preserving existing layout logic.
  • Safety: duplicate-before-edit, then approve.
Open dedicated guide

WPBakery MCP

wpbakery.com

Respira acts as a WPBakery MCP server for shortcode-based builder content.

  • Extracts editable content from WPBakery page structures.
  • Handles updates while preserving shortcode composition patterns.
  • Supports refresh workflows for legacy agency builds.
  • Safety: duplicate-before-edit, then approve.
Open dedicated guide

Gutenberg MCP

wordpress.org

Respira acts as a Gutenberg MCP server for block-aware editing flows.

  • Reads block structure and preserves block semantics on updates.
  • Supports content, media, and section-level block transformations.
  • Works well for editorial and long-form workflows.
  • Safety: duplicate-before-edit, then approve.
Open dedicated guide

Respira acts as an Oxygen MCP server for builder data and safe page changes.

  • Reads Oxygen-specific structures used in production sites.
  • Applies focused edits without forcing full-page rebuilds.
  • Supports modernization passes on established Oxygen installs.
  • Safety: duplicate-before-edit, then approve.

Beaver Builder MCP

wpbeaverbuilder.com

Respira acts as a Beaver Builder MCP server for module-level content updates.

  • Extracts content and layout context from Beaver Builder data.
  • Supports safe edits to existing pages and template clones.
  • Designed for iterative edits instead of one-shot rewrites.
  • Safety: duplicate-before-edit, then approve.

Brizy MCP

brizy.io

Respira acts as a Brizy MCP server for structure-preserving edits.

  • Reads editable fields from Brizy page data.
  • Keeps builder hierarchy intact through update cycles.
  • Supports campaign page refreshes and content operations.
  • Safety: duplicate-before-edit, then approve.

Visual Composer MCP

visualcomposer.com

Respira acts as a Visual Composer MCP server for safe operations on existing layouts.

  • Interprets Visual Composer page structures for targeted edits.
  • Preserves visual block composition during updates.
  • Useful for legacy sites that still run VC workflows.
  • Safety: duplicate-before-edit, then approve.

Thrive Architect MCP

thrivethemes.com

Respira acts as a Thrive Architect MCP server for conversion-page editing workflows.

  • Reads Thrive content structures used in marketing funnels.
  • Supports content and layout changes with builder context intact.
  • Works for ongoing CRO iteration without manual rebuilds.
  • Safety: duplicate-before-edit, then approve.

Breakdance MCP

breakdance.com

Respira acts as a Breakdance MCP server for builder-aware reads and controlled updates.

  • Extracts Breakdance structure and editable content nodes.
  • Supports safe refreshes of component-heavy page sections.
  • Maintains layout fidelity while updating copy and media.
  • Safety: duplicate-before-edit, then approve.

Disclaimer: Respira for WordPress is not officially affiliated with Elementor, Divi, Bricks, WPBakery, Gutenberg, Oxygen, Beaver Builder, Brizy, Visual Composer, Thrive Architect, Breakdance. All trademarks and product names belong to their respective owners.

Fidelity

Builder fidelity: clean extraction + lossless source

Respira can return a clean extraction view for AI tasks, then keep the original builder source intact for safe writes. That gives you readable context and layout fidelity in the same workflow.

Clean extraction for AI context

Use normalized content views for text, assets, and structure checks when you need concise context.

Lossless round-trips for builder source

Respira preserves source payloads such as Elementor JSON/meta and Divi structures so edits do not collapse page layouts.

Duplicate-first safety in both modes

Reads can be lightweight, but writes still follow duplicate-before-edit, then approval before live publish.

Positioning

Respira MCP vs Official WordPress MCP

Both matter. Official WordPress MCP provides core protocol access; Respira layers in builder and safety behavior for production operations.

Official WordPress MCP
Respira for WordPress MCP

Core WordPress entities and adapter-level discovery.

Builder-aware tools across 11 page builders.

Protocol and registration baseline.

Duplicate-before-edit with explicit approval mediation.

Generic runtime capabilities.

Snapshot and fidelity-aware workflows for safer rollouts.

Foundational server path.

WooCommerce CRUD extensions plus audit-oriented operations.

Browser MCP Context

WebMCP is the browser protocol. Respira makes it production-safe for WordPress.

WebMCP covers browser-side discovery and invocation. Respira adds approval gates and fidelity-aware write behavior so teams can ship safely, not just quickly.

Chrome runtime

Live in Chrome 146+ with Experimental WebMCP enabled.

Source

Cross-vendor editors

Current draft includes editors from Google and Microsoft.

Source

Community report

Published as a Web Machine Learning Community Group draft.

Source

Open specification

Spec text and issue history are public on GitHub.

Source

Respira safety contract

Duplicate-first writes, approvals, snapshots, and rollback.

Source
Discover tools in browser AI clients Keep approvals and rollback before publish Run one safety model across WebMCP and desktop MCP

Trusted by professionals

People shipping WordPress faster, without breaking live sites

Reviews are submitted by real users inside Respira for WordPress right after successful sessions.

Verified Reviews

7

Average Rating

5.0/5

Collection

In-product

“"I run two websites on FLAVOR.PRESS and have been really impressed with how seamlessly it integrates with Claude Code. The workflow just works – I can manage both sites efficiently, and the combination of FLAVOR.PRESS's platform with Claude's capabilities has made my day-to-day so much smoother. It's one of those tools where everything clicks into place from the start. Highly recommended for anyone looking for a reliable, developer-friendly setup."”

Martin

Verified

“I've been searching for exactly this solution for months – and then I found Respira. What truly amazes me: it doesn't just do what you expect, it actually thinks along with you. For my work with mysolarplant.de, this is a real game changer.”

“This plugin definitely has a WOW factor. After helping me change slugs and adding new hero to multiple pages in one prompt in a couple of minutes, i have to say that editing my client's wordpress sites will never be the same. thank god for good tech!”

Anonymous

Verified

“I love Respira! I can now literally have a chat with Claude Code and have it update my Wordpress sites with no fuss. The MCP Server/Plugin combo is secure and robust - it's saving me hours updating client sites. it handles plugins, Elementor, the admin and front end of my sites. What's great as well is that the developer is responsive, friendly and rolls out improvements regularly. Highly recommended!”

“ALHUMDULILLAH great experience”

Anonymous

Verified

“Mihai, just wanted to say thanks for building Respira. I run a chiropractic clinic in Adelaide and I'm using Claude AI to rebuild my entire website in Bricks Builder. Respira filled a gap nothing else could: letting Claude actually read and write Bricks content through MCP. The fact that you built this as a solo developer, listened to early feedback, and kept shipping updates is genuinely impressive. Rooting for you and the product. Keep going! 🎉🚀”

“This is fxxxxxg amazing! I had to upload 14 PDFs and find a way to show them on a complex page build more than 1 year ago on a WordPress site with a theme that is using WP Backery. I linked Cursor (auto-mode) to my site with this plugin and it uploaded the PDFs to Media Library (it asked me for an application password but that was easy) and created a stunning section (in a similar style with the other sections on the page) with a preview panel and all the PDFs displayed nicely and when somebody clicks a PDF it loads in the panel without opening a new tab. Everything took about 15 minutes in total. I did not even know how to do that myself, not to mention that just uploading the PDFs and putting them on the page would have take me at 3 hours and the result would have been a lot worse.”

Victor

cekt.ro

Verified

Every review shown here was submitted by a real Respira for WordPress user in-product.

Execution Paths

Same workflow, two runtimes

Desktop MCP (CLI/editor)

Runs through the npm server package and connects assistants like Claude Code, Cursor, Windsurf, Codex, and other MCP-compatible clients.

  • Use npx -y @respira/wordpress-mcp-server in your client config
  • Negotiates respira/v2 when available, clean fallback to respira/v1
  • Aligned with MCP Adapter v0.4.1 server registration + transport permission model
  • Tool inventory sourced from mcp-server/src/server.ts

Browser AI (WebMCP)

Built into Respira for WordPress and exposed through WordPress Abilities/MCP Adapter. No second browser bridge plugin is required.

  • Chrome 146+ with Experimental WebMCP enabled
  • Ability IDs are rebased as respira/<tool-name>
  • Tool inventory sourced from plugin WebMCP registry

Accuracy Ledger

Tool inventory by surface

Numbers below are generated from source files at build time, not hand-typed marketing claims.

Surface WordPress Tools Woo Tools Total When Woo Active Source of Truth
Desktop MCP server 82 21 (conditional) 103 mcp-server/src/server.ts
WebMCP / Abilities 85 21 (conditional) 106 class-respira-webmcp-integration.php

WebMCP currently exposes 0 plugin-side shortcuts not present as separate desktop tool IDs: none

Desktop Catalog

What the desktop MCP server actually exposes

WooCommerce add-on tools (21)

These register only when WooCommerce add-on is both installed and licensed: woocommerce_list_productswoocommerce_get_productwoocommerce_create_productwoocommerce_update_productwoocommerce_duplicate_productwoocommerce_list_orderswoocommerce_get_orderwoocommerce_update_order_statuswoocommerce_get_stock_statuswoocommerce_update_stockwoocommerce_sales_reportwoocommerce_list_categorieswoocommerce_get_categorywoocommerce_create_categorywoocommerce_update_categorywoocommerce_delete_categorywoocommerce_list_tagswoocommerce_get_tagwoocommerce_create_tagwoocommerce_update_tagwoocommerce_delete_tag

Latest Woo expansion includes dedicated category and tag taxonomy tools.

See WooCommerce add-on details

Commerce

WooCommerce MCP

Respira extends WordPress MCP with WooCommerce operations for stores and agencies that manage product updates through AI assistants.

Current CRUD coverage

  • Products: list, read, create, update, duplicate
  • Orders: list, read, and status updates
  • Stock operations: stock status + inventory updates
  • Taxonomies: category and tag CRUD tools

Why this matters for teams

  • Run catalog refreshes without touching live originals directly.
  • Keep approved Woo product edits on the same live product ID for ad/catalog sync stability.
  • Keep one approval model across pages, posts, and commerce tasks.
  • Coordinate store edits from desktop MCP or browser WebMCP paths.
  • Audit all operations through the same Respira safety contract.

WordPress AI Infrastructure

Abilities + MCP Adapter + WebMCP

Ability IDs

Respira registers tools as WordPress abilities and rebases IDs to kebab-case, for example: respira/wordpress-list-pagesrespira/wordpress-apply-builder-patch

Discovery endpoints

/wp-json/wp-abilities/v1/abilities /wp-json/mcp-adapter/v1/servers

If both are present, Respira abilities are discoverable through the official adapter path and browser WebMCP.

Surface behavior

Desktop MCP and WebMCP share the same duplicate-before-edit and approval semantics. The browser path adds WordPress-native ability discovery.

Generic MCP server config snippet

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

FAQ

Common WordPress MCP questions

Is there an Elementor MCP server?

Yes. Respira acts as an Elementor MCP server with builder-aware reads, safe duplicate-first writes, and approval before publish.

Is there a Divi 5 (Divi5) MCP server?

Yes. Respira supports Divi 4 and Divi 5 structures and keeps updates inside duplicate-before-edit approval flows.

Is there an MCP server for Bricks, WPBakery, or Gutenberg?

Yes. Respira covers Bricks MCP, WPBakery MCP, Gutenberg MCP, and other supported builders through one consistent MCP safety model.

Does Respira work with Claude Desktop, Claude Code, Cursor, and Codex?

Yes. The desktop MCP server works with MCP-compatible clients, and browser AI paths can use WebMCP through WordPress abilities.

Do I need my WordPress site publicly accessible?

Your MCP client must reach the site URL and authenticate with a Respira API key. Public internet exposure is not required when your network provides secure access.

Can MCP edit WooCommerce products?

Yes. Respira WooCommerce MCP tools cover product CRUD, order and stock operations, and taxonomy flows for categories and tags. Product approvals keep the original live product ID stable so Meta Catalog and Google Merchant Center mappings do not break.

What does duplicate-before-edit mean?

Respira edits a duplicate first, then you review and approve before anything goes live. The original remains untouched until approval.

How is Respira different from official WordPress MCP?

Official WordPress MCP gives AI core access. Respira gives it page-builder superpowers (Divi 200+ modules, Elementor widgets, Bricks, etc.) with duplicate-before-edit safety so nothing ever breaks. Works on any hosting — self-hosted or managed.

How does Respira preserve builder fidelity?

Respira can return a clean extraction view for AI tasks while preserving lossless builder source for round-trips, so layouts remain stable after edits.

What is the difference between desktop MCP and WebMCP?

Desktop MCP runs through the npm server in your editor or CLI. WebMCP runs in browser AI paths through WordPress abilities and MCP Adapter.

How do I connect WordPress to MCP quickly?

Run npx @respira/wordpress-mcp-server --setup, add your site URL and API key, then verify read access before your first duplicate edit.

Single next step

Connect your assistant and run a safe first edit

Start with the setup command, verify connection, then ask your assistant to read context, duplicate a page, and edit only the duplicate.

Start Free Trial Read Docs