Integrations / WPBakery Page Builder

Governed integration

WPBakery MCP abilities

WPBakery MCP for AI agents: 12 governed abilities that read and edit WPBakery Page Builder pages. They appear on your WordPress MCP server only while WPBakery Page Builder is active, and stay off until you enable them. Read and edit WPBakery pages element by element, insert saved and Templatera templates, and change page code and WPBakery settings.

12 governed abilities Requires WPBakery Page BuilderGuarded write

Governed exactly like core

These abilities are off until you enable them, capability-checked before every call, and written to the same audit log as everything else. There is no separate trust model for integrations.

  • Active only while WPBakery Page Builder is installed and active
  • Off by default, enabled one ability at a time
  • Capability-gated on every call, discovery and execution separately
  • Logged like core, denials included, keys and identifiers, never free-text

How the WPBakery Page Builder tools work

WPBakery Page Builder stores a page as shortcodes in the post content. These tools read them and change them one element at a time through WPBakery’s own element map, add-ons included, so an agent can edit a row or drop in a saved template without rebuilding the page.

What an agent can do

  • Read a page’s raw content, unchanged, with an outline of every element: its attributes as stored and decoded the way WPBakery reads them, its inner text and a fingerprint.
  • Change one element’s settings or text, insert new elements with their children, move an element, or remove one, on pages and Grid Builder templates.
  • List the templates in WPBakery’s own library and copy one into a page.
  • Replace literal text between elements while every shortcode and attribute stays the same.
  • Set a page’s custom CSS, header JS and footer JS.
  • For a user who can manage options: read and change a fixed list of WPBakery’s site-wide settings.

Who can do what

  • Element and page tools need edit access to that post. The two settings tools need the manage_options capability.
  • Raw HTML, raw JS, maps, custom onclick settings, Design Options and page code need a user who may post unfiltered HTML. The page header and footer JS fields are also refused when WPBakery’s Role Manager would not save custom JS for that user.
  • Otherwise WPBakery’s Role Manager is not applied, apart from the editor setting that decides whether an empty post can be started. WPBakery’s own save filter still runs.

The way back

  • Element and template edits return restore_revision_id when WordPress keeps a revision, and Restore revision brings the page back to it. Restore revision works on WPBakery pages while WPBakery is active, and rebuilds the page’s generated CSS afterwards.
  • Removing an element is refused when the post keeps no revisions (a Grid Builder template keeps none) or the site keeps only one.
  • Page code and settings changes return previous, the earlier values, which you send back to undo the change.
  • None of these tools is in the Changes tab. Replace text is not undoable here either; WordPress keeps a revision when revisions are on.

What it refuses

  • Text WPBakery keeps in an element’s settings, such as a heading or a button label, through Replace text. Update element changes those.
  • A stale index or fingerprint, a page that changed since the last read, or a save that would change other content for this user. Nothing is saved.
  • Adding an element to a flexbox or grid container item, or moving one into it: WPBakery 9.1 ships those containers without registering them. Elements already inside can be edited, reordered or removed.
  • CSS that holds markup or a “<” followed by another character, where WPBakery cuts the CSS off, and JS containing a closing script tag.
  • The license code and every setting outside the fixed list are never returned, and the Gutenberg switch, auto save and Design Options use are not writable.

Templatera templates

  • While the Templatera add-on is active, the template list shows Templatera’s published templates that the user can edit and whose own role list allows the user.
  • Insert template copies one into the page, or places it by reference so the page shows the template’s current content. A reference gets the same access and content checks as a copy, and a reference loop is refused.
  • Templatera template posts are treated as WPBakery content, and the WPBakery card on the Integrations tab says whether Templatera is active.

Versions

  • The tools appear while WPBakery Page Builder is active. 9.1 is the tested version and no minimum is set.
  • Visual Composer Website Builder is a different product and gets no tools.

How to connect an AI agent to WPBakery Page Builder

Activate WPBakery Page Builder, then open the Agent Abilities for MCP screen and enable the WPBakery Page Builder abilities you want. Connect your AI client, such as Claude or ChatGPT, to the endpoint on the Connection tab, and it can call those abilities as the WordPress user you connected. The address below is illustrative; your real one shows there. Each client has its own setup guide.

Illustrative endpoint (your real one shows on the Connection tab)https://your-site.com/wp-json/…/mcp

The 12 WPBakery Page Builder abilities

Each one is off until you enable it and capability-checked on every call. Open any card to see how it is governed.

Get WPBakery page content

Read only

Reads the raw post content of a WPBakery page, unchanged. Shortcodes come back exactly as stored, never rendered or stripped, and attribute values keep the form WPBakery stores them in, including its escaped brackets and quotes and base64 encoded values such as raw HTML, so search for text as it is stored. Also returns is_wpbakery_owned, true when WPBakery owns the page or the post is a Grid Builder template. With include_structure it also returns an outline of the shortcode elements (tag, nesting depth, attributes as stored and decoded the way WPBakery reads them, the inner text of an element with no child element, decoded for raw HTML and raw JS, and a fingerprint per element) plus a page fingerprint, to find the text block that holds the text before calling wpbakery-replace-text. The outline stops at 2,000 elements. With include_page_settings it also returns the page custom CSS and the editor status, and the page custom JS only to users who may post unfiltered HTML. Requires edit access to the post; WPBakery's Role Manager settings are not applied. Only while WPBakery Page Builder is active.

View ability

Replace text in a WPBakery page

Guarded write

Replaces literal text within a WPBakery page while requiring the shortcode structure and every attribute value to stay the same before and after (quoting style and whitespace inside a tag are not part of this guarantee). Text that WPBakery keeps in an element's settings, such as a heading or a button label, cannot be changed here and is refused, as is any replacement that would add, remove or alter an element. Only a user who may post unfiltered HTML can put square brackets, percent-encoded brackets or data-* attributes in body text, and even then text that would add an element is refused. If saving the page as this user would remove or change elements, or change other content on the page, the call is refused and nothing is saved. Not undoable from this plugin's change history; WordPress keeps a revision when revisions are on. Requires edit access to the post; WPBakery's Role Manager settings are not applied. Only while WPBakery Page Builder is active.

View ability

List WPBakery elements

Read only

Lists the elements WPBakery Page Builder has on this site, add-ons included, from WPBakery's own element map: tag, name, category, whether it holds other elements, the elements it allows inside it and the ones it may sit in, and whether it is deprecated. With tag it returns one element with its settings: name, kind, label, default, the allowed values of a choice (at most 100), whether wpbakery-update-element can write it, and needs, which is unfiltered_html for Design Options and for settings that can carry script or raw HTML. With context grid it lists the Grid Builder's elements too. An element an add-on maps only inside wp-admin is not listed. Requires the edit_posts capability; WPBakery's Role Manager settings are not applied. Only while WPBakery Page Builder is active.

View ability

Update a WPBakery element

Guarded write

Changes the settings or the inner text of one element on a WPBakery page or Grid Builder template, named by its index and by the tag and fingerprint wpbakery-get-page-content returned with include_structure. set_atts sets settings, each value in the form wpbakery-list-elements gives as its kind (a link as url, title, target and rel; an image as an attachment id; Design Options as fields such as margin_top, never as CSS); remove_atts returns settings to their default; text replaces the inner content of an element that has a content setting and no child elements. Only a user who may post unfiltered HTML can put square brackets, percent-encoded brackets or data-* attributes in body text, and even then text that would add an element is refused. Only the element's opening tag and, for text, its inner content change; every other byte of the page stays as it was. Refused: a stale index or fingerprint, a setting the element does not have or that cannot be written, a value its kind does not accept, already encoded values, and any change that would add or remove an element. Design Options and settings that can carry script or raw HTML need a user who may post unfiltered HTML. A save that would change other content for this user is refused, and nothing is saved. When a revision is kept, restore_revision_id brings the page back through restore-revision; the response also returns the element's new fingerprint and the page fingerprint. The outline stops at 2,000 elements. Not undoable from this plugin's change history. Requires edit access to the post; WPBakery's Role Manager settings are not applied, though its own save filter still runs. Only while WPBakery Page Builder is active.

View ability

Insert a WPBakery element

Guarded write

Adds an element with its children to a WPBakery page or Grid Builder template, before or after an element from the outline of wpbakery-get-page-content or as its first or last child; element takes tag, atts in the input form of each kind from wpbakery-list-elements, text and children. WPBakery's own nesting rules apply: the top level takes rows and sections, a row takes columns, a column takes content elements or an inner row. At most 50 elements, nested at most 6 deep. On an empty post with no builder, leave out the anchor to start the page; this one check follows WPBakery's own setting for which post types its editor is on for. Raw HTML, raw JS, maps, custom onclick settings and Design Options need a user who may post unfiltered HTML, and only such a user can put square brackets, percent-encoded brackets or data-* attributes in body text. Requires page_fingerprint from the last read or write and returns the new one; a changed page is refused and nothing is saved. Other indexes may move, so read the outline again before the next structural change. When a revision is kept, restore_revision_id brings the page back through restore-revision. The page's generated CSS is rebuilt. Not undoable from this plugin's change history. Requires edit access to the post; WPBakery's Role Manager settings are not applied, though its own save filter still runs. Only while WPBakery Page Builder is active.

View ability

Move a WPBakery element

Guarded write

Moves one element, with everything inside it, on a WPBakery page or Grid Builder template to a new place named against another element from the outline of wpbakery-get-page-content: before or after it, or as its first or last child. The element's stored text moves byte for byte; nothing in it is rewritten. WPBakery's own nesting rules apply to the new place, and a move into the element's own children or one that leaves a row with no column is refused. Requires page_fingerprint from the last read or write and returns the new one; a changed page is refused and nothing is saved. A move to the place the element already has saves nothing and returns moved false. Other indexes may move, so read the outline again before the next structural change. When a revision is kept, restore_revision_id brings the page back through restore-revision. The page's generated CSS is rebuilt. Not undoable from this plugin's change history. Requires edit access to the post; WPBakery's Role Manager settings are not applied, though its own save filter still runs. Only while WPBakery Page Builder is active.

View ability

Remove a WPBakery element

Guarded write

Removes one element, with everything inside it, from a WPBakery page or Grid Builder template, named by its index and by the tag and fingerprint from the outline of wpbakery-get-page-content. The fingerprint covers the whole element, so one that gained content since the read is refused. Refused when the post keeps no revisions (a Grid Builder template keeps none) or the site keeps only one, for the page's last row or section, and when a row would be left with no column. Requires page_fingerprint from the last read or write and returns the new one; a changed page is refused and nothing is saved. Other indexes may move, so read the outline again before the next structural change. restore_revision_id brings the page back through restore-revision. The page's generated CSS is rebuilt. Not undoable from this plugin's change history. Requires edit access to the post; WPBakery's Role Manager settings are not applied, though its own save filter still runs. Only while WPBakery Page Builder is active.

View ability

List WPBakery templates

Read only

Lists the templates saved in WPBakery Page Builder's own template library on this site: id, source (saved) and name, plus total. With include_content each template's stored shortcode text comes back byte for byte; for a user who may not post unfiltered HTML, a template holding raw HTML, raw JS, a map, a custom onclick setting or Design Options comes back without its content and with content_withheld true. While the Templatera add-on is active, WPBakery's editor shows Templatera's own templates instead, and so does this list: its published template posts (source templatera, id the post id) that the user can edit and whose own role list allows the user's first role, and with for_post_id only those whose own post type list allows that post; templatera_active says which list this is. Requires the edit_posts capability; WPBakery's Role Manager settings are not applied. Only while WPBakery Page Builder is active.

View ability

Insert a WPBakery template

Guarded write

Copies a template, named by its id and source from wpbakery-list-templates (saved, from WPBakery's own library, or templatera, a published Templatera template post the user can edit and may use on this post by the template's own role and post type lists, only while Templatera is active), into a WPBakery page or Grid Builder template, before or after an element from the outline of wpbakery-get-page-content or as its first or last child; on an empty post with no builder, leave out the anchor to start the page, where this one check follows WPBakery's own setting for which post types its editor is on for. The template's stored text is copied byte for byte; with mode reference (Templatera only) one Templatera element is placed instead, which shows the template's current content and gets the same unfiltered HTML checks on that content as a copy. A Templatera template it shows by reference, at any depth, gets the same access check and content checks; a reference loop is refused. WPBakery's own nesting rules apply to its top level, and a template may hold at most 50 elements, nested at most 6 deep. A template holding raw HTML, raw JS, a map, a custom onclick setting or Design Options needs a user who may post unfiltered HTML, and for any other user its text may hold no square bracket, percent-encoded bracket, data-* attribute, unfinished tag or HTML that WordPress would remove. Requires page_fingerprint from the last read or write and returns the new one; a changed page is refused and nothing is saved. Other indexes may move, so read the outline again before the next structural change. When a revision is kept, restore_revision_id brings the page back through restore-revision. The page's generated CSS is rebuilt. Not undoable from this plugin's change history. Requires edit access to the post; WPBakery's Role Manager settings are not applied, though its own save filter still runs. Only while WPBakery Page Builder is active.

View ability

Update WPBakery page code

Guarded write

Sets the custom CSS, header JS and footer JS of one WPBakery page, the fields of the page settings in WPBakery's editor; give at least one of custom_css, custom_js_header and custom_js_footer. Each field given replaces the page's existing code for that field, and an empty string removes it; previous returns the old value of every field that changed, which is the way back. CSS that holds markup is refused, as WordPress refuses it in custom CSS, and so is a "<" followed by another character, such as a <= range query, where WPBakery cuts the CSS off when it prints it; any other CSS is stored exactly as sent. JS containing a closing script tag is refused, and the JS fields are refused when WPBakery's own Role Manager would not save custom JS for this user. A field equal to what is stored is left alone and not listed in changed. No revision is kept, and the change is not undoable from this plugin's change history. Requires edit access to the post and a user who may post unfiltered HTML. Only while WPBakery Page Builder is active.

View ability

Get WPBakery settings

Read only

Reads a fixed list of WPBakery Page Builder's site-wide settings from its settings screen: responsive elements, Google Fonts subsets, local Google Fonts, keyboard shortcuts, CSS and JS loading, the Gutenberg switch, auto save, Design Options use, and the global custom CSS; the global header and footer JS only for a user who may post unfiltered HTML. Values come back as stored, and listed settings with no stored value are in not_set. Also returns the post types WPBakery's editor is on for and WPBakery's version. The license code and every other setting are never returned. Requires a user who can manage site options (manage_options). Only while WPBakery Page Builder is active.

View ability

Update WPBakery settings

Guarded write

Overwrites site-wide WPBakery Page Builder settings from wpbakery-get-settings: not_responsive_css, local_google_fonts and shortcuts (true or false), google_fonts_subsets (a list), css_loading and js_loading (hybrid, optimized or legacy), and the global custom_css, custom_js_header and custom_js_footer, which also need a user who may post unfiltered HTML. Each value goes through WPBakery's own sanitize callback for that field, and a value it would change is refused. The global custom_css is the exception: it is refused when it holds markup or a "<" followed by another character, where WPBakery cuts custom.css off, and otherwise stored exactly as sent. WPBakery points each url(../ in the global CSS at its own assets folder in the custom.css file it builds; the setting itself keeps the CSS as sent. A setting whose callback cannot be found, and the Gutenberg switch, auto save and Design Options use, are not writable. The change applies to the whole site at once; previous returns the old value of every setting that changed, null where none was stored, which is the way back. A value equal to what is stored is left alone. Writing custom_css rebuilds WPBakery's custom.css file, and the call reports an error when the file does not match afterwards. Not undoable from this plugin's change history. Requires a user who can manage site options (manage_options). Only while WPBakery Page Builder is active.

View ability

Try it with a prompt

Example requests you could paste to your agent once WPBakery Page Builder abilities are on.

  1. Show me the element outline of page 57 so I can see how the WPBakery layout is built.
  2. Change the heading in the first row of page 57 to Spring opening hours.
  3. Insert our saved Contact strip template at the bottom of page 57.
  4. Move the image gallery row on page 57 above the text block that follows it.
  5. Read the WPBakery settings and tell me how CSS and JS are loaded.

These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.

Back to all integrations

Add WPBakery Page Builder, keep the same control.

Every integration ability is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.

Active only while its host plugin is on, and gated like core.