Get the plugin
WP MCP/Integrations/Avada MCP

Avada MCP · Pro

Avada MCP: let an AI agent edit Avada pages.

An Avada MCP server gives an AI agent a safe way into Avada's Fusion Builder layouts. WP MCP reads an Avada page as a tree of containers, columns and elements, changes exactly the element you asked about, and snapshots the page first.

Self-hosted · snapshot before every write · one-click undo

What it is

What a Avada MCP server does.

Avada's Fusion Builder stores a layout as shortcodes in post_content, with a fusion_builder_status flag in post meta. An agent that edits that string with find and replace will sooner or later break a nested shortcode. An Avada MCP server exists to prevent that: it parses the layout, hands the agent a tree, and writes the result back in the format Avada expects.

WP MCP also finds Avada pages a simpler check would miss. Imported demo content often has no builder flag, so detection falls back to the fusion_builder_container shortcode itself.

Avada sites tend to be large: demo imports, dozens of containers per page, Fusion Builder elements nested several levels deep. The risk with an AI agent there is a broad rewrite that flattens work nobody remembers building. WP MCP reads an Avada page as a tree with a path per element and changes the one you name, leaving every other shortcode exactly as stored, then invalidates the page's dynamic CSS so styles recompile from what is really saved.

Read and change

What WP MCP can read and change in Avada.

It can read

  • Which pages are built with Avada, including imported ones with no builder flag
  • A page's layout as an element tree with a path per element
  • The hash of the stored layout, used to guard the next write

It can change

  • Update, add, remove or move one element by path
  • Replace the whole layout in one write
  • Set the builder flag so the page opens in Avada's editor
  • Invalidate Avada's per-page dynamic CSS after a write or a rollback
detect-builderget-builder-contentupdate-builder-contentrollback-operationrollback-session

These are the real ability and operation names the agent calls. TheAvada (Fusion Builder) AI agent tool reference page lists the calls in detail.

Example prompts

Three things to ask first.

Which of my pages are built with Avada, and which ones were imported from a demo?

In the first container on /about, change the title text and leave the styling alone.

Remove the outdated promo column from the Avada homepage, then show me what changed.

Which pages came from the demo import and never opened in Fusion Builder?

The read finds Avada pages including imported ones with no builder flag, so the agent can list them and say which carry the flag.

On /about, change the title text in the first container and leave the styling alone.

get-builder-content returns the tree and hash, update-builder-content changes one element by path, and the page's dynamic CSS is invalidated afterwards.

Remove the old promo column from the homepage and show me what changed.

A remove operation on that path, snapshotted first. rollback-operation restores the previous layout and the CSS is invalidated again.

Safety

Every Avada write has a way back.

Avada layouts are post_content plus one post meta flag, so the post snapshot holds the complete layout before each write. Elements the agent did not address keep their exact shortcode markup, and Avada's dynamic CSS for the page is invalidated after the write and again after a rollback, so the styles recompile to match what is stored.

Snapshot before every write

No tool that writes can skip it. The before-state is saved first, the change is applied second.

One-click undo

Restore a single change with rollback-operation or a whole agent run with rollback-session, from the agent or from wp-admin.

Content-hash guarded

A write to an Avada page that already has a layout needs the hash from the read. A page changed since then is refused, and nothing is written.

Free or Pro

Part of WP MCP Pro.

The three builder tools (detect-builder, get-builder-content, update-builder-content) are part of WP MCP Pro. The free plugin still covers the rest of the site, including Gutenberg block editing, posts, pages, media, menus and the full snapshot and rollback engine, so you can try the safety model before you pay for builder editing.

WP MCP Pro starts at $49 a year for one site. See pricing for what each tier includes.

How to connect

Connect Avada MCP in four steps.

  1. 01
    Install WP MCP

    Upload the free wpmcp plugin and activate it. It needs WordPress 6.9 or newer and PHP 8.1 or newer, and it runs entirely on your own server.

  2. 02
    Check the requirement

    Avada pages on the site. Reads and writes work on the stored shortcodes and flag, so Avada does not have to be loaded to edit, only for the pages to render.

  3. 03
    Connect your client

    Add the site to Claude Code, Claude Desktop, Cursor or any MCP client with a WordPress application password, or the WP-CLI stdio bridge locally. OAuth 2.1 with full or read-only access is there too, once the site owner switches it on.

  4. 04
    Ask for the change

    Describe what you want done in Avada. WP MCP snapshots the target, makes the change, and leaves a Restore button next to it in wp-admin.

Step-by-step guides: Claude,Claude Code andCursor. The docscover the safety model in full.

Frequently asked

Avada MCP: questions, answered.

What is Avada MCP?

It is Avada page editing exposed to AI agents over the Model Context Protocol. WP MCP runs inside your WordPress site and gives Claude, Cursor or any MCP client three tools for Avada: detect the builder, read a layout as a tree, and write one element or a whole layout.

Is Avada MCP the same as Fusion Builder MCP?

Yes, for this purpose. Fusion Builder is the page builder inside the Avada theme, and its layouts are what WP MCP reads and writes.

Will an AI edit break my Avada styling?

An element operation rewrites only the addressed element and leaves the rest of the markup byte for byte. After the write, Avada's dynamic CSS for that page is invalidated so it recompiles from the new layout.

Can I undo an Avada edit made by an agent?

Yes. Each write is snapshotted first, and rollback-operation restores the exact layout and flag. The dynamic CSS is invalidated on the rollback too.

Do I need WP MCP Pro for Avada?

Yes. Builder editing for Avada is a Pro capability. Everything else on the site, and the undo engine itself, is in the free plugin.

Do I need Avada loaded for the agent to edit a page?

No. Reads and writes work on the stored shortcodes and the builder flag, so Avada only has to be active for the pages to render.

Does the agent set the builder flag?

Yes, it can set the flag so an edited page opens in Avada's editor. Pages are otherwise left as they were stored.

Does Avada MCP work with Claude, Claude Code and Cursor?

Yes. Claude Code and Cursor connect to WP MCP over HTTP with a WordPress application password, and Claude Desktop uses the desktop bundle from the WP MCP Connection screen. Clients that can only sign in with OAuth, such as the claude.ai custom connector, need OAuth switched on first with one line in wp-config.php, because it ships off. Once connected, the Avada tools are available in every client the same way.

Point your AI agent at Avada.