An agent can build and edit whole pages and posts element by element, manage global design tokens such as colors, fonts, and spacing, search stock photos, and manage theme builder templates, navigation menus, and media uploads.
View Pagelayer on WordPress.org
Needs WordPress 6.9 or newer with the Abilities API and Pagelayer active. Most abilities check edit_posts, page and post lifecycle actions check edit_pages, publish_pages, delete_pages, publish_posts or delete_posts, template abilities check edit_theme_options, menu and site-creation abilities check manage_options, and media upload checks upload_files, so a connected user needs the matching WordPress capability for each group.
All 59 abilities are registered through one shared helper with literal string keys in per-category arrays (widgets, global, templates, menus, pages, posts, media); none of the ids or their permission callbacks are runtime-computed. None of the wp_register_ability() calls pass a readonly or destructive annotation, so every ability falls to the risk floor. These ability names are put together by the plugin's code when it registers them, so we worked them out from that code. Check the exact names on your site's Bridge screen.
Grouped by what each one can change. Every one starts off until you enable it.
Lists a compact summary of every registered Pagelayer widget with its tag, name, group, and nesting rules.
Returns metadata and setting-section names for one widget type.
Returns the editable attribute schema for one widget.
Returns the style properties shared by every widget, row, and column.
Returns canonical example configurations for one or more widgets.
Returns the same compact widget list as List Pagelayer Widgets.
Lists prebuilt PopularFX and Pagelayer section templates.
Imports a prebuilt library section directly into a page or post.
Fetches a URL and extracts its title, headings, paragraphs, and image URLs for reference.
Returns compact schemas for up to 12 named widgets in one call.
Retrieves Pagelayer theme options, active layout settings, and header/footer assignments.
Retrieves the site's design tokens: global colors, fonts, content width, and style presets.
Updates the site's global colors, fonts, and content width.
Lists available FontAwesome and Pagelayer icons with category filtering and search.
Lists Google Fonts, system fonts, and Pagelayer custom fonts available for layouts.
Retrieves curated color palette presets as a starting point for a layout.
Retrieves standardized spacing scale presets for containers, padding, and gaps.
Searches Pexels for licensed stock photos and returns direct URLs, requiring a Pexels API key configured in settings.
Lists saved Pagelayer theme builder templates.
Creates a new theme builder template such as a header, footer, or archive layout.
Updates a saved template's layout or display conditions.
Deletes a saved theme builder template.
Saves an element from an existing page as a reusable template section.
Inserts a saved template section into a page or post.
Lists the site's WordPress navigation menus and their items.
Creates a navigation menu or replaces an existing one's items.
Deletes a WordPress navigation menu.
Generates a full multi-page website with pages and optional theme templates from a brief.
Creates a new page with a Pagelayer layout.
Updates a page's title, status, or entire layout tree.
Returns a page's content and layout data.
Lists the site's pages.
Publishes a draft page.
Duplicates an existing page with new element IDs.
Trashes or deletes a page by ID.
Returns a preview link for a page.
Checks a page's layout data for structural or content-quality issues.
Generates new layout sections for a page from a brief.
Edits a page's layout tree directly.
Changes style properties on one or more elements in a page.
Returns documentation of the pagelayer_data JSON structure.
Finds elements in a page's layout matching given criteria.
Returns an outline of a page's element tree for navigation.
Updates one element's content or properties in a page.
Adds a new element to a page.
Deletes an element from a page.
Moves an element within a page's layout.
Duplicates an element within a page.
Starts a batched edit transaction on a page.
Commits a batched edit transaction to a page.
Discards a batched edit transaction without saving it.
Creates a blog post with categories, tags, excerpt, featured image, and a Pagelayer layout.
Updates an existing blog post's title, layout, categories, tags, excerpt, or status.
Retrieves a blog post's details and layout data.
Lists the site's blog posts built with Pagelayer.
Publishes a draft blog post.
Clones an existing blog post with new element IDs.
Trashes or deletes a blog post by ID.
Sideloads an image from a URL into the media library.
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. Pagelayer 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 Pagelayer 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. Pagelayer registers 59 abilities covering widgets, global styles, templates, menus, pages, posts, and media through a real wp_register_ability() call, so the Bridge discovers and can wrap any of them once switched on.
Yes, unconditionally, once Pagelayer is active. Nothing else has to be configured for the Bridge to discover them.
Needs WordPress 6.9 or newer with the Abilities API and Pagelayer active. Most abilities check edit_posts, page and post lifecycle actions check edit_pages, publish_pages, delete_pages, publish_posts or delete_posts, template abilities check edit_theme_options, menu and site-creation abilities check manage_options, and media upload checks upload_files, so a connected user needs the matching WordPress capability for each group.
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 Pagelayer'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, Softaculous or Pagelayer. 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.