Until now, our Elementor MCP add-on was mostly good at reading, checking, and carefully changing existing Elementor data.
Useful? Yes. Exciting? Not exactly fireworks.
Version 2.3.0 changes that. It gives AI a box of proper Elementor building bricks.
From looking at pages to building pages
Think of Elementor like a giant LEGO board for websites. A page is not just one blob of text. It is made from containers, headings, images, buttons, text blocks, and other pieces.
Before this update, AI could help inspect those pieces and change some of them. With this release, it can start putting new pieces on the board in a safer, more predictable way.
What changed in 2.3.0?
We added the first set of Elementor page-authoring abilities. These are small, reusable actions that let an AI assistant build and rearrange page structure without pretending to be a browser.
elementor/create-pagecreates a new Elementor-ready page or post.elementor/add-containeradds a container, either at the top level or inside another container.elementor/add-widgetadds any Elementor widget type with raw Elementor settings.elementor/add-heading,elementor/add-text-editor,elementor/add-image, andelementor/add-buttonadd common page pieces quickly.elementor/move-elementmoves a piece to a new position.elementor/remove-elementremoves a piece with guardrails.elementor/duplicate-elementcopies a whole element tree with fresh IDs.elementor/reorder-elementschanges the order of children under a parent.
Why this matters
There is a big difference between “AI, please tell me what is on this page” and “AI, please create a draft landing page with a hero section, a few text blocks, an image, and a button.”
The second one needs building tools. Not magic. Not guessing. Tools.
That is what this release starts to provide. It does not try to copy a full MCP server into the plugin. It keeps the existing abilities-only design and adds the first useful authoring primitives inside the normal elementor/* namespace.
A small example
With these abilities, an AI assistant can now follow a sequence like this:
- Create a draft Elementor page.
- Add a container.
- Add a heading.
- Add a paragraph.
- Add an image.
- Add a button.
- Move the button above or below another element.
- Duplicate a section if the page needs another similar block.
That is boring if you read it like a changelog. It is much less boring when you realize it is the start of AI building actual Elementor drafts with real page parts.
What we did not add yet
This is not the “everything and the kitchen sink” release. We started with the basics because basics are what everything else sits on.
Possible next steps include higher-level page-building flows, template apply/save helpers, dynamic tags, stock image helpers, SVG or icon helpers, and prompt or blueprint support. But those should be built on top of solid primitives, not duct tape.
Already tested and rolled out
The release passed the WordPress Plugin Check gate with no errors. We also smoke-tested the new authoring flow on an Elementor site by creating a draft page, adding elements, duplicating, reordering, moving, and removing them, then deleting the test page afterwards.
After release, we deployed it to the sites we manage that are actively running Elementor.
So, short version: MCP Abilities – Elementor can now do more than inspect the LEGO pile. It can start building with it.