An agent can read and edit a block theme's templates, template parts, global styles and style variations, navigation menus, synced patterns and a custom-block library, and can apply a style variation or reset a template to its theme default.
View LolaCore for FSE on WordPress.org
Needs WordPress 7.0 or later with a block theme, the base LolaCore plugin active (2.7.0+), and this addon active. Most abilities need edit_theme_options; the synced-pattern and page-blocks abilities need edit_posts; the custom-block abilities (design, list, update, place) need manage_options.
All 21 ability ids are literal class constants, confirmed directly in the registrar, so none of them are dynamic. Neither the plugin's read-ability helper nor its write-ability helper sets meta.annotations.readonly or meta.annotations.destructive: the read helper sets no annotations at all, and the write helper's 'destructive' flag is written under meta.mcp, not under meta.annotations. Per the Bridge's fail-safe rule (no visible readonly annotation, and destructive not explicitly false in the annotations block) every one of the 21 abilities, including the plain get/list calls, counts as destructive rather than read or write.
Grouped by what each one can change. Every one starts off until you enable it.
Reports block-theme readiness, template counts and global styles state.
Lists the block templates of the active theme.
Reads one block template with a human-readable block summary.
Updates a block template's markup; WordPress keeps a revision for undo.
Removes a user customization so the theme's default template returns.
Lists template parts, optionally filtered by area.
Updates a template part such as the header or footer.
Reads the user global styles: palette, typography, spacing.
Merges partial settings or styles into the user global styles.
Lists the block style variations the active theme ships.
Applies a named theme style variation to the site by merging it into global styles.
Lists synced block patterns with where they are used.
Creates a synced wp_block pattern from block markup.
Updates a synced pattern's markup; the change propagates to every page using it.
Reads the parsed block tree of a page or post.
Lists block navigation menus (wp_navigation) with their link items.
Updates a navigation menu's markup.
Designs a custom block from a structured spec and saves it in the Block Builder library.
Lists custom blocks from the Block Builder library with usage and placement readiness.
Updates a custom block library entry from a structured spec.
Inserts an installed custom block into a template or template part.
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 FSE 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 FSE 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.
Conditionally. It registers 21 Full Site Editing abilities directly in the core Abilities API, but only once its own dependency check passes, so the Bridge only sees them on a site that also runs the base LolaCore plugin.
requires the base LolaCore plugin active, version 2.7.0 or newer (checked via a LOLACORE_VERSION constant and version_compare); the addon registers nothing and shows an admin notice instead if LolaCore is missing or outdated. requires WordPress 7.0 Full Site Editing primitives (get_block_templates() and wp_is_block_theme()) to exist.
Needs WordPress 7.0 or later with a block theme, the base LolaCore plugin active (2.7.0+), and this addon active. Most abilities need edit_theme_options; the synced-pattern and page-blocks abilities need edit_posts; the custom-block abilities (design, list, update, place) need manage_options.
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 FSE'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 FSE. 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.