WPBakery MCP · Pro
WPBakery MCP: AI editing for WPBakery Page Builder.
A WPBakery MCP server turns the vc_row shortcodes behind your pages into something an AI agent can read and edit safely. WP MCP does it from inside WordPress, for Claude, Cursor or any MCP client, with a snapshot before each write.
Self-hosted · snapshot before every write · one-click undo
› Move the testimonials row above the pricing row on /services
get-builder-content rows and elements with dotted paths
⛨ content, editor flag and CSS row saved
update-builder-content operation move, hash checked
✓ Row moved. The custom CSS row matches the new layout.
What it is
What a WPBakery Page Builder MCP server does.
WPBakery Page Builder saves a page as nested shortcodes in post_content, and keeps two post meta rows beside them: the backend editor flag and the compiled custom CSS that comes from each element's css attribute. An MCP server for WPBakery has to understand all three, or an edit leaves the page and its CSS out of step.
WP MCP reads the layout as a tree with a dotted path per element, so an agent can say 'the heading in the second row' and the write touches only that element. Sites that have run WPBakery for years tend to have hundreds of such pages, which is exactly where a careful, reversible bulk edit pays off.
WPBakery pages are shortcodes in post_content plus two meta rows, one for the editor flag and one for compiled custom CSS. That layout is why a find-and-replace across a WPBakery site is so error-prone: change the text and the compiled CSS row or the flag can fall out of step. WP MCP treats the three as one unit. An element edit rewrites only the addressed shortcode, keeps the flag and the CSS row consistent, and one snapshot holds all three.
Read and change
What WP MCP can read and change in WPBakery Page Builder.
It can read
- Which pages use WPBakery, including ones saved with the backend editor off
- A page's rows, columns and elements as a tree with a path per element
- The hash of the stored layout, used to guard the next write
It can change
- Update, add, remove or move one element by path
- Replace the whole shortcode layout in one write
- Keep the editor flag and the custom CSS row in step with the content
These are the real ability and operation names the agent calls. TheWPBakery Page Builder AI agent tool reference page lists the calls in detail.
Example prompts
Three things to ask first.
Find every WPBakery page that still mentions our old phone number and list them.
Change the heading in the second row of the homepage to 'Trusted by 400 local businesses'.
Remove the empty row at the bottom of /contact and tell me how to undo it.
Find every WPBakery page that still mentions our old phone number.
The agent reads each page's tree through get-builder-content and returns the pages and elements that contain it, with no writes.
Change the heading in the second row of the homepage to "Trusted by 400 local businesses".
update-builder-content addresses that element by path with the hash from the read, so a page edited meanwhile is refused.
Remove the empty row at the bottom of /contact and tell me how to undo it.
The row is removed after a snapshot of the layout, the editor flag and the CSS row. rollback-operation restores all three.
Safety
Every WPBakery Page Builder write has a way back.
The shortcodes are post_content and the two WPBakery rows are post meta, so one post snapshot captures the layout, the editor flag and the compiled custom CSS together. An element operation rewrites only the addressed element, and rollback-operation puts all three back exactly as they were.
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.
Content-hash guarded
A write to a WPBakery page that already has a layout needs the hash the read returned. A missing or stale hash is refused, so a page someone else just edited is never silently overwritten.
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 WPBakery 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
WPBakery pages on the site. Reads and writes work on the stored shortcodes and meta, so the plugin does not need to be loaded to edit, only for the pages to render.
- 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 WPBakery Page Builder. 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
WPBakery MCP: questions, answered.
What is WPBakery MCP?
It is a way to edit WPBakery Page Builder layouts from an AI agent over the Model Context Protocol. WP MCP exposes the layout as a tree and writes element-level changes back as valid WPBakery shortcodes.
Does it work with Visual Composer shortcodes like vc_row?
Yes. WP MCP detects WPBakery pages by the editor flag or by vc_row and vc_section shortcodes in the content, so pages saved with the backend editor off are found too.
Does WPBakery need to be active for the agent to edit?
No. Editing works directly on the stored shortcodes and meta, so nothing calls into the plugin. WPBakery does need to be active for the pages to render on the front end.
What happens to the custom CSS when an element changes?
WPBakery compiles each element's css attribute into a post meta row. WP MCP keeps that row in step with the content on every write, and the snapshot restores it on a rollback.
Is WPBakery MCP free?
WPBakery editing is part of WP MCP Pro. The free plugin covers Gutenberg and the rest of WordPress with the same snapshot and rollback engine.
Does it find WPBakery pages saved with the backend editor off?
Yes. Detection covers pages that use WPBakery even when they were saved with the backend editor switched off, so they are not missed in an audit.
Does WPBakery have to be active for edits?
No. Edits work on the stored shortcodes and meta. WPBakery only has to be active for the pages to render.
Does WPBakery 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 WPBakery Page Builder tools are available in every client the same way.
Keep exploring
MCP for WPBakery Page Builder →
Read and edit WPBakery layouts element by element over MCP, with its custom CSS kept in step, every write reversible.
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.
Avada MCP →
An Avada MCP server gives an AI agent a safe way into Avada's Fusion Builder layouts.
Beaver Builder MCP →
A Beaver Builder MCP server lets an AI agent work on the rows, columns and modules of a Beaver Builder page.
Thrive Architect MCP →
A Thrive Architect MCP server gives an AI agent the layout behind a Thrive page or landing page.
Browse all integrations, comparefree and Pro, read the docs, or see how the WordPress MCP server works.