GoBuildWP Pro · 11 Flatsome abilities
Flatsome MCP that edits UX Builder pages by path. Presets and UX Blocks included.
GoBuildWP's Flatsome MCP gives an AI client 11 typed abilities in GoBuildWP Pro. It parses a UX Builder page into a tree, edits one element's options by path, builds from the section presets Flatsome ships and finds reusable UX Blocks, then writes shortcodes UX Builder can open again.
Pro from $39/year, Flatsome 3.20+, Setup guide
Proposed sequence using source-declared abilities in GoBuildWP Pro 1.12.4. Site, IDs, changes and outcomes are illustrative; no live client, native-editor or restore test is recorded here. Confirm the installed schema and policy separately. A confirmed call carries confirm: true, which the agent sets itself by default; a person approves only when Confirmation mode is “A person approves” or a Pro approval policy holds the call.
UX Builder paths
Every UX Builder element has a path the agent can name
A path is the list of positions leading from the page root to one node, and its last entry is the node's place among its siblings. flatsome-add-element inserts at a path, flatsome-edit-element merges options at one, and flatsome-move-element reads its destination against the tree with the moved node already taken out, so a move within one parent lands where you expect.
UX Builder stores a page as nested shortcodes, with responsive values written as separate attributes and nesting handled through aliases. Rewriting that string is where hand edits go wrong. GoBuildWP parses it, changes the node you named, and writes the tree back, so the nesting aliases, responsive attributes and editor ids survive.
The reported development check compared node counts after UX Builder open/save. Equal counts alone do not prove option, responsive-value, ID or semantic preservation; retain a fixture diff and verify editor/frontend output. Product data stays with the WooCommerce module; this one handles the layout around it. A draft page does not isolate a reused live UX Block: inspect its embedding shortcode in site content and theme assignments, identify affected routes, and obtain separate approval before changing that shared block.
Guard rails on Flatsome writes
- Children left alone. flatsome-edit-element merges options into one node and never touches what is inside it.
- Whole-tree writes confirmed. Replacing a page's tree or deleting a subtree is destructive and needs explicit confirmation.
- Editor ids kept. Nesting aliases, responsive attributes and the ids UX Builder relies on are written back as they were.
- Catalogue on demand. The element catalogue loads only when asked, because Flatsome registers it inside its own editor.
Path-based abilities
Flatsome abilities that address one node by path
- Reads
- 6
- Writes
- 3
- Destructive effects
- 2
flatsome-get-contentParses a page into tag, type, options, a per-breakpoint responsive map and a path for every node.
flatsome-edit-elementMerges options into the element at a path and leaves its children alone.
flatsome-list-presetsThe ready-made markup UX Builder's own picker inserts, valid for this exact Flatsome version.
flatsome-list-blocksLists reusable UX Blocks and their embedding shortcode. Inspect which pages and theme settings reference the selected block before editing; the list is not a complete usage map.
flatsome-move-elementMoves a node and its children to a new path in one call.
flatsome-check-setupReports the theme version, child theme and UX Builder state, and whether the element catalogue can load.
Shop layout jobs
UX Builder jobs, from presets to UX Blocks
Edit one element, not the page
Address one element by its current path and limit the proposed option change. Compare the saved tree for unrelated changes: default removal and attribute ordering can change serialization bytes without changing meaning. No byte-identity guarantee is made.
Example prompt: Read the UX Builder tree for post_id [ID]. Identify the target heading at path [PATH] and its current text. Propose only the supplied replacement text [TEXT]; wait for approval, then use flatsome-edit-element with its installed schema. Re-read the saved tree and compare children, sibling options and responsive values. Re-read paths before another structural edit.
Start from what the theme ships
Flatsome carries its own section presets. Reading one gives markup that is valid for this exact version.
Example prompt: Show me the section presets Flatsome ships, then build the services section from the one with a media panel on the left.
Fix the block, not the twelve pages
A section repeated across a site is usually a UX Block. Find it first and make one edit.
Example prompt: Which UX Blocks does this site have, and which pages embed them?
Set responsive values plainly
Ask for six columns on desktop and twelve on mobile without knowing Flatsome's attribute convention.
Example prompt: Add a two-column row under the hero, six columns each on desktop and full width on mobile.
Complete module
All 11 Flatsome abilities at a glance
Reads · 6
| Ability | What it does | Read / Write / Destructive | Edition |
|---|---|---|---|
flatsome-check-setup | Check Flatsome Setup | Read | Pro |
flatsome-get-content | Get Flatsome Content | Read | Pro |
flatsome-get-element-schema | Get Flatsome Element Schema | Read | Pro |
flatsome-list-blocks | List Flatsome UX Blocks | Read | Pro |
flatsome-list-elements | List Flatsome Elements | Read | Pro |
flatsome-list-presets | List Flatsome Presets | Read | Pro |
Writes · 3
| Ability | What it does | Read / Write / Destructive | Edition |
|---|---|---|---|
flatsome-add-element | Add Flatsome Element | Write | Pro |
flatsome-edit-element | Edit Flatsome Element | Write | Pro |
flatsome-move-element | Move Flatsome Element | Write | Pro |
Destructive effects; inspect confirmation policy · 2
| Ability | What it does | Read / Write / Destructive | Edition |
|---|---|---|---|
flatsome-delete-element | Delete Flatsome Element | Destructive | Pro |
flatsome-set-content | Set Flatsome Content | Destructive | Pro |
Names drop the wppilot/ prefix. All 11 are GoBuildWP Pro and load only while the Flatsome plugin or theme is active. Supported writes are recorded in the change ledger with a redacted before and after, and reversible ones can be rolled back.
Working safely with UX Builder paths
Paths shift after every structural edit
A path such as [0, 2] means the third child of the first root node, and it is only true for the tree the agent last read. Insert an element above it and the same content is now at [0, 3]; delete a row and everything after it moves up. flatsome-move-element adds one more wrinkle: its destination path is read against the tree with the moving node already removed. An agent that plans five structural edits from one read will put the fourth and fifth in the wrong place.
The working rule is one structural change, then flatsome-get-content again. Option edits through flatsome-edit-element do not move anything, so several of those can follow one read. Where an element carries UX Builder's own _id, ask the agent to match on it as well as the path, which catches a stale path before it writes.
Getting a deleted Flatsome section back
flatsome-delete-element removes the node and everything inside it from the page content, and its own description is plain that only a post revision holds the subtree afterwards. Before deleting anything on a page that matters, make sure WordPress revisions are enabled for it, then check the change list for the entry the delete created. If that entry cannot be undone, list-revisions and restore-revision in GoBuildWP Free can bring the earlier version back, with one catch: restoring a revision restores the whole page, so any edits made after the delete are lost and need to be made again.
Flatsome shop pages with the WooCommerce module
Most Flatsome sites are shops, and the work usually spans both layers: the UX Builder layout of a landing or category page, and the product data it displays. Keep them separate in the prompt. The Flatsome abilities place and configure Flatsome's own product elements; the WooCommerce abilities change the products. One product's basic fields can be edited in GoBuildWP Free, while variations, categories and bulk price changes need Pro. A prompt that works: "Read the Black Friday landing page tree, list the product elements and the products or categories each shows, then propose which products to swap. Change nothing until I approve."
If the site is moving off Flatsome
Stores often change theme during a redesign.GoBuildWP Pro's page builder converter can read Flatsome UX Builder pages and write them as new drafts in another supported builder, leaving the source page untouched, after a preview that lists what survives whole, what is approximated and what falls back to raw markup. Run convert-preview on your most complex page first; that report is the honest estimate of how much rebuilding the move will need.
FAQ
Flatsome MCP questions about UX Builder
Other builders: Elementor, Bricks, Breakdance, Divi, Oxygen, Beaver Builder, WPBakery, Etch, Mosaic.
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 GoBuildWP Free running inside your WordPress install, and GoBuildWP Pro adds 11 typed Flatsome abilities.
Will the page still open in UX Builder afterwards?
It is designed to. Content written by the module keeps the nesting aliases, responsive attributes and element ids the editor relies on, and the editor's own save may drop options equal to their default and reorder attributes, which changes bytes rather than meaning. Elements and options outside the installed schema are not covered, so open the page in UX Builder and check the front end after each change.
Does it handle responsive settings?
Flatsome writes a per-breakpoint value as its own attribute. The module exposes these as a per-option map instead, so you ask for six columns on desktop and twelve on mobile. 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. The Flatsome module and full product editing are in Pro, and an agent can use them in the same conversation.
Which Flatsome versions are supported?
The module declares Flatsome 3.20 as its floor and was built and verified against 3.20.9. Child themes are supported and report the parent theme's version.
Requirements
Flatsome 3.20, child themes and hard limits
Requirements
- WordPress
- 6.9 or newer, PHP 8.0 or newer.
- Flatsome
- 3.20 or newer; built and verified against 3.20.9. Child themes supported.
- Theme options
- Not covered: Theme Bridge has no Flatsome adapter, so header builder, typography and colours stay in Flatsome's own Theme Options.
- GoBuildWP
- Free plugin plus a Pro licence for the 11 Flatsome abilities.
- Current versions
- GoBuildWP Free 1.18.6 and Pro 1.12.4.
Limits
- 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 have no escape for it. Such a value is refused, not mangled.
- The element catalogue loads 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.
First run
Install GoBuildWP Free
WordPress 6.9+ and PHP 8.0+; the site becomes its own MCP endpoint.
Connect a client
OAuth 2.1 in the browser, or an Application Password where the client cannot sign in.
Read one page tree
flatsome-get-content returns every node with its path and responsive values.
Insert at a path
With Pro, add one row at a path on a draft and open the page in UX Builder.
Setup guide · OAuth 2.1 · Application Passwords · Client guides
Open a Flatsome page as a tree of paths.
Connect read-only and read one UX Builder page; each node comes back with the path an edit would use.