Elementor MCP Goes Live: Agents Edit Real Pages, V4 Only
Elementor's MCP connector is live for Claude, Cursor, Codex and ChatGPT. It builds real, editable pages, but only on Atomic V4 — and with admin rights.

Elementor's official MCP connector is live: Claude, Cursor, Codex or ChatGPT can now build and edit real, editable Elementor pages from a typed sentence. One limit decides whether that matters to you this week — it supports Atomic (V4) elements and layouts only.
What shipped, and when
Elementor announced the MCP on September 15, 2026 and shipped it in Elementor 4.3 a week later, on September 22. This week's "officially live" framing comes from WP Weekly 309, as relayed by the ConvertElementor write-up, which reads it as Elementor now treating the connector as a finished, supported way to build rather than a developer preview.
What the agent returns is a genuine Elementor page you reopen in the editor and keep editing — not pasted HTML parked inside a widget. Describe a landing page with a hero, feature boxes, logos and a call to action, and it builds that structure in your site's colors and fonts, saved as a draft.
The limit that decides whether you can use it today
Classic widgets — the V3 editor Elementor users have built with for years — are outside the connector for now, and Elementor says support for them is coming. Sites already on the Atomic editor, which arrived with Elementor 4.0 in April 2026, are ready today. Everyone else is looking at a rebuild first, and that is a project, not a toggle.
The rest of the requirements are short: Elementor 4.3 or newer, an administrator account, and a compatible client. Elementor lists Claude Desktop, Claude Code, Cursor and Codex as the tools it works best with. Connecting is free; Pro elements still need a Pro plan, and your AI tool's subscription is separate.
The permission question to settle first
Setup runs through the WordPress dashboard — Elementor, then Elementor MCP — where you pick a client and copy a generated setup prompt that creates an application password behind the scenes. That is the part worth slowing down on: the connector uses your WordPress user's permissions, so an administrator connection can do administrator things.
One guardrail is built in: every generation is saved as a draft, so a bad instruction cannot publish a broken page on its own. The rest is on you, and the framing from Control Plane's 2026 DevOps MCP guide (which Control Plane itself publishes) transfers cleanly — pick servers by what they are allowed to change and how they authenticate, because a server that can deploy is production access. Its tiering is the right shape here: start read-only, expand to non-production writes, and require confirmation for destructive actions. In practice that means a staging copy before a live client site.
The ecosystem filling the V3 gap
WordPress made this practical with the Abilities API in WordPress 6.9, and the official WordPress MCP Adapter plugin reports more than 50,000 active installs. Three third-party options already cover ground the official connector does not:
| Project | What it adds | Version |
|---|---|---|
| Respira | Independent MCP server covering classic widget pages and Atomic elements alike; every edit lands on a copy, with 90 days of undo | — |
| Atomic Addons | Free plugin registering 31 abilities through the WordPress Abilities API, served from its own MCP endpoint | 1.9.0 |
| UiCore PRO | Added its own MCP integration this month | 2.5.0 |
And the page-builder market moved at once: Breakdance 3.0 and Oxygen 6.2 shipped agent control within about 90 minutes of each other last month, and Divi has its own AI agent for Divi 5.
Is it worth connecting this week?
On Atomic V4, yes — connect a staging copy, give it one real page brief with the audience, goal, sections and tone named, and review the draft the way you would review a colleague's first pass: copy, links, mobile layout, forms.
On classic widgets, the question isn't about MCP at all. It's whether a V4 rebuild is worth scheduling now, or worth waiting out until Elementor ships classic-widget support — the one announcement to watch next.
More from DangMua