GoBuildWP Pro · 41 Mosaic abilities
Mosaic MCP that checks the design system before adding to it. Components, templates and tokens included.
GoBuildWP's Mosaic MCP gives an AI client 41 typed abilities for Mosaic Pro, the Nextend builder, in GoBuildWP Pro. It reads element trees for templates, components and style guides, audits a document against Mosaic's own utility classes and variables, and manages collections, utility classes, template assignments and component overrides.
Pro from $39/year, Mosaic 1.0.3+, 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.
Design-system check
Audit a Mosaic document against its own tokens before adding more
mosaic-check-design-system reads every element of a template, component, master or style guide and reports the ones styled outside Mosaic's utility classes and theme variables. Running it first tells the agent which values already have a token, so a fix binds to the system instead of adding a near-duplicate class.
Mosaic keeps its own themes, templates, components and design-token collections in custom tables, separate from WordPress themes. The module speaks that model directly rather than mapping it onto a generic element tree.
Most Mosaic deletes are soft: the row's status flips and it disappears from every read and from the editor, but references are not scrubbed. The agent is told exactly that, so it checks for elements still using a class or variable before removing it.
Guard rails on Mosaic writes
- Soft deletes. Most deletes flip a status and hide the row without scrubbing references, so the agent looks for users of a class or variable first.
- Version band. The setup check rejects a Mosaic release at or above the supported maximum.
- Bounded repair. Legacy data repair is transactional, capped at 1,000 rows and can roll back the most recent repair.
- Concurrent edits refused. A collection edit fails if another writer changed the row after it was read.
Design-system jobs
Mosaic jobs that keep the token set small
Check the design system first
Confirm the system is coherent before the agent adds utility classes of its own.
Example prompt: Run the Mosaic design system check and summarise anything inconsistent before we add new utility classes.
Fix component drift
Find instance overrides and clear the ones that no longer differ from the definition.
Example prompt: Show every component instance override on this page and clear the ones that no longer differ from the definition.
Assign templates with intent
Set or clear a template assignment as an explicit operation.
Example prompt: List template assignments and tell me which template renders the landing pages.
Repair legacy data safely
Run the dry-run check, read the report, then repair as a separate reviewed step.
Example prompt: Run the legacy data check and explain what a repair would change. Do not repair yet.
Complete module
All 41 Mosaic abilities, grouped by effect
Reads · 17
| Ability | What it does | Read / Write / Destructive | Edition |
|---|---|---|---|
mosaic-check-design-system | Check Mosaic Design-System Compliance | Read | Pro |
mosaic-check-legacy-data | Check Mosaic Legacy Data | Read | Pro |
mosaic-check-setup | Check Mosaic Setup | Read | Pro |
mosaic-get-collection | Get Mosaic Collection | Read | Pro |
mosaic-get-element-tree | Get Mosaic Element Tree | Read | Pro |
mosaic-get-template | Get Mosaic Template | Read | Pro |
mosaic-get-theme | Get Mosaic Theme | Read | Pro |
mosaic-get-theme-settings | Get Mosaic Theme Settings | Read | Pro |
mosaic-get-utility-class | Get Mosaic Utility Class | Read | Pro |
mosaic-get-variable | Get Mosaic Variable | Read | Pro |
mosaic-list-collections | List Mosaic Collections | Read | Pro |
mosaic-list-components | List Mosaic Components | Read | Pro |
mosaic-list-template-assigns | List Mosaic Template Assigns | Read | Pro |
mosaic-list-templates | List Mosaic Templates | Read | Pro |
mosaic-list-themes | List Mosaic Themes | Read | Pro |
mosaic-list-utility-classes | List Mosaic Utility Classes | Read | Pro |
mosaic-list-variables | List Mosaic Collection Variables | Read | Pro |
Writes · 16
| Ability | What it does | Read / Write / Destructive | Edition |
|---|---|---|---|
mosaic-add-element | Add Mosaic Element | Write | Pro |
mosaic-create-collection | Create Mosaic Collection | Write | Pro |
mosaic-create-template | Create Mosaic Template | Write | Pro |
mosaic-create-utility-class | Create Mosaic Utility Class | Write | Pro |
mosaic-create-variable | Create Mosaic Variable | Write | Pro |
mosaic-edit-collection | Edit Mosaic Collection | Write | Pro |
mosaic-edit-component-instance-override | Edit Mosaic Component-Instance Override | Write | Pro |
mosaic-edit-element | Edit Mosaic Element | Write | Pro |
mosaic-edit-template | Edit Mosaic Template | Write | Pro |
mosaic-edit-theme-settings | Edit Mosaic Theme Settings | Write | Pro |
mosaic-edit-utility-class | Edit Mosaic Utility Class | Write | Pro |
mosaic-edit-variable | Edit Mosaic Variable | Write | Pro |
mosaic-move-element | Move Mosaic Element | Write | Pro |
mosaic-set-template-assign | Set Mosaic Template Assign | Write | Pro |
mosaic-set-utility-class-style | Set Mosaic Utility Class State Style | Write | Pro |
mosaic-set-variable-value | Set Mosaic Variable Value | Write | Pro |
Destructive effects; inspect confirmation policy · 8
| Ability | What it does | Read / Write / Destructive | Edition |
|---|---|---|---|
mosaic-clear-component-instance-override | Clear Mosaic Component-Instance Override | Destructive | Pro |
mosaic-clear-template-assign | Clear Mosaic Template Assign | Destructive | Pro |
mosaic-delete-collection | Delete Mosaic Collection | Destructive | Pro |
mosaic-delete-element | Delete Mosaic Element | Destructive | Pro |
mosaic-delete-template | Delete Mosaic Template | Destructive | Pro |
mosaic-delete-utility-class | Delete Mosaic Utility Class | Destructive | Pro |
mosaic-delete-variable | Delete Mosaic Variable | Destructive | Pro |
mosaic-repair-legacy-data | Repair or Roll Back Mosaic Legacy Data | Destructive | Pro |
Names drop the wppilot/ prefix. All 41 are GoBuildWP Pro and load only while the Mosaic 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.
Mosaic's vocabulary
Six Mosaic abilities worth knowing by name
- Reads
- 17
- Writes
- 16
- Destructive effects
- 8
mosaic-check-design-systemAudits every element of a document for styles that bypass Mosaic's utility classes and theme variables.
mosaic-check-setupReports the supported version band, where a Mosaic release at or above the maximum is rejected, and table provisioning.
mosaic-edit-component-instance-overrideOverrides properties on one instance without touching the shared component or its other instances.
mosaic-set-template-assignBinds a single post to a template explicitly, instead of as a side effect of editing content.
mosaic-set-variable-valueSets a design token's value for one skin and one mode, checked against the variable's type.
mosaic-repair-legacy-dataTransactional, bounded to 1,000 rows, records affected ids, and can roll back the most recent repair.
Requirements
Mosaic Pro, its tables and the supported version band
Requirements
- WordPress
- 6.9 or newer, PHP 8.0 or newer.
- Mosaic
- Mosaic Pro 1.0.3 or newer, inside the version band the setup check reports.
- Database
- Mosaic's custom tables must be provisioned; the setup check confirms it.
- GoBuildWP
- Free plugin plus a Pro licence for the 41 Mosaic abilities.
- Current versions
- GoBuildWP Free 1.18.6 and Pro 1.12.4.
Limits
- Utility classes and theme settings are site-wide; adding them casually is how a design system degrades.
- Soft deletes do not scrub references. Elements still naming a deleted class or variable lose its styles.
- Legacy data repair changes stored structures: run the check, read the report, and back up before repairing.
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.
Run the setup check
mosaic-check-setup confirms the version band and that Mosaic's tables are provisioned.
Audit one template
Run the design-system check on one template and read the report before any write.
Setup guide · OAuth 2.1 · Application Passwords · Client guides
Tokens, skins and retiring things cleanly
Collections, variables, skins and modes
Mosaic organises design tokens as collections under a theme, with variables nested in each collection. mosaic-create-collection is meant to be used once per token family, such as brand colours or spacing, and mosaic-create-variable adds tokens to it. A variable can hold a different value per skin and per mode, which is how one token serves a light and a dark presentation. mosaic-set-variable-value writes one skin and mode at a time, defaults to the collection's own when you leave them out, and checks the value against the variable's type first, so a colour that is not a colour, or a length without a unit, is refused rather than stored.
For an agent, that structure is the useful constraint. Ask it to read the collections and variables before it styles anything, and to set an existing variable's value for a mode rather than creating a near-duplicate token.
Retiring a class or variable without broken styles
Deletes in Mosaic are soft, and they do not follow references. A deleted utility class disappears from the editor and from every read, but elements that used it still print the class name in the HTML with no rules behind it. A deleted variable leaves every style that names it pointing at a custom property that no longer resolves. Deleting a collection does not delete its variables either; they stay in the table attached to a collection that is gone.
So retirement is a sequence, not one call: find the elements and styles that use the class or variable, repoint each one to its replacement, read the affected templates again to confirm nothing still names the old one, and only then delete. For a collection, delete its variables first. A good prompt states that order outright: "Replace every use of the old accent variable with brand-primary, show me the elements you changed, then delete the old variable."
Theme settings: merge, not replace
mosaic-edit-theme-settings merges by default, keeping keys you did not send, such as the default font stack and breakpoints. Its replace mode makes the payload the entire settings object. Reserve replace for a deliberate reset with a full copy of the settings in hand, and keep it out of prompts written for routine changes.
Mosaic is also one of the builders GoBuildWP's page builder converter does not read or write, so a move between Mosaic and another builder stays a manual rebuild.
FAQ
Mosaic MCP questions about tokens and repairs
Other builders: Elementor, Bricks, Breakdance, Divi, Oxygen, Beaver Builder, WPBakery, Flatsome, Etch.
What is Mosaic MCP?
Mosaic MCP gives an AI client typed access to Mosaic element trees, templates, collections, components, utility classes, themes and design-system checks. The MCP server itself is GoBuildWP Free running inside your WordPress install, and GoBuildWP Pro adds 41 typed Mosaic abilities.
What does the design system check do?
It audits every element of a Mosaic document for styles that come from outside Mosaic's own utility classes and theme variables. It reports and changes nothing. Reading that report before a write shows which values already have a token, so you and the agent can reuse them instead of adding near-duplicate classes; it does not block a new class.
Can it fix component drift?
It can edit and clear instance overrides, which is usually the cause. Clearing an override returns that instance to the component definition without touching other instances.
Is legacy data repair safe to automate?
Run the dry-run check and read the report first. The repair is transactional, bounded to 1,000 rows and records the affected ids, and the most recent repair can be rolled back, but treat it as a reviewed migration.
Does it work with the free edition of Mosaic?
The module targets Mosaic Pro, and a handful of advanced operations check for the Pro edition explicitly. The setup check reports the edition and distribution channel before anything else runs.
Audit one Mosaic template before adding a class.
Connect read-only, run the design-system check on a template, and fix only what it reports.