Avada Builder MCP tools
Available in EMCP 3.17.0. Avada combines a theme, a visual builder and a Core companion plugin. EMCP Pro exposes a dedicated toolset for native layout discovery, draft creation and bounded shortcode-tree editing. Your agent can inspect installed element maps instead of inventing shortcode attributes.
Requirements and setup
Section titled “Requirements and setup”- Check installed versions. Avada Builder 3.16.1 through 3.16.x with the active Avada theme. EMCP Pro is required.
- Select the builder. Open EMCP Tools → Page Builders, pick the Avada card under 1. Standalone builder and choose Save changes in the save bar. A card marked Not detected cannot be picked and lists what it needs, such as the supported version and an EMCP Pro licence. Gutenberg stays on beside it, with any block packs you enable.
- Switch on its tools. Open EMCP Tools → Tools and select the Avada tab, which appears once the builder is saved. Write tools start disabled. On a new EMCP install the read tools start disabled too, as every Pro tool does. Switch on the tools the task needs and choose Save changes.
- Connect and inspect. Reconnect your MCP client, then read context and schemas. Start with a draft and inspect the native editor.
Native workflow
Section titled “Native workflow”When Avada Core is active, content discovery lists accessible Portfolio and FAQ records and Slider groups. Supported display elements can reference published source content. Build a portfolio page or FAQ section using those records while keeping source-content changes separate from layout work.
Discover Avada and Core
Section titled “Discover Avada and Core”Read native schemas and existing Portfolio, FAQ and Slider group records.
Assemble the supported layout
Section titled “Assemble the supported layout”Use containers, rows, columns and verified content elements with a fresh hash.
Review in Live Builder
Section titled “Review in Live Builder”Check responsive output and a native Live Builder save.
Tool reference
Section titled “Tool reference”All names use the emcp-tools/ namespace. Read the live input schema for optional fields, enums, limits and confirmation requirements; this table lists required inputs only.
| Tool | Access | Purpose | Required inputs |
|---|---|---|---|
avada-list-core-content | Read | Discover existing portfolio items, FAQs and slider groups for Core display elements. Does not change source content. | kind |
avada-get-context | Read | Read installed version, permissions, supported types and storage contract. Start here. | None |
avada-list-elements | Read | List registered native element types and nesting rules. Some specialized elements are read-only in this adapter. | None |
avada-get-element-schema | Read | Read native controls, defaults and nesting rules for a native shortcode type, e.g. fusion_title. | type |
avada-list-pages | Read | List editable WordPress pages and their Avada status. | None |
avada-get-page | Read | Read the native nested tree and content_hash for a page or existing template. | post_id |
avada-create-page | Write | Create an empty draft with Avada Builder enabled. | title |
avada-set-page-tree | Write | Replace a page tree with root, _nextNodeId and nested nodes. Requires expected_hash; preserves template settings and page status. | post_id, expected_hash, tree |
avada-add-element | Write | Add a childless native element, allocating a unique ID. Read schema/defaults first; default parent is root 1. | post_id, expected_hash, type |
avada-update-element | Write | Recursively merge named property groups while replacing lists and preserving other properties. IDs are scoped to the latest read. | post_id, expected_hash, element_id, properties |
avada-move-element | Write | Move a node and descendants to a parent and sibling position; rejects cycles and invalid nesting. | post_id, expected_hash, element_id, parent_id |
avada-remove-element | Write | Remove a node and its entire subtree; root cannot be removed. | post_id, expected_hash, element_id |
avada-list-templates | Read | List editable non-global library items and layout sections. Creation and conditions are not included. | None |
avada-get-design-system | Read | Read allowlisted typography, colors, widths and breakpoint settings; no global writes. | None |
Example request
Section titled “Example request”Create an Avada draft with service columns and an FAQ display using existing published Core records. Inspect available elements before building.
Read current state before editing and re-read after each save. If a hash is stale, inspect the changed document before rebuilding the request. A successful save is not proof of correct visual output: inspect the native editor and frontend.
Supported scope
Section titled “Supported scope”- Requires EMCP Pro, the active Avada theme and supported Avada Builder. Core elements also require Avada Core.
- Fifteen element types support authoring. Other installed types may be discovery-only.
- Source-item and slide creation, global settings, forms, global instances and layout conditions are excluded.
Troubleshooting
Section titled “Troubleshooting”If tools are missing, check versions, dependencies, integration selection, tool switches and user capabilities. Reconnect long-lived MCP clients after plugin updates or selection changes. If output differs after saving, inspect the native document and styles before retrying; do not bypass the adapter with direct metadata writes.
See the Avada Builder integration overview, builder setup guide and agent skills.