Read a page's tree and change one element without touching the rest
Start by inspecting the relevant setup health state. Ask the agent to show the exact target, intended inputs, affected shared resources, and validation step before it executes.
Flatsome MCP integration
Flatsome workflows, translated into typed AI tools.
Read and write the UX Builder shortcode tree, edit single elements by path, browse the element catalogue and option schemas, insert the theme's own section presets, and work with reusable UX Blocks.
Pro integration profile
Flatsome
Page builders
- setup health
- shortcode tree reads
- whole-tree writes
- element insert, edit, move, delete
- element catalogue
- option schemas
- theme presets
Dependency-aware · isolated loading · live schema discovery · licence-gated
New to this? Flatsome MCP covers what you can build, example prompts, and a four-step setup.
Read the Flatsome MCP guide →Why plugin-aware matters
Use Flatsome's structure, not a generic shortcut.
A visual builder stores a structured document tree, schemas, shared design primitives, and template rules. Treating that state as generic HTML can lose editor compatibility or design-system relationships. The WPPilot Pro module gives the agent builder-specific nouns and operations so it can inspect structure before it proposes a change.
Capability map
What the Flatsome module can work with
setup healthshortcode tree readswhole-tree writeselement insert, edit, move, deleteelement catalogueoption schemastheme presetsUX Blocks inventory
This is a human-readable capability map. The live WPPilot ability registry and its input schemas remain authoritative for exact operations and parameters on your installed version.
Flatsome workflow examples
Three useful ways to put the module to work.
Each example begins with discovery and a read. Writes should follow only after the current structure, dependencies, and review path are clear.
Start a new section from a preset the theme ships rather than hand-written markup
Start by inspecting the relevant shortcode tree reads state. Ask the agent to show the exact target, intended inputs, affected shared resources, and validation step before it executes.
Find the reusable block behind a repeated section before rebuilding it
Start by inspecting the relevant whole-tree writes state. Ask the agent to show the exact target, intended inputs, affected shared resources, and validation step before it executes.
A production-minded sequence
From idea to verified Flatsome change.
The module makes the operation typed. Your workflow still determines whether the outcome is trustworthy.
- 1
Inspect the existing document or element tree
Keep the target narrow, record what evidence was checked, and report any external or visual path that remains unverified.
- 2
Read the live element or style schema
Keep the target narrow, record what evidence was checked, and report any external or visual path that remains unverified.
- 3
Identify shared classes, variables, presets, or components
Keep the target narrow, record what evidence was checked, and report any external or visual path that remains unverified.
- 4
Apply the smallest coherent structural change
Keep the target narrow, record what evidence was checked, and report any external or visual path that remains unverified.
- 5
Validate the native editor and responsive output
Keep the target narrow, record what evidence was checked, and report any external or visual path that remains unverified.
Operating boundary
A module is capability, not blanket permission.
- The companion plugin or theme must be present where required
- WPPilot Free and an active Pro licence are required
- The connected WordPress user's capabilities still apply
- The safety profile and per-ability status are enforced
- Critical actions can require confirmation or human approval
- Live schemas and integration health decide current availability
Specific guardrail
What to watch with Flatsome
Nesting aliases, responsive breakpoint attributes and the editor's element ids are handled for you, and a tree that nests one tag past the tenth level is refused rather than silently flattened. Theme options remain Customizer settings served by the Theme Bridge module, and the module does not register new UX Builder elements.
Page-builder success is not only a valid API response. The finished page must still be checked in the native editor and on representative desktop and mobile routes, including templates, dynamic data, responsive rules, fonts, interactions, and caches.
Read the safety checklist →Flatsome MCP FAQ
Practical answers before you connect.
Reviewed against the current WPPilot module and client registries on August 10, 2026.
What does the Flatsome MCP integration do?
Read and write the UX Builder shortcode tree, edit single elements by path, browse the element catalogue and option schemas, insert the theme's own section presets, and work with reusable UX Blocks.
Is Flatsome support included in WPPilot Free?
No. The specialized Flatsome module is part of WPPilot Pro. WPPilot Free supplies the MCP server, connection, policy, core abilities, diagnostics, and change controls that Pro extends.
Does the Flatsome module load on every site?
No. WPPilot Pro checks the relevant dependency and licence state. The live integration health and ability registry are the source of truth for the installed site.
Can an AI agent change Flatsome without review?
Only within the connected WordPress user's capabilities, the active WPPilot safety profile, enabled abilities, and any confirmation or approval requirement. Nesting aliases, responsive breakpoint attributes and the editor's element ids are handled for you, and a tree that nests one tag past the tenth level is refused rather than silently flattened. Theme options remain Customizer settings served by the Theme Bridge module, and the module does not register new UX Builder elements.
What should I test after a Flatsome change?
Page-builder success is not only a valid API response. The finished page must still be checked in the native editor and on representative desktop and mobile routes, including templates, dynamic data, responsive rules, fonts, interactions, and caches. A successful tool result is evidence that an operation returned successfully, not proof that every front-end, provider, or production path is correct.
More page builders
Explore related WPPilot modules.
Use the category page to compare adjacent workflows, then inspect the dedicated module that matches your installed stack.
Page builders
Elementor
Let an AI client inspect Elementor documents and work with elements, schemas, dynamic tags, global classes, variables, and design tokens through WPPilot Pro.
document contentelement schemasadd, edit, and delete elementsatomic widgetsdynamic tags
Explore Elementor Page builders
Bricks
Use WPPilot Pro to work with Bricks content, elements, templates, components, global classes, theme styles, variables, dynamic data, and builder settings.
content treeselementstemplates and conditionscomponentsglobal classes
Explore Bricks Page builders
Breakdance
Connect your AI client to Breakdance-specific elements, templates, conditions, variables, global classes, dynamic data, forms, and global settings.
element treeselement type schemastemplatestemplate conditionsglobal classes
Explore Breakdance Before the first write
Read first. Change one thing. Then look.
The sequence matters more than the tool. Ask the agent to describe what is already there. Check its answer against the plugin itself. If the description is wrong, stop. Nothing written after that will be right.
Once the description matches, make one small change. Not a batch. One. Then open the plugin and look at the result with your own eyes.
A tool result that says success means the call returned. It does not mean the page is correct. Caches, templates, notifications and front-end styles are all outside what the call can see. Nesting aliases, responsive breakpoint attributes and the editor's element ids are handled for you, and a tree that nests one tag past the tenth level is refused rather than silently flattened. Theme options remain Customizer settings served by the Theme Bridge module, and the module does not register new UX Builder elements.
Do the first few sessions on staging. Use a WordPress user created for this connection. Keep the safety profile tight until you have watched a full session in the change ledger. None of that takes long, and it is the difference between a workflow you trust and one you hope about.
Your site · your policy · your AI client
Bring Flatsome into a controlled AI workflow.
Start with WPPilot Free for the MCP foundation. Add Pro when your work needs Flatsome-specific structure, plugin-aware skills, memory, or human approvals.