A beta that opened on September 15 lets AI tools connect to a WordPress site and build pages as native, editable Elementor structures rather than returning raw code. Elementor, which runs on more than ten million WordPress sites, names Claude Code, Claude Desktop, Codex and Cursor, and leaves the list open to anything else that speaks the Model Context Protocol. Roi Tal, product marketing manager, frames the appeal around continuity with existing workflows, saying that a user keeps working the way they already do across other tools and that “Elementor becomes the place that context lands directly.”
What the feature connects to matters as much as the feature itself. WordPress has carried an Abilities API in core since version 6.9, a way for plugins to register discrete, machine-readable actions with defined permissions and input and output schemas. Elementor says the MCP exposes its website-building capabilities through those abilities, so a builder of its size shipping an official implementation on that layer is worth following. For hosting providers, the beta matters because it creates a new route through which an authorized external AI client can invoke supported actions inside a WordPress site.
Key facts
- What it does: lets MCP-compatible AI tools build and edit pages as Elementor structures, with the result saved as a draft rather than published.
- Where it works: on atomic pages and layouts, with the Atomic Editor activated.
- What needs Angie: three of the nine advertised capabilities require Angie, a separate Elementor plugin listed at more than 100,000 active installations.
- What it asks of a site: joining the beta means switching that site to Elementor’s beta release channel and updating to a pre-release build.
What the Connection Reaches
Six of the nine capabilities Elementor lists concern page structure. An AI tool can generate a full page with content and styling in one pass, rework an existing layout rather than only adding to it, create and apply classes and variables, adjust responsive breakpoints and hover states, build theme parts such as headers, footers, archives and popups with their display conditions, place or create components, and wire elements to post fields, custom fields and taxonomies.
The remaining three reach further, and all of them require Angie, Elementor’s separate agentic plugin. They cover creating custom widgets and admin experiences, managing content in bulk alongside debugging and maintenance, and using the site as an entry point to abilities registered elsewhere in WordPress. Elementor says that last category can include abilities for WooCommerce, Yoast, WPForms, Jetpack and Advanced Custom Fields. Angie has been on the WordPress plugin directory since September 2025 and is listed there at more than 100,000 active installations.
That last group is the widest in reach, since it takes an agent beyond the builder and into the rest of the install. It is also the group that depends on a second plugin being present.
Controls, Setup and Scope
The beta includes several controls. Output is saved as a draft and not published. If the editor and an AI tool touch the same page at once, the conflict is detected and flagged. Access is restricted to site administrators, and a connection is made per site rather than across an account. On cost, Elementor says basic sections and features can be generated free while Pro elements require a Pro plan, and that usage of the connected AI tool is billed separately under that provider’s pricing.
Getting in takes a few steps. Turning the beta on means going to the version control screen, enabling beta tester status, updating the site to Elementor’s latest beta build, and activating the Atomic Editor. Because the feature is enabled through a beta build of the main Elementor plugin, that version information may be relevant when a provider handles a related support request.
The Atomic Editor step also sets the current scope. The tools work on atomic pages and layouts, and Elementor does not list classic editor pages within the scope of the beta.
The Layer Underneath
The Abilities API arrived in WordPress 6.9 as a foundation for registering permission-checked actions with typed input and output schemas. It has kept moving since. In July, Jorge Costa proposed three broader read-only abilities for the 7.1 cycle, core/read-settings, core/read-content and core/read-users, with the stated aim of making WordPress more agent-readable.
WordPress 7.1 separately adds features relevant to site operators. Two new filters let plugins extend the validation of what an ability receives and returns. A new action fires at the start of every ability invocation, before validation and before the ability runs, and plugins can use it to record that a call was attempted, including calls that never proceed to execution. WordPress describes the action as suitable for auditing, telemetry, tracing and invocation accounting. It gives plugins a standard observation point as more integrations start using the API.
Third-party WordPress plugins and MCP servers already offer ways to connect AI tools to Elementor. This is the first such implementation released by Elementor itself.
What the Announcement Leaves Open
The announcement explains the initial connection step, including the creation of a WordPress application password that Elementor places in the setup prompt generated for the chosen AI client, with a manual route for anyone who prefers one. It does not detail what site data may be returned through the connection, or how individual agent calls are exposed for logging. Where that data is processed depends on the selected AI tool and its configuration.
For hosting companies those details may be relevant when documenting data flows, handling support requests and reviewing changes made through an AI client.
About the Data
The capabilities, the controls, the enablement route, the connection step, the pricing split and the quotation come from Elementor’s announcement of September 15. Installation counts, versions and listing dates for Elementor and Angie come from their WordPress plugin directory listings, read the same day. The installation figures are rounded thresholds rather than exact counts. The Abilities API facts come from WordPress core development notes: the July 31 note on 7.1 for the new filters and the invocation action, and the July 2 merge proposal for the three read abilities. Those abilities were proposed for WordPress 7.1 but are not listed as shipped in the July 31 note. Because we have not tested the beta, the description of how it works is based on Elementor’s announcement.
