The Day the Editor Started Listening
I have built more Elementor pages than I can count, and the work has always looked the same: open the editor, drag a section in, set the padding, pick the heading size, nudge the button three pixels to the left, repeat. I like the craft of it, but the dragging was never the valuable part. The valuable part is knowing what the page should say and whether the result is actually good.
That is why I paid close attention when Elementor announced its official MCP connector on September 15, 2026, and shipped it in Elementor 4.3 a week later. And this week, WP Weekly 309 put it plainly: Elementor MCP is officially live. Connect the AI tool you already use — Claude, Codex, Cursor or ChatGPT — describe the page you want in plain language, and the assistant builds real, editable Elementor structure. Not pasted HTML in a widget. A genuine Elementor page you open in the editor and keep editing like any other.
What MCP Is, in One Paragraph
MCP stands for Model Context Protocol, an open standard that lets AI assistants use tools offered by other software. Your website runs an MCP server that describes what it can do; an MCP client — Claude Code, Claude Desktop, Cursor, Codex, VS Code and others — discovers those tools and calls them when your request needs them. WordPress made this practical with the Abilities API, which arrived in WordPress 6.9, and the official WordPress MCP Adapter plugin already reports more than 50,000 active installs.
The Timeline: Announced in September, Live Now
The dates matter here, because this did not arrive overnight. Elementor announced the MCP on September 15, 2026, and shipped it in Elementor 4.3 on September 22. That was the first launch: the connector existed, it worked, and the people who tried it first were mostly developers building on the new Atomic editor. The "officially live" moment this week is the point where Elementor is treating it as a finished, supported way to build — the same week WP Weekly also flagged Novamira HQ desktop apps and WPPilot's self-hosted WordPress MCP plugin. The whole WordPress ecosystem is wiring itself up to agents at once.
It also completes a picture Elementor started with version 4.4, which I covered here recently: that release made your website agent-ready, with llms.txt support and WebMCP, so outside agents could read and understand your site. MCP is the other half. First the agent could read your site; now it can edit it.
What the Agent Can Actually Do
Here is what happens once the connection is live. You describe what you want in plain English — "Build a draft landing page for our consulting service with a hero, three feature boxes, client logos and a call to action, using our site colors" — and the assistant builds it with real Elementor elements, in your site's colors and fonts, and saves it as a draft. You open it in the same Elementor editor, look it over, tweak anything by hand, and publish when it is right.
The everyday edits are where it earns its keep: "Make the phone number in our header bigger on phones." "Add a section about our new service under the reviews." One agency, CKreative Digital, rebuilt a client site this way in late October with Claude connected straight to the site through the new Elementor MCP — and their report reads like a normal build, except the first pass was typed, not dragged.
Two details are worth knowing before you start. Every generation is a draft — nothing the MCP creates is published on its own, so a bad instruction cannot push a broken page live while you are making coffee. And connecting is free, but Pro elements still need a Pro plan, and your AI tool's own subscription is separate.
The One Limit You Need to Know First
The MCP currently supports Atomic (V4) elements and layouts only. Pages built with classic widgets — the V3 editor most of us have used for years — are outside it for now, and Elementor says support for them is coming. This decides whether you can use the connector today or not.
If your site is already on the Atomic editor, which arrived with Elementor 4.0 in April 2026, you are ready. If your site is still built with classic widgets, the rebuild comes first — and that is a real job, not a toggle. You need Elementor 4.3 or newer, an administrator account, and a compatible AI client. Elementor lists Claude Desktop, Claude Code, Cursor and Codex as the tools it works best with.
The good news is that the gap is already being filled from the sides. Respira, an independent MCP server, works on classic widget pages and Atomic elements alike, and every edit lands on a copy first, with 90 days of undo. Atomic Addons, a free plugin at version 1.9.0, registers 31 abilities through the WordPress Abilities API and serves them from its own MCP endpoint. And UiCore PRO added its own MCP integration in version 2.5.0 this month. None of these replaces the official connector, but together they mean the "classic widgets" limit is a matter of when, not if.
How to Set It Up
The setup is shorter than most plugin installs I have done. In your WordPress dashboard, go to Elementor, then Elementor MCP, pick your AI client — Claude Code is listed among the choices — and copy the setup prompt Elementor generates. The prompt creates a secure application password behind the scenes and builds it into the connection. Paste it into your AI tool and you are connected.
My advice: do this on a staging copy first. The connector uses your WordPress user's permissions, so an administrator connection can do administrator things. Treat the agent like a new team member with admin access — useful, supervised, and never pointed at a live client site on day one.
The Prompts That Actually Work
Vague briefs get vague pages, and that is as true for an agent as it is for a junior developer. The prompts that work name the audience, the goal, the sections and the tone. A few I would start with:
- "Build a draft Black Friday landing page: a hero with our 30% offer, a countdown to November 30, three featured products, customer reviews and an FAQ. Use our kit colors."
- "Build a draft services page for a plumbing company: hero, services grid, testimonials, contact form, local SEO headings."
Then review the draft the way you would review a colleague's first pass: check the copy, the links, the mobile layout and the forms. The agent does the dragging; the judgement is still yours.
How This Fits the Bigger Shift
Step back for a moment, because Elementor MCP is not happening in isolation. Breakdance 3.0 and Oxygen 6.2 shipped agent control within about 90 minutes of each other last month, Divi has its own AI agent for Divi 5, and WordPress's own AI team is openly working on making WordPress agent-ready.
What is different about Elementor's move is the audience. Elementor is the largest third-party builder in the WordPress world, and its MCP turns the editor millions of people already use into something an agent can drive. The skill that matters is shifting in plain sight: the dragging was never the craft. Writing a sharp brief, reviewing agent output like a professional, and fixing what it gets wrong — that is the job now.
The Limits I Would Not Ignore
I am enthusiastic about this, but here are the limits, because I have watched enough new tools to know where they break.
First, agents make confident mistakes. They will build a beautiful section with the wrong phone number or a pricing table with last year's prices, or a layout that looks fine on desktop and collapses on mobile. The draft step helps, but it is no substitute for opening the page yourself on a real phone.
Second, Atomic-only is a real constraint today. If most of your client sites are still classic widgets, the connector is a reason to plan your V4 migration, not a tool you can use on those sites tomorrow.
Third, access is the security question nobody has fully answered yet. An agent connection that can edit pages, templates and design systems is enormously powerful, and enormously risky if it is misconfigured. Least privilege, reviewed regularly, revoked the moment you stop using it.
Fourth, cost is still fuzzy. The connector is free, but the AI provider is not. A big site build can burn through a meaningful chunk of tokens on your Claude, Codex or Cursor subscription.
What I Would Do This Week
Here is the short list I would work through this week:
- Check whether your sites are Atomic. Open your most-edited client site and see whether its pages are built with V4 elements. That one check decides whether you can use the MCP today.
- Connect it on a staging site. Elementor, then Elementor MCP, pick Claude Code or Cursor, paste the setup prompt. Build one small page and time it.
- Write down your review checklist. Before any AI-built page goes live, check the copy, links, mobile layout, forms and loading speed.
- Try one real edit, not just a new page. "Update our holiday hours" or "make the phone number bigger on phones" — the small edits are where you will feel whether this saves time.
Most of it is an afternoon's work.
Conclusion
Elementor MCP being officially live is the moment the world's most-used WordPress builder stopped being something you only drive with a mouse and became something you can direct with words. The connector is free, the setup takes minutes, and the output is a real, editable Elementor page saved as a draft for your review. The Atomic-only limit is real, and the review discipline around it is non-negotiable — but the direction is settled. Every builder is moving the same way, and Elementor has just made sure its users are not left watching from the sidelines.
Frequently Asked Questions
What is Elementor MCP?
Elementor MCP is Elementor's official Model Context Protocol connector, announced on September 15, 2026 and shipped in Elementor 4.3 on September 22. It connects AI tools such as Claude, Codex, Cursor and ChatGPT to your WordPress site so the assistant can read your Elementor pages and build or edit them from plain-language prompts, saving everything as a draft for your review.
Do I need Elementor Pro to use Elementor MCP?
Connecting is free, but Pro elements still need a Pro plan, and your AI tool's own subscription is separate — the MCP does not include an AI model or credits. You also need Elementor 4.3 or newer, WordPress 6.8 or newer, an administrator account, and a compatible AI client such as Claude Desktop, Claude Code, Cursor or Codex.
Does Elementor MCP work with classic widget pages?
Not yet. The official connector currently supports Atomic (V4) elements and layouts only; Elementor says support for classic widget (V3) layouts is coming. Independent options such as Respira already work on classic widget pages as well as Atomic elements, with every edit landing on a copy first and 90 days of undo.
Will the AI publish pages to my live site automatically?
No. Every page or change the MCP creates is saved as a draft. Nothing is published on its own — you open the draft in the Elementor editor, review it, tweak anything by hand, and publish only when it is right.
How is Elementor MCP different from Elementor 4.4's agent-ready features?
Elementor 4.4 made your website agent-ready with llms.txt support and WebMCP, so outside agents could read and understand your site. Elementor MCP is the other half: it lets an agent edit and build pages inside the editor, not just read the finished site.
