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.
View ElementsKit Elementor Addons on WordPress.org
ElementsKit needs WordPress 6.9 or later and the plugin active. Widget, template and library abilities check edit_posts or edit_pages, mega menu abilities mostly check manage_options (one also requires edit_theme_options), and custom-widget abilities check manage_options.
None of the 15 registrations declare a readonly or destructive annotation in the evidence, so every ability, including the list operations, falls to the Bridge's fail-safe destructive classification rather than being marked as a safe read.
Grouped by what each one can change. Every one starts off until you enable it.
Lists the ElementsKit Elementor widgets available on the site.
Inserts an ElementsKit widget into an Elementor post.
Lists ElementsKit page and section templates.
Inserts an ElementsKit template into a post.
Creates a new page or post using ElementsKit.
Creates a new reusable ElementsKit template.
Creates a new header or footer template.
Lists widgets built with ElementsKit's custom Widget Builder.
Creates a new widget with the Widget Builder.
Lists the site's ElementsKit mega menus.
Turns on the mega menu builder for a specific WordPress menu.
Updates a single item inside a mega menu.
Creates a new mega menu.
Lists templates available in ElementsKit's remote template library.
Imports a template from the remote library into a post.
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. ElementsKit Elementor Addons 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 ElementsKit Elementor Addons 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 15 abilities register unconditionally with the core Abilities API when the plugin is active, in addition to the plugin's own MCP server, so the Bridge discovers them independently of that server.
Yes, unconditionally, once ElementsKit Elementor Addons is active. Nothing else has to be configured for the Bridge to discover them.
ElementsKit needs WordPress 6.9 or later and the plugin active. Widget, template and library abilities check edit_posts or edit_pages, mega menu abilities mostly check manage_options (one also requires edit_theme_options), and custom-widget abilities check 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 check or flip coming soon and maintenance mode, and list, read, and create or update SeedProd landing pages, mode pages, and theme templates.
Verified from ElementsKit Elementor Addons'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, Roxnor or ElementsKit Elementor Addons. 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.