Get the plugin
WP MCP/Integrations/Page builders

Page builders integration

Bricks AI agent tool reference

Bricks stores its layouts in its own structured format. WP MCP detects when a page is built with Bricks and exposes its content for reading and writing over MCP, so an AI agent can edit Bricks pages the same way it edits the rest of your site, snapshotted before every write and reversible. A write does what Bricks' own save does after the layout row: it sets the editor mode that makes Bricks render the page, and when Bricks is loaded with CSS set to external files it rebuilds the page's CSS file, after a rollback too. Header and footer templates are written to their own header or footer row and get the same CSS rebuild. A post Bricks cannot edit (not a Bricks template, not a post type enabled in the Bricks settings, and holding no Bricks data) is refused with a message naming the setting to change. With scope set, the read also returns the site-wide design system (global classes, variables and color palettes), local templates including headers and footers, and the element catalog with each element's controls, and a design-system write adds, updates or removes one class, variable or palette color, refused if that data changed since it was read and undone with rollback-operation. Bricks support is a Pro capability, and it's one most WordPress MCP tools simply don't offer.

detect-builderget-builder-contentupdate-builder-content

In practice

How Bricks work goes with an agent.

A Bricks page keeps its layout as a native PHP array in the _bricks_page_content_2 meta row, while headers and footers sit in separate rows on bricks_template posts. The site-wide pieces live in options: global classes, global variables and color palettes. WP MCP reads and writes all of these directly, so Bricks does not have to be loaded for a page read or write. That matters for staging copies and scripted clean-ups. A page write replaces the whole element list as one JSON array, while the design lists are edited one entry at a time.

Rename the btn-primary global class to button-main.

Runs get-builder-content with scope design_system, then update-builder-content on classes/<id> with the hash from hashes.classes. The entry is validated (no spaces, no leading dot, name not already taken), the bricks_global_classes option is snapshotted whole first, and the classes timestamp is bumped so an open Bricks editor is warned.

Add our new teal to the main color palette.

Runs get-builder-content with scope design_system, then update-builder-content with operation add and to set to palettes/<palette id>. A color needs a light, raw or hex value, gets a generated id, and the bricks_color_palette option is snapshotted first. Bricks' style manager CSS is rebuilt when Bricks is loaded.

Replace the hero copy on the landing page with this text and leave everything else alone.

Runs get-builder-content to fetch the element list, then update-builder-content with the edited list as a JSON string. Malformed JSON is refused before any snapshot is taken; a valid write snapshots the post and its meta first. There is no hash check on Bricks pages, so the read and the write belong in one pass.

Which templates control the footer on blog posts?

Runs get-builder-content with scope templates, which lists every bricks_template post with its type, its conditions, its settings and its elements, header and footer rows included. It is a read: nothing is snapshotted because nothing changes.

What your AI can do

Real Bricks operations, every write reversible.

  • Detect whether a page is built with Bricks
  • Read a Bricks page's structured content
  • Update Bricks content, snapshotted and reversible
  • Write header and footer templates to their own rows
  • Set the Bricks editor mode and rebuild the page CSS file after a write or an undo
  • Refuse a post Bricks is not set up to edit, naming the setting to change
  • Read the Bricks design system: global classes, variables and color palettes
  • Add, update or remove a global class, variable or palette color, each change undoable
  • Read local templates, headers and footers, and the element catalog with its controls
  • Work alongside the full WP MCP surface on the same site

Example prompts

Example Bricks prompts.

Is the homepage built with Bricks or Elementor?

Update the hero heading on the Bricks-built landing page.

Roll back the last change I made to the Bricks pricing section.

Under the hood

The Bricks calls, under the hood.

wpmcp, bricks

detect-builder({ post_id: 8 }), reports the builder in use

update-builder-content({ post_id: 8, … }), snapshotted, restorable

Safety and access

What can be undone on Bricks, and what costs what.

Recoverable on Bricks

  • A page write snapshots the whole post row and its meta, so rollback-operation restores the element list exactly, then resets the editor mode and rebuilds the page CSS the way the write did.
  • A design write snapshots the one option it changes (classes, variables or palettes), and a rollback puts that whole option back.
  • After a design rollback the style manager CSS and the classes timestamp are refreshed, the same as after the write.

Bricks limits and opt-ins

  • Page writes replace the whole element list. Bricks has no per-element operations and no content hash here.
  • Header and footer templates are written to their own header or footer row; template conditions and the element catalog are read-only, and the catalog needs Bricks loaded.
  • The page CSS file is rebuilt only when Bricks is loaded and its CSS loading is set to external files; with inline CSS there is no file to rebuild.
  • Design writes cover classes, variables and palettes only, need the edit_theme_options capability, and must pass the hash of the list from the read.

Free or Pro: Every Bricks tool is Pro: detect-builder, get-builder-content (including the design_system, templates and catalog scopes) and update-builder-content. On the free tier, search-content still finds text inside Bricks elements and returns a bricks/element/<id> location for each hit, and export-content with mirror:true writes Bricks pages to JSON files you can keep in git. Page writes need no opt-in filter.

Part of WP MCP Pro

The Bricks integration is part of WP MCP Pro.

One Pro licence unlocks the Bricks tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.

Frequently asked

Bricks MCP: questions, answered.

Which builders does WP MCP support beyond Elementor?

On the Pro tier, the same three builder tools cover Bricks, Divi, WPBakery, Beaver Builder, Breakdance, Oxygen (6 and classic 4.x), Avada and Thrive Architect. The Gutenberg block editor is supported on the free tier.

Are Bricks edits reversible?

Yes, every write routes through the snapshot engine, so you can undo a change or a whole session.

Will the page look right after an agent edits it?

Yes. Like Bricks' own save, a write sets the editor mode Bricks renders from and, when Bricks is loaded and CSS loading is set to external files, rebuilds the page's post CSS file. An undo does the same, so the styles never lag behind the restored layout.

Does Bricks have to be installed for WP MCP to read a page?

No for pages: the element list is plain post meta, so reads and writes work without calling into Bricks. The element catalog needs Bricks loaded, and the page CSS file and the style manager CSS are rebuilt after a write only when Bricks is loaded.

Can an agent edit a single Bricks element?

Not as a one-element operation. It reads the element list, changes what it needs and writes the full list back as JSON. Global classes, variables and palette colors are different: each entry is addressed and edited on its own.

Can it find text inside Bricks elements without opening every page?

Yes. The free search-content tool indexes Bricks element settings, which a post_content search cannot see, and each hit carries a bricks/element/<id> location the agent can use when it reads the page.

What protects a Bricks page I am editing at the same moment?

For page content, nothing beyond the snapshot: a Bricks page write has no hash check, so it replaces whatever is stored. Tell the agent to read and write in one pass. The global class, variable and palette lists do refuse a write when their hash is stale.

Is there an AI agent for Bricks?

Yes, through WP MCP rather than Bricks itself. An agent you choose, such as Claude or Cursor, can detect whether a page is built with Bricks. WP MCP is a separate plugin, not a built-in AI feature of Bricks. On the undo side: A page write snapshots the whole post row and its meta, so rollback-operation restores the element list exactly, then resets the editor mode and rebuilds the page CSS the way the write did.

Point your AI at Bricks.