An agent can inspect a page's drag-and-drop widget layout and write a new one back, covering both the classic meta-stored layout and the newer Layout Block storage.
View Page Builder by SiteOrigin on WordPress.org
Needs Page Builder by SiteOrigin active and WordPress 6.9 or later. Both abilities check edit_post against the specific post being read or written, so a connected user needs edit rights on that post.
Grouped by what each one can change. Every one starts off until you enable it.
Reads a post's Page Builder layout, from classic meta storage, block storage, or both, reporting which storage supplied the data.
Writes a post's classic or block-stored Page Builder layout after re-sanitizing it through the plugin's own widget sanitizer.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Page Builder by SiteOrigin registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from Page Builder by SiteOrigin starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Yes. Both abilities register unconditionally, gated only by the standard edit_post capability on the target post, with no separate feature toggle found in the code.
Yes, unconditionally, once Page Builder by SiteOrigin is active. Nothing else has to be configured for the Bridge to discover them.
Needs Page Builder by SiteOrigin active and WordPress 6.9 or later. Both abilities check edit_post against the specific post being read or written, so a connected user needs edit rights on that post.
An agent can read and edit the structure of Elementor-built pages, list and inspect widget and component schemas, manage the site's shared global CSS classes and design-token variables, build whole page layouts from a composition description, and publish or preview documents.
Once enabled, an agent can read and manage HFE header/footer/block templates and Elementor pages end to end: list, create, update, duplicate, delete and restore templates and pages, build and edit Elementor layouts widget by widget, toggle widgets and extensions, set display rules and theme compatibility, read the site's design tokens, and clear the Elementor CSS cache.
An agent can list and insert ElementsKit's widgets and templates into Elementor pages, scaffold new pages, headers, footers and custom widgets, and manage mega menus, all with an unauthenticated caller in mind since the code carries no readonly or destructive annotations.
Verified from Page Builder by SiteOrigin's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, Greg - SiteOrigin or Page Builder by SiteOrigin. Back to the full directory.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.