MCP server
Respira for Avada
Your AI builds and edits Avada pages that still open in Avada Live.
Containers, rows, columns and Avada elements, written as Avada Builder shortcodes. Everything Respira does not change stays byte for byte. The global palette, typography sets, Layouts and the Library too, with a snapshot before every write. Works with Claude, ChatGPT, Cursor, Codex or any MCP client.
Avada Builder shortcodesUntouched content kept byte for byteGlobal palette and typographyLayouts and Layout SectionsLibrary itemsOpens in Avada LiveSnapshot before every write
Respira MCP
Avada detected
Prompt
"Add a section with three checklist items under the hero on the services page."
Respira
Added one container under the hero, with a row, a column, a title and a checklist of three items. The rest of the page is unchanged, byte for byte, and the edit link opens it in Avada Live.
Every element Avada Builder 3.16.2 registers, with its child items and settings
Design system, Layouts, Layout Sections and the Library
Avada joins the list in plugin 9.2.6
Capabilities
What Respira does on an Avada site.
Avada shortcodes, natively
Pages are read and written as Avada Builder shortcodes: containers, rows, columns and Avada elements such as titles, text blocks, buttons, images, toggles, tabs, checklists and code blocks. Loose elements get the container, row and column Avada needs.
The rest stays byte for byte
Everything Respira does not model, a third-party shortcode, a newer Avada element or a Library global, is kept exactly as it was. A write that would not read back the same way is refused before anything is saved.
Element-level editing
Find an element, change one setting, move or remove it, add elements with the add tools or build a whole page. After each write Respira clears that page's compiled Avada CSS so the change shows.
The design system
Read the global colour palette and the five typography sets with the CSS variables elements use, such as var(--awb-color5), and change them through Avada's own Global Options. Design tokens land in the palette as new colours and never overwrite one you have.
Layouts and Layout Sections
List, read, create and change Layouts: which header, page title bar, content and footer section each one uses and where it applies, the Global Layout included. The sections themselves can be read, built and edited.
The Library
List and read Library items with the exact piece to place in a page. A global item is placed the way Avada places it, as a reference, so the page keeps following edits to the original.
What it knows
The details that decide whether an Avada edit is safe.
Library globals stay references
Avada copies any element marked as an expanded global back into its Library item, on every page that uses it. Respira reads pages without expanding globals and refuses a write that holds an expanded one, so a page edit cannot overwrite a shared element.
Site-wide changes ask first
A palette or typography change, a Layout with conditions, or an edit to a Layout Section in use restyles many pages at once. Respira asks you, takes a snapshot, and a restore puts the old values back and clears Avada's caches again.
Avada's own cache resets
A page write runs Avada's per-page CSS reset, the one Avada runs when you save a page. Global Options and Layout Section changes reset Avada's caches for the whole site, as Avada does itself.
Three elements are experimental
Avada 7.16 rebuilt Pricing Table, Tabs and Testimonials. Respira writes and reads them like the rest and marks them experimental, so check those in Avada Live after a change.
Avada tools
11 tools built for Avada, on top of the page and element tools every builder gets.
respira_get_avada_design_system Read the global palette and the five typography sets, with the CSS variable each one is used by.
respira_update_avada_design_system Change palette colours and typography sets through Avada's Global Options, after your yes, with a snapshot first. A dry run shows the plan.
respira_list_avada_layouts Every Layout in match order, the section in each slot and the pages it applies to, plus every Layout Section.
respira_get_avada_layout One Layout, the Global Layout included: its sections per slot and its conditions.
respira_create_avada_layout A new Layout. Without conditions it shows nowhere, so you can review it first.
respira_update_avada_layout Assign sections or change conditions. A change to a live Layout waits for your yes.
respira_get_avada_layout_section Read a header, page title bar, content or footer section, with its Avada Live link.
respira_create_avada_layout_section Build a new section. It shows nowhere until a Layout uses it.
respira_update_avada_layout_section Replace or extend a section. A section in use waits for your yes, and Avada's caches are reset.
respira_list_avada_library Saved containers, columns, elements, post cards, mega menus and templates, and which are global.
respira_get_avada_library_item One Library item, the pages that use it, and the exact piece to place in a page.
How it works
Detect Avada. Read its elements. Write what Avada renders.
1. Detect
Respira sees Avada on the site
Builder info reports Avada and its version, and the Avada tools appear in your AI client. Pages built with Avada Builder are edited as Avada; Layouts and the Library need Avada Builder active.
2. Understand
Elements from a real Avada Builder
Avada lists its elements only inside wp-admin and its own editor, so Respira carries a scan of Avada Builder 3.16.2: 143 elements, their child items, and every setting with its type, default and allowed values.
3. Write
Shortcodes Avada renders, with a snapshot first
Missing containers, rows and columns are added, the write must read back the same before it is saved, and the edit link Respira returns opens the page in Avada Live.
Tested on a real site running Avada 7.16.2 with Avada Builder 3.16.2: pages render and open in Avada Live, a page saved in Avada Live still reads and writes byte for byte, a global colour change showed on the page, a new footer went live site-wide, and a placed Library item followed an edit to the original.
Example prompts
What you can ask, right now.
These work with any MCP client. Respira turns them into Avada containers, rows, columns and elements, so you never describe the shortcode format yourself.
Try prompts like these
Add a section with three checklist items under the hero on the services page.Change the button text in the second container to "Book a call".Show me the Avada palette and typography sets on this site.Make color 5 a darker teal across the whole site.Which Layout shows on the blog, and which footer does it use?Build a new footer section with the contact details, and keep it off the site until I review it.Place the global call to action from the Library at the end of the about page.Restore the homepage to how it was before the last change.
Avada, natively
Pages your AI builds, in the builder your clients already know.
Avada Builder pages, the design system, Layouts and the Library, with a snapshot before every write. Start free, no credit card.
