Bricks MCP · Pro
Bricks MCP: connect an AI agent to Bricks Builder.
A Bricks MCP server lets an AI agent read and write the element data behind a Bricks Builder page. WP MCP runs inside your WordPress site, speaks to Claude, Cursor or any MCP client, and takes a snapshot before it stores anything.
Self-hosted · snapshot before every write · one-click undo
› Update the hero heading on the Bricks landing page
detect-builder bricks
get-builder-content structured element content
⛨ page and its meta saved
update-builder-content validated, stored the way Bricks stores it
✓ Heading updated. Open the page in Bricks to keep editing.
What it is
What a Bricks MCP server does.
Bricks keeps a page's elements as structured data in post meta rather than in post_content. That is clean to work with, and invisible to any tool that only knows the WordPress editor. A Bricks MCP server closes that gap: it tells the agent a page is a Bricks page, returns the element data, and accepts an edited version back.
WP MCP stores Bricks content the way Bricks itself does, so what an agent writes opens normally in the Bricks editor. The write is checked first: content that is not well-formed is refused before a snapshot is even taken.
Bricks keeps page content as structured data in post meta, which is why content search and generic WordPress tools never see it. The practical question for a Bricks agency is whether an agent can change that data without breaking the editor. WP MCP stores the content in the shape Bricks itself uses, refuses malformed payloads before taking a snapshot, and leaves you with a page that opens normally in Bricks afterwards. The tools are detect, read and write, which is a small surface by design.
Read and change
What WP MCP can read and change in Bricks.
It can read
- Whether a page is built with Bricks, Elementor, Gutenberg or another builder
- A Bricks page's structured element content
- The site-wide design system: global classes, variables and color palettes
- Local templates, including headers and footers, and the element catalog
It can change
- Write updated Bricks content back to the page
- Reject malformed content before anything is stored
- Restore the previous content exactly with a rollback
- Add, update or remove a global class, variable or palette color, refused if it changed since the read
These are the real ability and operation names the agent calls. TheBricks AI agent tool reference page lists the calls in detail.
Example prompts
Three things to ask first.
Is the homepage built with Bricks? If it is, summarise its sections for me.
Change the call-to-action text in the Bricks hero to 'See live demo' and nothing else.
Undo the last change you made to the Bricks pricing page.
Is the pricing page built with Bricks, and what sections does it have?
detect-builder names the builder and get-builder-content returns the element data, which the agent summarises section by section.
Change the call-to-action text in the Bricks hero to "See live demo" and nothing else.
The agent reads the content, changes the one value and calls update-builder-content. The payload is validated, the page snapshotted, then stored.
That last edit broke the layout. Undo it.
rollback-operation restores the previous content exactly, or rollback-session undoes every write from the same agent run.
Safety
Every Bricks write has a way back.
Bricks content is ordinary post meta on the page, which is exactly what the post snapshot captures. Every write goes through the same safety engine as the rest of WP MCP: snapshot first, then store, with rollback-operation ready to put the previous content back.
Snapshot before every write
No tool that writes can skip it. The before-state is saved first, the change is applied second.
One-click undo
Restore a single change with rollback-operation or a whole agent run with rollback-session, from the agent or from wp-admin.
Validated before it is stored
Bricks content has to be well-formed and decode to a proper element list. Anything else is refused up front, so a broken payload never reaches the page.
Free or Pro
Part of WP MCP Pro.
The three builder tools (detect-builder, get-builder-content, update-builder-content) are part of WP MCP Pro. The free plugin still covers the rest of the site, including Gutenberg block editing, posts, pages, media, menus and the full snapshot and rollback engine, so you can try the safety model before you pay for builder editing.
WP MCP Pro starts at $49 a year for one site. See pricing for what each tier includes.
How to connect
Connect Bricks MCP in four steps.
- 01Install WP MCP
Upload the free wpmcp plugin and activate it. It needs WordPress 6.9 or newer and PHP 8.1 or newer, and it runs entirely on your own server.
- 02Check the requirement
Bricks Builder active on the site.
- 03Connect your client
Add the site to Claude Code, Claude Desktop, Cursor or any MCP client with a WordPress application password, or the WP-CLI stdio bridge locally. OAuth 2.1 with full or read-only access is there too, once the site owner switches it on.
- 04Ask for the change
Describe what you want done in Bricks. WP MCP snapshots the target, makes the change, and leaves a Restore button next to it in wp-admin.
Step-by-step guides: Claude,Claude Code andCursor. The docscover the safety model in full.
Frequently asked
Bricks MCP: questions, answered.
What is a Bricks Builder MCP server?
It is Bricks Builder content made available to AI agents over the Model Context Protocol. WP MCP adds three tools for it: detect the builder, read a page's Bricks content, and write updated content back with a snapshot.
Will pages edited through MCP still open in the Bricks editor?
Yes. WP MCP stores the content in the same post meta and the same shape Bricks uses, so the page opens in Bricks as usual.
Can I undo a Bricks edit?
Yes. The page is snapshotted before each write and rollback-operation restores the previous content. A whole agent session can be rolled back with rollback-session.
Is Bricks MCP included in the free plugin?
No, Bricks is part of WP MCP Pro. The free plugin covers Gutenberg and the rest of WordPress.
Which other builders does the same toolset cover?
The same three builder tools also work with Divi, WPBakery, Beaver Builder, Breakdance, Oxygen, Avada, Thrive Architect, Cornerstone and BeTheme. Elementor has its own deeper toolset.
Can the agent edit Bricks classes and variables?
Yes. With scope set to design_system, get-builder-content returns the global classes, variables and color palettes, and update-builder-content adds, updates or removes one of them. Each change is refused if that data changed since the read, and rollback-operation undoes it.
What if the agent produces invalid Bricks content?
It is refused before anything is stored. Content must be well-formed and decode to a proper element list, so a broken payload never reaches the page.
Does Bricks MCP work with Claude, Claude Code and Cursor?
Yes. Claude Code and Cursor connect to WP MCP over HTTP with a WordPress application password, and Claude Desktop uses the desktop bundle from the WP MCP Connection screen. Clients that can only sign in with OAuth, such as the claude.ai custom connector, need OAuth switched on first with one line in wp-config.php, because it ships off. Once connected, the Bricks tools are available in every client the same way.
Keep exploring
MCP for Bricks →
Read and write Bricks Builder content over MCP, a page builder most MCP tools can't touch.
Oxygen MCP →
An Oxygen MCP server gives an AI agent access to the element tree behind an Oxygen page.
Breakdance MCP →
A Breakdance MCP server gives an AI agent the JSON document behind a Breakdance page.
Divi MCP →
A Divi MCP server lets an AI agent open a Divi page the way the builder stores it and change it for you.
GenerateBlocks MCP →
A GenerateBlocks MCP server lets an AI agent build with GenerateBlocks and tune the GeneratePress theme around it.
Browse all integrations, comparefree and Pro, read the docs, or see how the WordPress MCP server works.