GoBuildWP Pro · 49 Bricks abilities
Bricks MCP that patches one element, not the whole page. Components, classes and templates included.
GoBuildWP's Bricks MCP server gives Claude, ChatGPT, Codex or Cursor 49 typed Bricks abilities in GoBuildWP Pro: read content trees by area, patch a single element, carve components out of existing sections, verify dynamic data, and manage global classes, theme styles, variables and template conditions. The MCP server itself is the free GoBuildWP plugin on your own site.
Pro from $39/year, Bricks active, 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.
Element-level edits
Patch one Bricks element, carve out a component
The module is built around changing the smallest thing that works: one element by id, one insertion at a position, one component lifted from a section that already exists.
- Reads
- 21
- Writes
- 19
- Destructive effects
- 9
bricks-patch-elementsTargeted updates to named elements without re-sending the tree, so a long page is changed by id, not rewritten.
bricks-insert-contentAdds elements before, after, or inside an existing element, instead of replacing the area.
bricks-create-componentCarves a component out of an existing page subtree, then bricks-apply-component places lightweight instances.
bricks-delete-componentRefuses by default while instances exist and returns the affected posts, so nothing is orphaned silently.
bricks-resolve-dynamic-dataRenders one dynamic tag against a real post. Bricks leaves unknown tags as literal text, so this is the proof it works.
bricks-list-template-conditionsAn empty condition list never renders. This is the check behind most "the site has no header" reports.
Patches and components
Why a patch beats re-sending the content tree
Bricks keeps each area of a page, header, content and footer, as one array of elements that point at their parents. A tool that rewrites the whole array to change one heading has to reproduce forty other elements exactly, and a model working from memory seldom does. bricks-patch-elements changes the elements it names and leaves the rest of the array untouched; bricks-insert-content and bricks-remove-content do the same for structure.
Components take repetition out of pages. bricks-create-component lifts an existing subtree into a component, and bricks-apply-component places a small instance that points at it, so the body is stored once. Editing a component re-renders every instance, which is why the agent lists components first.
Guard rails on Bricks writes
- Code elements refused. A write that adds or changes raw code is rejected unless the call sets allow_code_elements, and that opt-in is accepted only on the Developer Full Access profile; native elements are the default.
- Components protected. Deleting a component is refused while instances exist, and the reply lists the pages that still use it.
- Hard deletes confirmed. Removing a global class, variable, theme style or palette colour strips it from every element that used it, so each call needs explicit confirmation.
- Conditions read back. An empty condition list means a template never renders, so conditions are read before and after a write.
Bricks 2.4 abilities
Bricks' own AI abilities, a community server and GoBuildWP
Bricks 2.4 added AI abilities of its own, registered with the WordPress Abilities API and exposed through the MCP Adapter. Bricks Academy calls the feature experimental and advises keeping it off on production sites. GoBuildWP is a separate plugin with its own endpoint; we have not published a test of both running on one site.
| Bricks 2.4 abilities | cristianuibar/bricks-mcp | GoBuildWP Pro | |
|---|---|---|---|
| Status | Experimental, introduced in Bricks 2.4. | Not stated in the README. | Released in Pro 1.12.4. |
| Connection | MCP Adapter; remote clients through @automattic/mcp-wordpress-remote. | Connect commands for Claude Code, Claude Desktop and Cursor. | GoBuildWP's own HTTPS endpoint, from any MCP client. |
| Auth | Application Passwords, WordPress capabilities and Bricks' builder access controls. | Application Passwords. | OAuth 2.1, an Application Password or a scoped access token. |
| Code and PHP | PHP abilities stay off unless the BRICKS_ENABLE_PHP_ABILITIES constant is set, and are meant for development or staging. | Not documented. | No ability runs PHP directly, but a Bricks code element set to execute runs PHP when the page renders. New or changed code needs the allow_code_elements opt-in, accepted only on the Developer Full Access profile. |
| Element-level patch | Element abilities; patch granularity not documented. | Not documented. | Yes: patch, insert and remove elements by id. |
| Components and classes | Design system, theme styles, templates, WooCommerce templates and media. | Global classes, theme styles, WooCommerce templates and Unsplash media. | Components, global classes, theme styles, variables, palette and template conditions. |
| Undo | Revision history is among the documented abilities. | Not documented. | Change ledger with rollback for reversible writes. |
| Requirements | Bricks 2.4. | WordPress 6.4+, PHP 8.2+, Bricks 1.6+. | WordPress 6.9+, PHP 8.0+, the Bricks theme active. |
Where the other route is stronger. Bricks' abilities come from the builder's own team, so they follow its data model as it changes, cost nothing beyond Bricks, and ship with a Skills package, per-user and per-role scoping and revision history. If you automate only Bricks and can keep an experimental feature on staging, start there.
Competitor cells come from the vendors' own pages, seen 29 September 2026; “not documented” means the source is silent, not that the feature is missing: Bricks Academy: AI abilities and skills, cristianuibar/bricks-mcp.
Bricks work
Four Bricks jobs, with the prompt that starts each
Patch one element without rewriting the page
Propose a patch to one element in the existing tree. Compare the saved subtree and siblings against the before-state; native serialization and editor behavior still require verification.
Example prompt: Patch only the CTA element in this content tree to use the existing button global class. Do not touch sibling elements.
Turn a repeated section into a component
Create a Bricks component from an existing structure and apply it, so future edits happen in one place.
Example prompt: Create a component from this pricing section, then apply it on the two other pages that duplicate it.
Check template conditions before a global change
List which templates apply where, so a header edit does not silently change every page.
Example prompt: List the template conditions on this site and tell me which pages the header template applies to.
Wire dynamic data you can trust
List the tokens by provider, then resolve one against a real post before it is saved into content.
Example prompt: Find the ACF field for the client name and resolve it against case study 214 before you use it in the card.
All 49
The full Bricks module, grouped by effect
Reads never change the site, and bricks-list-elements returns any element's control schema before a write. Every call in the destructive group needs explicit confirmation.
Reads · 21
| Ability | What it does | Read / Write / Destructive | Edition |
|---|---|---|---|
bricks-check-setup | Check Bricks Setup | Read | Pro |
bricks-get-color-palette-entry | Get Bricks Color Palette Entry | Read | Pro |
bricks-get-content | Get Bricks Content | Read | Pro |
bricks-get-global-class | Get Bricks Global Class | Read | Pro |
bricks-get-settings | Get Bricks Settings | Read | Pro |
bricks-get-theme-style | Get Bricks Theme Style | Read | Pro |
bricks-get-variable | Get Bricks Global Variable | Read | Pro |
bricks-list-color-palette | List Bricks Color Palette | Read | Pro |
bricks-list-components | List Bricks Components | Read | Pro |
bricks-list-dynamic-data | List Bricks Dynamic Data | Read | Pro |
bricks-list-elements | List Bricks Elements | Read | Pro |
bricks-list-global-classes | List Bricks Global Classes | Read | Pro |
bricks-list-interaction-events-and-actions | List Bricks Interaction Events And Actions | Read | Pro |
bricks-list-interactions | List Bricks Interactions | Read | Pro |
bricks-list-settings | List Bricks Settings | Read | Pro |
bricks-list-template-condition-schema | List Bricks Template Condition Schema | Read | Pro |
bricks-list-template-conditions | List Bricks Template Conditions | Read | Pro |
bricks-list-templates | List Bricks Templates | Read | Pro |
bricks-list-theme-styles | List Bricks Theme Styles | Read | Pro |
bricks-list-variables | List Bricks Global Variables | Read | Pro |
bricks-resolve-dynamic-data | Resolve Bricks Dynamic Data | Read | Pro |
Writes · 19
| Ability | What it does | Read / Write / Destructive | Edition |
|---|---|---|---|
bricks-add-color-palette-entry | Add Bricks Color Palette Entry | Write | Pro |
bricks-add-interaction | Add Bricks Interaction | Write | Pro |
bricks-apply-component | Apply Bricks Component | Write | Pro |
bricks-apply-global-class | Apply Bricks Global Class to Element | Write | Pro |
bricks-create-component | Create Bricks Component | Write | Pro |
bricks-create-global-class | Create Bricks Global Class | Write | Pro |
bricks-create-template | Create Bricks Template | Write | Pro |
bricks-create-theme-style | Create Bricks Theme Style | Write | Pro |
bricks-create-variable | Create Bricks Global Variable | Write | Pro |
bricks-edit-color-palette-entry | Edit Bricks Color Palette Entry | Write | Pro |
bricks-edit-component | Edit Bricks Component | Write | Pro |
bricks-edit-global-class | Edit Bricks Global Class | Write | Pro |
bricks-edit-interaction | Edit Bricks Interaction | Write | Pro |
bricks-edit-theme-style | Edit Bricks Theme Style | Write | Pro |
bricks-edit-variable | Edit Bricks Global Variable | Write | Pro |
bricks-insert-content | Insert Bricks Content | Write | Pro |
bricks-patch-elements | Patch Bricks Elements | Write | Pro |
bricks-set-post-types | Set Bricks Post Types | Write | Pro |
bricks-set-settings | Set Bricks Settings | Write | Pro |
Destructive effects; inspect confirmation policy · 9
| Ability | What it does | Read / Write / Destructive | Edition |
|---|---|---|---|
bricks-delete-color-palette-entry | Delete Bricks Color Palette Entry | Destructive | Pro |
bricks-delete-component | Delete Bricks Component | Destructive | Pro |
bricks-delete-global-class | Delete Bricks Global Class | Destructive | Pro |
bricks-delete-interaction | Delete Bricks Interaction | Destructive | Pro |
bricks-delete-theme-style | Delete Bricks Theme Style | Destructive | Pro |
bricks-delete-variable | Delete Bricks Global Variable | Destructive | Pro |
bricks-remove-content | Remove Bricks Content | Destructive | Pro |
bricks-set-content | Set Bricks Content | Destructive | Pro |
bricks-set-template-conditions | Set Bricks Template Conditions | Destructive | Pro |
Names drop the wppilot/ prefix. All 49 are GoBuildWP Pro and load only while the Bricks 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.
Requirements
Bricks versions, licences and known limits
Requirements
- WordPress
- 6.9 or newer, PHP 8.0 or newer.
- Bricks
- The Bricks theme, active. bricks-check-setup reports its version, licence and CSS loading mode.
- Dark-mode colours
- Palette dark variants need Bricks 2.2 or newer.
- GoBuildWP
- Free plugin plus a Pro licence for the 49 Bricks abilities.
- Current versions
- GoBuildWP Free 1.18.6 and Pro 1.12.4.
Limits
- Template conditions, global classes and theme styles are site-wide. Treat them as staging-first changes with approval.
- Writes that add or change raw code are rejected unless the call opts in with allow_code_elements, which only the Developer Full Access profile accepts; native Bricks elements are the default.
- Dynamic data depends on the plugins actually installed. Unresolvable tags are reported rather than silently emptied.
- Bricks settings can change editor behaviour for every user, so they sit behind the same gates as other privileged writes.
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 bricks-check-setup
On a Read Only connection it reports the Bricks version, licence and CSS loading mode.
Patch one element
With Pro on staging, change a single element by id, then roll it back once from the Changes screen.
Setup guide · OAuth 2.1 · Application Passwords · Client guides
FAQ
Bricks MCP questions from builders
Other builders: Elementor, Breakdance, Divi, Oxygen, Beaver Builder, WPBakery, Flatsome, Etch, Mosaic.
What is Bricks MCP?
Bricks MCP gives an AI client structured access to Bricks content trees, components, global classes, theme styles and templates through typed abilities. The MCP server itself is GoBuildWP Free running inside your WordPress install, and GoBuildWP Pro adds 49 typed Bricks abilities.
Do Bricks 2.4's own AI abilities replace this?
Not necessarily. Bricks 2.4 added experimental AI abilities exposed through the MCP Adapter, and Bricks advises keeping them off on production. GoBuildWP is a separate plugin whose Bricks module sits next to modules for WooCommerce, ACF, forms and SEO on one endpoint, with safety profiles, a change ledger and Pro approvals. Compare both on staging with your own templates.
Can it run PHP on my site?
Not directly, and not on Read Only or Production Safe. No Bricks ability executes PHP itself, but a Bricks code element set to execute runs PHP when the page renders. A write that adds or changes such code is refused unless the call sets allow_code_elements, and that opt-in is accepted only on the Developer Full Access profile. The agent sets the flag itself, so keep production connections off Developer Full Access. Bricks' own PHP abilities are a separate feature that stays off unless the BRICKS_ENABLE_PHP_ABILITIES constant is defined.
Is it safe to use on a production Bricks site?
Start with reads: they change nothing on the site, though whatever they return goes to your AI provider. Template conditions, global classes and theme styles apply site-wide, so change them on staging first. Destructive calls need explicit confirmation, which the agent gives itself unless Confirmation mode is set to "A person approves", and Pro can hold writes until a person approves them.
Can ChatGPT connect to Bricks through GoBuildWP?
Yes. In ChatGPT you create a custom app, paste your site's public GoBuildWP MCP URL, choose OAuth and complete the WordPress authorization. The site needs public HTTPS and an eligible ChatGPT plan. The Bricks abilities then appear like any others, under the same site policy.
Can it edit a single element in a large page?
Yes. bricks-patch-elements targets elements by id instead of re-serialising the whole content tree, and bricks-insert-content adds new elements at a position. That is the safest way to change a long page.
Will it understand my Bricks components?
It lists components, reads their definitions, creates new ones from an existing subtree and applies instances. Editing a component's elements re-renders every instance, so the agent checks the instance count first.
Does this work with Bricksforge?
Bricksforge has its own GoBuildWP Pro module. The two are separate integrations, and each loads only if its plugin is present.
Patch a single Bricks element on staging.
Connect read-only, read one content area, then let the agent change one element by id and undo it.