Avada MCP server, with undo on every edit.

An Avada MCP server lets Claude, ChatGPT or Cursor read and edit Avada Builder pages on a live WordPress site, element by element, along with Avada Layouts and the global colours and typography. With Respira every page edit lands on a copy first, and you can undo it for 90 days.

Start free Connect in one command

7 days free. No card. Runs on the AI subscription you already have.

Support
Full
Avada tools
11
Latest release touching it
9.3.4
Releases touching it
23

Respira is an independent MCP server. Not affiliated with, endorsed by, or sponsored by ThemeFusion. Avada is a product of ThemeFusion.

What works today. What still needs you.

Read from the current MCP server release, first-class reads and writes across the builder structure.

Works now

  • Avada Builder is detected when it is loaded or Avada is installed, and a page counts as an Avada page when its content holds Avada containers.
  • Pages are read and written as Avada's own shortcodes: containers, rows, columns and fusion_* elements, one inner row level included. Anything Respira does not model is kept byte for byte, and a write is refused when the page would not survive its own round trip.
  • Whole pages, element find, update, move and remove, and the add_* tools work against a catalog of 143 elements scanned from Avada 7.16.2 with Avada Builder 3.16.2.
  • After each write Avada's per-page CSS is reset, and edit links open the page in Avada Live.
  • The design system has its own tools: respira_get_avada_design_system and respira_update_avada_design_system read and change the palette (color1 to color8 plus custom colours) and the five typography sets. A change needs a confirmed live edit, can run as a dry run first, and takes a snapshot that also resets Avada's caches when restored.
  • Avada Layouts and Layout Sections, Avada's theme builder, can be listed, read, created and updated, and Library items can be read and placed on a page. Template conditions are set through the shared tools since plugin 9.3.1.

Where a human still steps in

  • Pricing Table, Tabs and Testimonials are experimental: check those elements in Avada Live after a change.
  • Content that uses Avada's global elements (fusion_global) is refused.
  • Library items are read and placed, not written. Edit the item itself in Avada.
  • Layouts and the Library need Avada Builder active, and the design system tools need the Avada theme.
  • The eight base colours can be changed but not removed. The Global Layout cannot be given conditions, and a condition for "items with any term" cannot be expressed in Avada.

Hit one of these and the snapshot gives you a clean way back.

11 tools made for Avada.

Registered in the MCP server at build time. Each name is the id your client calls, on top of the universal set: find, update, move, remove, build, snapshot, roll back.

  • wordpress_get_avada_design_system
  • wordpress_update_avada_design_system
  • wordpress_list_avada_layouts
  • wordpress_get_avada_layout
  • wordpress_create_avada_layout
  • wordpress_update_avada_layout
  • wordpress_get_avada_layout_section
  • wordpress_create_avada_layout_section
  • wordpress_update_avada_layout_section
  • wordpress_list_avada_library
  • wordpress_get_avada_library_item

Browse every tool

Three prompts you can paste right now.

Each one assumes Respira is connected to a Avada site. Paste it into your AI tool and run.

  1. Change a headline on a copy

    On the page "Services", find the first title element and change it to "Same-day repairs in Leeds". Make the change on a copy and send me the preview.

  2. Adjust the palette safely

    Show me the Avada palette and the five typography sets. Then do a dry run that changes color4 to #1F6F5C, and apply it only after I approve.

  3. Review the Layouts

    List the Avada Layouts on this site and the Layout Sections each one uses. Change nothing.

More recipes, per builder, in the Prompt Book.

Connect an Avada site in two minutes.

Pick your client and paste. The site URL and key come from your setup page, or from Respira › Setup in wp-admin. Node.js 20 or newer for the local server.

Claude Code

claude mcp add respira-wordpress --env WORDPRESS_URL=https://yoursite.com --env WORDPRESS_API_KEY=respira_your_api_key_here -- npx -y @respira/wordpress-mcp-server@latest

Put in your own site URL and key, run it, then check with /mcp. Every site at once: pass --env RESPIRA_CONFIG_B64=… from your setup page instead of the two values. The full Claude Code guide covers the first edit and undo.

Claude Desktop and Cursor

{
  "mcpServers": {
    "respira-wordpress": {
      "command": "npx",
      "args": ["-y", "@respira/wordpress-mcp-server@latest"],
      "env": {
        "WORDPRESS_URL": "https://yoursite.com",
        "WORDPRESS_API_KEY": "respira_your_api_key_here"
      }
    }
  }
}
  • Claude Desktop, macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Claude Desktop, Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Cursor: .cursor/mcp.json in your project

The file is claude_desktop_config.json, not config.json. Every site at once: replace the two env values with RESPIRA_CONFIG_B64 from your setup page.

Codex

codex mcp add respira-my-site --url https://yoursite.com/wp-json/respira/v1/mcp
codex mcp login respira-my-site

Run them one at a time. The second opens your browser to sign in to Respira; no key goes in the config. By hand, in ~/.codex/config.toml, then run the login command:

[mcp_servers.respira-my-site]
url = "https://yoursite.com/wp-json/respira/v1/mcp"

Browser sign-in, no key

https://yoursite.com/wp-json/respira/v1/mcp

Claude Desktop, claude.ai, ChatGPT and Cursor: add a custom connector, paste your site's MCP URL, leave Client ID and Client Secret blank, and approve the sign-in on respira.press. One connector per site.

Any other client

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

Detects Claude Code, Cursor, Codex, Windsurf and more, and writes the config. Set WORDPRESS_URL and WORDPRESS_API_KEY afterwards.

Common errors

The server does not show up in /mcp, or the client says it failed to start.
Cause Node.js is older than 20, or the site URL and key are missing.
Fix Run npx @respira/wordpress-mcp-server --doctor in the same shell. It names the missing setting, a bad URL or a refused key. node -v must print 20 or newer.
ENOENT errors that mention /_npx/ or node_modules.
Cause The npx cache is damaged, often by an interrupted install.
Fix Run rm -rf ~/.npm/_npx and restart the client. Or install once with npm install -g @respira/wordpress-mcp-server and use respira-wordpress-mcp as the command.
The browser sign-in opens a "Page not found" on yoursite.com/authorize.
Cause A Client ID was filled in on the connector, usually the respira_site_ key.
Fix Remove the connector and add it again with the MCP URL only. Leave Client ID and Client Secret blank. Sign-in happens on respira.press, never on your site.
The MCP address returns 404.
Cause WordPress is on plain permalinks, so /wp-json/ addresses do not resolve.
Fix In wp-admin open Settings › Permalinks, choose Post name and save once.
Calls fail with 401, 403, or HTML where JSON belongs.
Cause A firewall, a bot filter or a challenge page answers before WordPress does, or the host strips the Authorization header.
Fix Open Respira › Troubleshoot in wp-admin. It runs the checks from the site's own server, names what is in the way and writes a report for your host.
The agent says it saved, and the live Avada page looks the same.
Cause The edit is on a draft duplicate, waiting for your approval. That is the default on a published page.
Fix Approve the duplicate in wp-admin under Respira, or from its preview page. Until then the live page stays as it was.

Still stuck? Troubleshooting in the docs, or write to word@respira.press with the first error line.

What changed for Avada lately.

The last 5 releases that mention Avada, filtered from the same changelog the releases page reads.

  1. 9.3.4 Nov 3, 2026
    • Preserved Avada Layout conditions and slots when the stored JSON is double-encoded.
  2. 9.3.1 Nov 1, 2026
    • An Avada condition for posts in a category now matches. It was stored with a type Avada does not read. list_avada_layouts also shows Layouts in Avada's own order.
  3. mcp-8.7.2 Nov 1, 2026
    • Template conditions (plugin 9.3.1+): wordpress_get_template_conditions and wordpress_set_template_conditions read and set where a site template applies, in the same plain words on every builder with the builder's own value beside them.
  4. mcp-8.6.6 Oct 18, 2026
    • The README says what is new in 8.6. The npm page now lists full Yoast SEO support, publishing bound to the version a person approved, the Publish only key, Avada, inserts that leave the rest of a page alone, native block-library blocks and the busy-site retry.
  5. 9.2.7 Oct 15, 2026
    • A generic section on a Beaver Builder page shows its content. The shape agents send to every builder, a section holding a heading and text, was saved on Beaver with "section" and "text" as module names. Beaver has neither, so the page showed nothing but its title while the write said success.

All 23 releases that touched Avada

Questions people ask about Avada and MCP.

Does it change Avada's global options?

The palette and the five typography sets, through their own tools, with a confirmed live edit and a snapshot first. Those tools cover the design system only, not the rest of Avada's global options.

Is there an MCP server for Avada?

Yes. Respira is an independent MCP server that reads and writes Avada in its own format, with first-class reads and writes across the builder structure. It is not made by the Avada team.

Which tools does it use for Avada?

11 Avada-specific tools on top of the universal set: find, update, move and remove elements, build pages, snapshot and roll back. The list on this page is read from the MCP server source at build time.

What happens when the agent gets an edit wrong?

Nothing on the live page. The agent edits a copy first, you approve it inside WordPress, and every write is snapshotted with 90 days of undo.

Do I need a developer or a terminal?

No. Sign in with your browser from Claude, ChatGPT or Cursor and approve the connection once. Coding tools get a one-line command.

Does it work with a Avada site that also runs WooCommerce?

Yes. The WooCommerce add-on adds 104 store tools on the same connection, with the same duplicate-first approval flow.

Looking for the Avada overview, with visuals and the conversion story? Avada features

The other builders, same server.

Everything the WordPress MCP doesWooCommerce MCP

Start with one site. Free for 7 days.

Maker is €9 a month after the trial. No card for the trial, and it runs on the AI plan you already have, so there is no extra AI bill.

Start free Email Mihai
Summarize with Google AI Mode