Page buildersPro
GoBuildWP Bricks integration: requirements and coverage
Use this Bricks MCP abilities reference to see what each GoBuildWP call writes inside a Bricks site. Page elements, global classes, components, theme styles and palette colours live in separate stores, and the store decides two things: whether a call touches one post or every page, and what rolling it back will restore.
The pricing cards are pasted on three pages. Make them a single component and replace the copies.
wppilot/bricks-get-contentReadReads the content area of the first page and returns the flat element list, so the card wrapper's id and its descendants are known.
wppilot/bricks-create-componentWriteCopies that subtree into a new entry in bricks_components and returns its component id. It places no instance, so the first page still holds its pasted copy at this point.
wppilot/bricks-apply-componentWriteOn each of the three pages, inserts an instance after the heading, the first page included; the instance only references the component id.
wppilot/bricks-remove-contentConfirm firstOn each page, removes the old pasted copy, subtree and all. This is destructive, so each removal waits for confirmation.
- Edition
- Pro
- Abilities
- 49
- Requires
- WordPress 6.9+, PHP 8.0+
Requirements and coverage
What this integration needs, and where the detail lives
- Edition
- Pro
- WordPress and PHP
- 6.9+ and 8.0+
- Abilities
- 49, listed in the reference
Bricks MCP guide: setup and worked tasks Bricks ability reference (bricks)
Data model
Areas in post meta, everything shared in option rows
Bricks is a theme, and it stores a page's elements in post meta with one key per area: header, content and footer. Within an area the elements form a flat array. Each carries an id, a name, a parent reference and its settings, and the nesting is derived from the parent references, which is why bricks-set-content accepts a flat list and computes children itself. Page settings go to _bricks_page_settings, and a successful write sets the post's editor mode to Bricks so the page renders through the builder.
Templates are posts of Bricks' template type. The template's type picks the area its elements belong in (a header template writes the header key, most other types the content key), and its conditions are stored on the template post. Shared design is kept in option rows: global classes and their categories, variables and their categories, theme styles, the colour palette, components as one flat array in bricks_components, and the global settings that include the list of post types Bricks may edit.
Limits
Bricks limits worth knowing before a write
- The module loads only while the Bricks theme is active. No base minimum is enforced in this local manifest; that is not a tested compatibility range. Dark-mode palette variants need Bricks 2.2 or later. Verify the installed release before writes.
- Writing a store's option directly, for example through execute-php, is what the Bricks skill forbids: a hand-copied variable can end up sharing an id with another, which Bricks cannot untangle.
- A page whose post type is not enabled for Bricks saves but never renders through the builder. Fix it with set-post-types before building.
- Global classes, theme styles, palette colours and template conditions reach the whole site. Rollback exists, but the change is live on every page until you use it.
Worked example
Turning three copied pricing blocks into one component
Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.
Three pages now render one component, and a later edit to it changes all of them. Each page write can be rolled back from its own snapshot; the component row can be restored separately.
Creating a component saves a subtree; it need not replace the original instance. Convert or apply the source page as well as the other two pages, or report only two changed pages. Inspect all intended pages.
bricks-get-contentReads the content area of the first page and returns the flat element list, so the card wrapper's id and its descendants are known.
bricks-create-componentCopies that subtree into a new entry in bricks_components and returns its component id. It places no instance, so the first page still holds its pasted copy at this point.
bricks-apply-componentOn each of the three pages, inserts an instance after the heading, the first page included; the instance only references the component id.
bricks-remove-contentOn each page, removes the old pasted copy, subtree and all. This is destructive, so each removal waits for confirmation.
Questions
Bricks questions
Where do the elements of a Bricks header template go?
Into the header area key on the template post. GoBuildWP maps the template type to its area the way Bricks does: header and footer types to their own keys, every other type to content. Writing a header's elements into the content key would leave the header empty.
What happens to pages when a Bricks component is deleted?
By default nothing, because the call refuses and lists the affected posts. You then choose inline, which expands each instance into plain elements, or remove, which deletes the instances too. Either rewrites pages that the rollback of the component row will not touch.
Why is there a separate call for Bricks post types?
Enabling a post type is the most common setup fix, and the general settings call touches many unrelated keys. set-post-types writes only the enabled list, so a setup repair cannot change anything else in the settings row.
How does GoBuildWP know Bricks' option names if Bricks is closed source?
It reads them from the theme's own constants at runtime instead of restating them. On a site where those constants do not resolve, a write is recorded without a before-image rather than against a guessed option.
Bricks MCP Open is a separate open-source server. Compare its client-side setup, bridge plugin and native editing operations with the GoBuildWP module on the same staging site. Bricks MCP Open repository
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.
Bricks is a separate product; no partnership or endorsement is implied.