What is Elementor MCP?
Two different products answer to the name Elementor MCP, which makes the question worth a page of its own. This one defines the protocol, separates the two products, and describes what the paid plugin sold here does on your WordPress site.
What does MCP stand for?
MCP means Model Context Protocol, an open standard for connecting AI assistants to software.
Anthropic published it in late 2024 and other vendors adopted it quickly, so the same connection now works with Claude, ChatGPT, Cursor or Codex. Think of it as a standard plug rather than a piece of software: before it existed, every assistant needed bespoke wiring for every tool it wanted to reach, and that wiring broke whenever either side changed.
The protocol has nothing to do with WordPress or with page building: it only settles the shape of that conversation. Anything can sit at the far end — a spreadsheet, a ticketing system, a design file, or a website.
What is an MCP server, and what is the client?
The server is the software that offers the actions; the client is the assistant that calls them.
Naming trips people up here, because the assistant you type into is the client, even though it feels like the main program. The server is the quiet half: it publishes a list of named actions, waits, executes the one it is asked for, and reports what happened. It usually runs where the data lives, which is the whole point — the assistant works on the real thing instead of on a description of it.
That is why a server for Elementor belongs inside WordPress: your pages, your media library and your design settings are there, and none of them can be edited convincingly from the outside.
Which two products are called Elementor MCP?
One is Elementor's own free MCP; the other is this paid third-party plugin.
The distinction matters before you install anything, because the names are nearly identical and the two are bought, installed and used differently. Here is how to tell which one you are looking at:
- Elementor's official MCP — announced in beta on 15 September 2026, generally available since 23 September, built by the Elementor team. Pricing follows Elementor's existing plans: in their words, basic sections and features are free to generate while Pro elements require a Pro plan. It converts Figma files and Google Drive documents into native Elementor content, and delivers each generation as a draft to review.
- Elementor MCP, the plugin sold on this site — an independent WordPress plugin written by Youness Fatine, not affiliated with Elementor. One payment of €9.99 covers a lifetime license bound to a single site, with 37 tools, writes normalised and audited on our server before they touch your pages, and repeatable content stored as custom post types with ACF fields.
Neither one is a replacement for Elementor: both need Elementor installed and both build inside it. If the official MCP covers what you need, use it — it is free and it comes from the people who make the editor.
What does the plugin actually do on your site?
It turns your WordPress install into an MCP server your assistant can operate.
Once activated, the plugin publishes its tools at a single address under your own domain and creates a dedicated WordPress account, MCP_ELEMENTOR, with an Application Password. Your assistant authenticates as that account, which keeps the access auditable and separate from your own login.
From there the assistant works with a defined set of actions rather than free-form guesses: read your kit's global variables and reuse them instead of hardcoding colours and sizes, rewrite the element tree of a page, register custom post types and ACF field groups, add Schema.org markup, convert heavy images to WebP, and compare the built section against your mockup check by check.
Writes take a detour through our server on purpose. Every tree is normalised and put through a structural SEO audit — one h1, no skipped heading levels, alt attributes, valid JSON-LD — before Elementor's own save routine applies it. If that round trip fails, the write is refused rather than approximated, so a half-validated structure never lands on a live page.
Who is it for, and what changes day to day?
It is aimed at freelancers and small agencies who build Elementor client sites.
The practical shift is that your assistant stops producing instructions you then execute by hand. You describe a section, or share a mockup, and the section appears in the page you named — still fully editable in the Elementor editor afterwards, element by element, because it was written through Elementor's own save path rather than pasted in as markup.
Being a non-developer is not an obstacle: the plugin installs from a .zip file like any other, and the whole workflow happens in the conversation you already have with your assistant.
What do you need before you start?
Three things: a WordPress site with Elementor, an AI assistant, and a license.
- A WordPress site running Elementor with its current editor. Elementor Pro is not required; the plugin builds with atomic elements and ships its own widgets for forms, listings and FAQ.
- An AI assistant that speaks MCP — Claude Desktop, Claude Code, ChatGPT, Cursor or another compatible client — on your own subscription. The generation runs there, on the plan you already pay for.
- One license per site. It binds to the first site that activates it and stays with that site, so a staging copy and a production site are two licenses.
Nothing else is billed and no third-party API key exists in the plugin. Our platform never calls an AI model: it validates your license, keeps the license tied to one site, and normalises and audits the trees your assistant writes.
Where should you go next?
Pick the page that matches where you are right now.