Page buildersPro
GoBuildWP Mosaic integration: requirements and coverage
Mosaic does not use posts or options for its design data; it has its own tables. The Mosaic MCP abilities in GoBuildWP read and write those rows directly or through Mosaic's services, so the usual change-log undo does not apply to any of them. This reference groups the calls by table and lists what each leaves behind.
Supported Mosaic interval: >=1.0.3 and <2.0. Each feature also has a base or Mosaic Pro gate.
On the partners template, change the heading of the second partner card only. The other cards should stay as they are.
wppilot/mosaic-get-element-treeReadReads the partners template and returns the instance nodes, each typed with the card component's UUID.
wppilot/mosaic-list-componentsReadConfirms which component the cards come from and finds the heading node inside it.
wppilot/mosaic-edit-component-instance-overrideWriteWrites an override row under the second instance with just the new heading text; everything else keeps inheriting.
- Edition
- Pro
- Abilities
- 41
- Requires
- WordPress 6.9+, PHP 8.0+, Mosaic 1.0.3+
Requirements and coverage
What this integration needs, and where the detail lives
- Edition
- Pro
- WordPress and PHP
- 6.9+ and 8.0+
- Version floor
- Mosaic 1.0.3+
- Abilities
- 41, listed in the reference
Mosaic MCP guide: setup and worked tasks Mosaic ability reference (mosaic)
Limits
Read first: Mosaic writes have no ledger undo
- Every Mosaic write is recorded in the change log without a before-image, because it lands in Mosaic's tables. Back up those tables before bulk work.
- The module accepts Mosaic Pro from the minimum its setup check names and below the next major, 2.0; a release at or above that is refused until GoBuildWP supports it.
- Soft-deleted rows can only be brought back with direct SQL, and nothing still pointing at them is repaired.
- Some advanced operations check for the Pro edition of Mosaic explicitly and report when it is missing.
Data model
Rows, UUIDs and fractional ordering
Mosaic keeps its records in custom tables such as wp_mosaic_nodes, wp_mosaic_templates, wp_mosaic_themes and wp_mosaic_utility_classes, with JSON in data columns. Every node row belongs to a document of one of four types, template, master, styleGuide or component, and is identified by a UUID. Root nodes carry the document type as their parent type and deeper nodes carry node. Sibling order is a fractional-index string; GoBuildWP generates it with Mosaic's own implementation so the editor sorts inserted elements where you put them.
A component instance is a node whose type names the component's UUID. An override on one instance is a separate row in the host document, with parent type override, pointing at the instance, and only the overridden properties set. New templates are created through Mosaic's service layer so they are wired into the design-system graph; a bare row would make the editor and renderer throw. Deletes are soft: status flips to delete and the row is hidden from reads and rendering, but references to it are not scrubbed.
Worked example
One instance of a shared card, reworded
Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.
The second card differs and the rest follow the component. To go back, mosaic-clear-component-instance-override removes that override row; the change log has no before-image for it.
Before editing, read or export the existing override. Clearing a newly added override restores inheritance; clearing an override that already existed does not restore its prior value. Check base versus Pro feature gates for each operation.
mosaic-get-element-treeReads the partners template and returns the instance nodes, each typed with the card component's UUID.
mosaic-list-componentsConfirms which component the cards come from and finds the heading node inside it.
mosaic-edit-component-instance-overrideWrites an override row under the second instance with just the new heading text; everything else keeps inheriting.
Questions
Mosaic questions
Can I roll back a Mosaic change from GoBuildWP's Changes screen?
No. The change is listed, but Mosaic writes to its own tables and the ledger can only restore posts, options and terms. Undo is the inverse call where one exists, such as clearing an override you added (clearing one that already existed does not bring its earlier value back), or a database backup.
Why doesn't the element tree show my instance overrides?
Overrides are separate rows with parent type override, and the tree read follows node children only. Use the override abilities to set or clear them.
Does inserting an element between existing ones disturb their order?
No. Order is a fractional-index string, and GoBuildWP computes new keys with Mosaic's own function, so an insertion sorts correctly in the editor without renumbering its neighbours. That settles ordering only: there is no ledger undo for the write, so check the inserted content and the rendered page afterwards.
This integration targets the Mosaic WordPress builder. Resource-planning, financial, semantic-data and Unity products also use the Mosaic name; their MCP servers cannot operate this builder's documents. Mosaic WordPress builder documentation
Where these facts come from
GoBuildWP behaviour is taken from the plugin source and the ability reference; third-party details from the vendor documentation below, checked by the GoBuildWP team.
Mosaic is a separate product; no partnership or endorsement is implied.