On September 23, 2026, Elementor officially launched Elementor MCP, a connection that lets AI tools like Claude, Codex, and Cursor build directly inside a WordPress site’s real Elementor structure, following a beta that ran from September 15. It is a genuinely different way of building pages, and it is worth understanding both what it does well and where a human still needs to be in the loop.
What Is Elementor MCP?
MCP stands for Model Context Protocol, an open standard that lets AI assistants connect to external tools and data sources rather than working from a blank chat window. Elementor’s implementation lets an AI tool read and write directly into Elementor’s own building blocks: sections, containers, widgets, classes, and design variables. Instead of generating a wall of raw HTML for you to paste in, the AI is generating an actual Elementor page, the same structure you would get by building it in the editor by hand.
That distinction matters. A generic AI-written page usually needs to be rebuilt inside your page builder before it looks or behaves right. An Elementor MCP output opens directly in the visual editor, already using your fonts, colours, and spacing, ready to be nudged rather than reconstructed.
What It Can Actually Do
Based on Elementor’s own documentation, the current capabilities include:
- Building complete pages and layouts, content and styling together, in a single step
- Editing or restructuring existing pages rather than just appending new content to them
- Creating and managing design system elements: colour and typography classes, spacing variables, and responsive breakpoints
- Building site-wide templates such as headers, footers, archive pages, and popups, including their display conditions
- Placing existing components or creating new ones
- Connecting dynamic content from post fields, taxonomies, and custom fields
- Pulling context in from Figma, Google Drive, or Notion and translating it into a real page
A further layer, custom widgets, bulk content updates, and deeper WordPress Abilities API access into plugins like WooCommerce and Yoast, requires Elementor’s separate Angie plugin. Right now the AI-building side works with Elementor’s newer Atomic (V4) structures, with support for the older Widget-based V3 sites promised soon.
How the Connection Actually Works
Setup happens from an Elementor > MCP screen inside the WordPress dashboard, restricted to site administrators. You pick an AI tool from a list, Claude Code, Claude Desktop, Codex, Cursor, or a generic “other” option, and Elementor generates a one-time prompt with an application password already embedded. Pasting that prompt into the chosen AI tool completes the connection; nothing needs to be configured by hand unless you want to.
From there, you describe what you want in plain language, and the AI works inside that specific site’s design system rather than inventing its own. Every output lands as a draft, not a live page, so nothing goes public without a person opening it in the visual editor and approving it first. If someone is editing visually at the same time the AI is working, Elementor flags the conflict and asks whether to keep or discard each version, rather than silently overwriting either one.
Why This Is a Bigger Deal Than It Sounds
WordPress has had page builders for well over a decade, and Elementor is the one most small business sites are already built on, which is part of why this comparison between Elementor, Divi, and Gutenberg keeps coming up in client conversations. What changes with MCP is not the builder itself, it is who, or what, is allowed to operate it directly. Landing pages, seasonal promotions, and routine template updates that used to take an hour of manual section-building can now be roughed out in minutes, then finished and polished by a human. One agency testing the tool on a live production site reported that it meaningfully sped up landing page creation and everyday site maintenance without changing how the site was actually built underneath.
For a small business, the practical upside is turnaround time. A new promotion, a seasonal landing page, or a content refresh does not need to sit in a queue waiting for a full manual build; the first draft can exist almost immediately, leaving the design and copy review as the actual bottleneck.
Where Human Judgement Still Matters
Every Elementor MCP output is a starting point, not a finished page. AI-generated layouts still need a real review pass for brand voice, accuracy, mobile behaviour, and whether the page actually persuades anyone to take action, the same review any of our own drafts go through before they go live. The tool is also new: current support is limited to V4 Atomic sites, several features require the separate Angie plugin, and per-site connections mean this is not yet a one-click, agency-wide rollout. Treat early output as a strong first pass, not a finished deliverable.
Related reading: Best WordPress AI Plugins in 2026: Honest Guide for Site Owners | Best AI Tools for Small Business in 2026: Honest Reviews by Category
Frequently Asked Questions
Does Elementor MCP publish pages automatically?
No. Every page or edit generated through Elementor MCP is saved as a draft. A site administrator has to open it in the visual editor and manually publish it, so nothing goes live without human review.
Do I need Elementor Pro to use it?
Connecting to Elementor MCP itself is free. Basic sections and layouts can be generated on any plan, but Pro-only features still require an Elementor Pro plan, and advanced actions like custom widgets or bulk updates require the separate Angie plugin.
Which AI tools work with Elementor MCP?
At launch, Elementor supports Claude Code, Claude Desktop, Codex, and Cursor directly from its setup screen, plus a generic option for any other MCP-compatible AI tool.
If this was useful, tell Google you want more of it.
