An agent with manage_options can inspect a Bricks site's global classes, variables, theme styles, components and templates, and create, edit, move, style or delete elements, sections, templates and components, most operations previewable with dry_run first; a small number of operations (merging or deleting a global class, deleting a global variable, deleting an element) are marked destructive.
View LolaCore for Bricks on WordPress.org
Needs the lolacore base plugin and WordPress 7.0 or later; WooCommerce active adds four more abilities. Every ability, read or write, checks the same manage_options capability through the plugin's own permission callback, so there is no separate read-only role.
69 lolacore-bricks/* ability id strings were found in the code (65 without WooCommerce), matching the readme's own stated count; risk for each is read directly from its ability map's readonly/destructive/idempotent flags, not guessed from its name.
Grouped by what each one can change. Every one starts off until you enable it.
Reports Bricks version, CSS mode, design-system counts and index coverage.
Lists Bricks global classes with categories and lock state.
Shows where a global class is used, grouped by page.
Lists Bricks global variables and the color palette.
Shows references to a global variable.
Lists Bricks theme styles with their conditions.
Lists Bricks components with instance counts.
Lists instances of one Bricks component.
Lists Bricks templates with type and conditions.
Resolves which Bricks template wins for a page.
Describes the control contract for a Bricks element type.
Returns Bricks domain SOP and architect guidance.
Finds global classes with no indexed usage.
Finds groups of equivalent global classes by normalized settings.
Finds global variables with no indexed references.
Finds components with zero indexed instances.
Finds theme styles whose conditions overlap on the same pages.
Summarizes the Bricks element tree for a page area.
Lists Bricks dynamic data tags grouped by provider.
Shows which Bricks shop templates exist and which WooCommerce elements are in use.
Lists Bricks WooCommerce elements grouped by shop function.
Advances the persisted Bricks design index in batches until finished.
Creates a Bricks global class with category and initial settings.
Updates Bricks global class settings across breakpoints and states.
Renames a Bricks global class and regenerates CSS where it is used.
Moves Bricks global classes to the native trash.
Restores a Bricks global class from the native trash.
Creates or updates Bricks global variables in one batch.
Creates or updates Bricks color palettes and their swatches.
Creates or updates a Bricks theme style, including settings and conditions.
Saves the Bricks naming convention and variable policy.
Inserts a Bricks element into a page area.
Moves a Bricks element to another parent or position.
Duplicates a Bricks element branch with new ids.
Applies universal Bricks style controls to one element.
Applies Bricks global classes to one or more elements.
Removes Bricks global classes from one or more elements.
Updates element-specific Bricks settings.
Updates text, image or link on one or more existing elements.
Inserts a Bricks section with optional content and site classes.
Inserts a Bricks container with optional content and site classes.
Inserts a Bricks div with optional content and site classes.
Inserts a Bricks heading with its text and site classes.
Inserts a Bricks text element with its copy and site classes.
Inserts a Bricks image from the media library.
Inserts a Bricks button with its label, link and site classes.
Creates a Bricks header, footer or content template.
Writes the element tree of one template area.
Sets where a template applies.
Duplicates a Bricks template with new element ids.
Moves a Bricks template to the WordPress trash.
Converts a Bricks element branch into a component and leaves an instance.
Defines component properties and types.
Edits a component's structure or style.
Inserts a component instance with property values.
Changes property values on one component instance.
Turns a component instance into regular elements on that page.
Edits Bricks page settings such as SEO, layout and page CSS.
Sets when a Bricks element is shown.
Sets Bricks element interactions.
Assigns a discovered dynamic data tag to an element setting.
Copies a Bricks branch onto several pages with new ids.
Updates text, images or links on matching elements across pages.
Adds or removes global classes on matching elements across pages.
Creates a Bricks shop template for product, archive, cart, checkout or account.
Inserts a WooCommerce product element such as title, price or gallery.
Replaces one global class with another everywhere and trashes the source.
Removes a Bricks global variable.
Removes a Bricks element branch from a page.
No abilities match that search.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. LolaCore for Bricks 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 LolaCore for Bricks 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. All 65 lolacore-bricks/* abilities (69 with WooCommerce active) register unconditionally through their per-domain registrar classes, and each one's readonly/destructive flags come straight from a data-driven ability map rather than being guessed from its name.
the required lolacore base plugin must be installed and active. the four get-woo-bricks-surface/create-woo-template/add-product-element/get-product-elements-catalog abilities only register when WooCommerce is active.
Needs the lolacore base plugin and WordPress 7.0 or later; WooCommerce active adds four more abilities. Every ability, read or write, checks the same manage_options capability through the plugin's own permission callback, so there is no separate read-only role.
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 LolaCore for Bricks'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, Fran Barbero or LolaCore for Bricks. 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.