Edit one element, not the page
UX Builder stores a page as shortcodes, so the usual approach is to rewrite the whole string. Addressing an element by its path changes a heading or a column width and leaves everything else byte for byte identical.
Flatsome · 11 typed abilities
Flatsome MCP.
Flatsome MCP lets an AI client read and edit UX Builder pages as a structured tree, using the theme's own elements, presets and reusable blocks.
Definition
What is Flatsome MCP?
Flatsome MCP is the Model Context Protocol surface for Flatsome itself. WPPilot Free installs the MCP server inside your own WordPress site, and the Pro Flatsome module registers 11 typed abilities on top of it, so a connected AI client can inspect setup health, the UX Builder tree of any page and element catalogue before it proposes anything, then insert an element or a whole subtree once the active safety profile allows a write.
MCP for Flatsome is not a chat box bolted onto the editor, and no external service sits in the middle. Because the Flatsome MCP server runs on your install, your WordPress roles and capabilities, the safety profile, and per-call confirmation decide what an agent may touch, and every supported write is recorded in the change ledger.
Read first, then write
What an agent can see and change in Flatsome
Every Flatsome operation is a typed ability with a schema, not a free-text write. The agent inspects before it proposes.
Reads
Available in every safety profile, including Read Only.
setup healththe UX Builder tree of any pageelement catalogueelement option schemassection presets the theme shipsreusable UX Blocks
Writes
Gated by the active profile, your WordPress capabilities, and confirmation for destructive calls.
insert an element or a whole subtreeedit one element's optionsmove an elementdelete a subtreereplace a page's tree
What you can build
Jobs Flatsome teams actually hand to an agent
Each of these starts with an inspection step, which is what keeps the change reviewable.
Start from what the theme ships
Flatsome carries its own section presets — eighteen for the section element alone. Reading one gives the agent markup that is valid for this exact Flatsome version, instead of attributes assembled from a schema and hope.
Fix the block, not the twelve pages
A section repeated across a site is usually a UX Block. Finding it first means one edit rather than twelve, and the agent can tell you which pages embed it before it writes.
Audit an inherited store
Reading the tree of every page is far quicker than clicking through UX Builder, and it needs no write access at all.
Example prompts
Start with an inspection, not an instruction
Prompts that use Flatsome's own vocabulary get better results than "redesign this page".
- 1
“Read this page's UX Builder tree and tell me what each section contains.”
- 2
“Add a two-column row under the hero, with the left column at six columns on desktop and full width on mobile.”
- 3
“Show me the section presets Flatsome ships, then build the services section from the one with a media panel on the left.”
- 4
“Which UX Blocks does this site have, and which pages embed them?”
Setup
Connect an AI client to Flatsome in four steps
WPPilot documents routes for 20 current AI clients. The Flatsome abilities behave identically across all of them because policy is enforced on your site.
- 1
Install WPPilot Free
Activate the free plugin on WordPress 6.9+ and open the Connect screen. This is the MCP server itself, no external service sits in the middle.
- 2
Connect your AI client
Copy the generated configuration for your client, or complete browser-based OAuth 2.1 with PKCE. WPPilot documents a route for each supported client.
- 3
Start in Read Only
Ask the agent to inventory a page before enabling any write. You see exactly what it can read before it can change anything.
- 4
Activate Pro for the builder module
The builder-specific abilities load once a Pro licence is active and the plugin is detected on the site.
Authenticating for the first time? OAuth 2.1 setup or Application Passwords. For the read-before-write sequence, see the page builder workflow guide.
Honest limits
What this will not do.
Flatsome output still has to be reviewed by a human. These are the constraints worth knowing before you point an agent at a production site.
Read the safety model- Theme options — the header builder, typography, colours — are Customizer settings served by the Theme Bridge module, not this one.
- WordPress cannot nest a shortcode inside itself past the aliases UX Builder registers, so a tree that nests one tag more than ten levels deep is refused rather than written and silently flattened.
- Option values cannot contain a double quote, because shortcode attributes are quoted with one and WordPress has no escape for it. Such a value is refused, not mangled.
- The element catalogue is loaded on demand, because Flatsome only registers it inside its editor. Reading and writing pages never needs it.
- Registering a new UX Builder element is a code change in a theme or plugin, not a content operation.
How the abilities split
What the Flatsome module can do, and what it asks first
The module registers 11 abilities. 6 of them are reads: they inspect Flatsome structure, schemas and settings, return what they found, and change nothing, which is why they stay available even under the Read Only safety profile and are not rate limited. 3 are writes, gated by the active profile and by the WordPress capabilities of the user behind the connection. The remaining 2 are marked destructive in the plugin source, so each call needs an explicit confirmation flag every time it is made, with no way to turn that prompt off for a session.
That ratio is the practical answer to how much of this you can leave an agent doing unattended. Discovery is cheap and safe to run often; the writes are where the review belongs. Every write is recorded in the change ledger with the ability that made it, and the Flatsome ability reference lists all 11 by name with the description the plugin itself registers.
Questions
Flatsome MCP, answered
What is Flatsome MCP?
Flatsome MCP lets an AI client read and edit UX Builder pages as a structured tree, using the theme's own elements, presets and reusable blocks. The MCP server itself is WPPilot Free running inside your WordPress install, and the Pro module adds 11 typed Flatsome abilities on top of it.
Does it edit UX Builder shortcodes directly?
It parses them into a tree, changes the node you named, and writes the tree back. That is what keeps the nesting aliases, the responsive attributes and the editor's element ids intact — the three things hand-editing the string gets wrong.
Will the page still open in UX Builder afterwards?
Yes. Content written this way was run through UX Builder's own open-and-save transformers, which read back the identical node count. The editor's save drops options equal to their default and reorders attributes, which changes bytes and not meaning.
Does it handle responsive settings?
Flatsome writes a per-breakpoint value as its own attribute, with the breakpoint name appended to the option name. They are exposed as a per-option map instead, so you ask for six columns on desktop and twelve on mobile without knowing the convention. A breakpoint Flatsome does not have is refused.
Can it work on my WooCommerce shop pages?
Product data belongs to the WooCommerce module; this one handles the layout around it, including Flatsome's own product elements. Both are in Pro and an agent can use them in the same conversation.
Which Flatsome versions are supported?
The module was built and verified against Flatsome 3.20.9 and floors there. Child themes are supported and report the parent theme's version.
Looking for the full capability reference? See every Flatsome tool group.
Your site · your policy · your AI client
Point your AI client at Flatsome.
Install WPPilot Free, start in Read Only, and add Pro when you want the 11 typed Flatsome abilities.