By Fahad Murtaza · Published · Updated
Elementor AI vs MCP: what each does and when to use it
Elementor AI and an MCP connection both let an AI help you build Elementor pages, and people search for “Elementor AI” expecting one answer. They are different things. Elementor AI is an assistant built into the editor. MCP is an open protocol that lets an AI client you choose reach into your site. This guide compares them on what they do, what they need, how they handle mistakes, and which fits which job.
I have kept every claim about Elementor to what its own pages say, and left prices out. Elementor changes plans and credit rules often, so a number copied into an article goes stale quickly.
What is the difference between Elementor AI and MCP? Elementor AI works inside the editor, on the page or widget you have open, with models Elementor chose. MCP lets an outside client such as Claude or Cursor call tools on your site, so the agent can work across pages, templates, global styles and the rest of WordPress. One is a feature of the builder. The other is a connection to your site.
What Elementor AI does
According to Elementor’s AI page, the in-editor assistant covers four kinds of work:
- Text: write headlines, paragraphs and calls to action, translate text, change tone, and draft SEO titles and descriptions.
- Images: create images from a prompt, edit an existing image, and make variations.
- Code: generate custom CSS and HTML snippets from a description, with suggestions in the Custom CSS and HTML widgets.
- Sections: generate the text and images for a hero or feature section.
Elementor also builds an agent called Angie, described on its AI products page. Angie builds full pages, design systems from a screenshot, forms and loops (these two need Elementor Pro), and code such as custom widgets and admin snippets. You open the editor, click Angie and describe what you want.
The strength of all this is that it sits where you already work. There is no API key, no extra software on your computer and no protocol to learn. The limit is the same fact seen from the other side: it works through the editor, in the shapes Elementor built for it.
What an MCP connection does
MCP, the Model Context Protocol, is how an AI client discovers and calls tools on a server. If the idea is new, read what an MCP server is and the protocol explained. For Elementor, the server exposes the page as tools, and the client decides which to call.
There are two routes to know about:
- Elementor’s own MCP. Elementor’s MCP page says it connects Claude, Codex, Cursor and other AI tools to your Elementor site, that only site admins can connect, and that what gets built lands as a draft for you to review. It says some features need the free Angie plugin, and that editing existing pages works only for sites using atomic elements and layouts (Elementor V4), with older widget layouts listed as coming.
- WP MCP. An independent WordPress plugin, not made by or affiliated with Elementor. It serves an MCP endpoint at
https://your-site.com/wp-json/mcp/wpmcp-serverand exposes Elementor through its own validated tools. See Elementor MCP and the Elementor integration for the full list.
WP MCP’s Elementor tools work from a curated catalog. In the tool list, list-widgets and get-widget-schema are free, while get-elementor-data, add-widget, update-widget and update-global-colors are Pro. A call to read the page and then add a widget looks like this:
{
"jsonrpc": "2.0", "id": 4, "method": "tools/call",
"params": {
"name": "wpmcp-get-elementor-data",
"arguments": { "post_id": 42 }
}
}
The reply carries the element tree and an expected hash. The agent sends that hash back with its write, so a stale edit is refused instead of overwriting newer work. This read-then-write pattern is the main safety habit in Elementor v4 atomic elements too.
Side by side
| Elementor AI (in the editor) | MCP connection | |
|---|---|---|
| Where you work | Inside the Elementor editor | In Claude, Cursor or another MCP client |
| Which model | Chosen by Elementor | Chosen by you |
| Scope | The widget, section or page open in the editor | Pages, templates, global styles and the rest of the site |
| Setup | Elementor account, plugin plus AI access | Connect a client to an endpoint with a credential |
| Best at | Copy, images, snippets, quick section drafts | Multi-step jobs across many pages |
| Billing | Elementor credits or plans | Elementor’s plan for its MCP, or the WP MCP tier, plus your own AI client costs |
| Undo | The editor’s own history | Depends on the tool (see below) |
Requirements and cost, as Elementor states them
Treat this section as a snapshot of Elementor’s pages as they read when I checked, and verify them again before buying.
- Elementor’s AI page says each AI action uses between 1 and 40 credits depending on the request, that credits sit in a monthly pool shared with other Elementor services, and that unused credits do not roll over.
- The same page says credit costs may change over time, and its FAQ says you first need an active Elementor Pro plan before buying an AI subscription.
- Angie is described as having a free plan with daily-renewing credits, with extra credits not purchasable on their own for now, and as needing an Elementor account to log in.
- Elementor’s MCP page lists the MCP as included in its plans, says connecting is free, and says AI actions draw on the same credits. It adds that your AI tool’s own costs are separate.
Elementor’s pages do not always agree on plan names and inclusions, which is why this guide gives no prices. With WP MCP, the Elementor deep editing tools are part of the Pro tier, and the site’s pricing page has the plans. Your AI client has its own subscription or token cost either way.
Undo and safety
This is where the two approaches differ most for a live site.
An editor assistant makes a change you can see, and you review it before you leave the page. An MCP agent can change several pages in one session while you are not watching, so recovery matters more.
WP MCP snapshots every supported write before it runs. _elementor_data is ordinary post meta, so the standard post snapshot captures it. You can list the changes and undo them from the AI:
{
"jsonrpc": "2.0", "id": 9, "method": "tools/call",
"params": { "name": "wpmcp-list-operations", "arguments": {} }
}
{
"jsonrpc": "2.0", "id": 10, "method": "tools/call",
"params": { "name": "wpmcp-rollback-operation", "arguments": { "operation_id": "OPERATION_ID" } }
}
rollback-session unwinds everything one agent session did, and the wp-admin screen has a Restore button per operation. A few kinds of change cannot be snapshotted, such as package updates and raw database writes, and WP MCP says so in its response. More in undoing changes in WordPress.
Elementor’s MCP page describes a draft-first workflow. That is a good habit, and it reviews what the agent made, but it is not the same thing as a per-operation undo of edits to an existing page. If you rely on any agent to modify live pages, test the undo path on a copy before you trust it.
Which one should you use?
Use Elementor AI when:
- You are in the editor and want a headline, a translation, an image or a CSS snippet right there.
- You work alone on one page at a time.
- You want no setup outside Elementor.
Use an MCP connection when:
- The job spans many pages, such as restyling the kit’s colors and fonts, or fixing the same issue on thirty pages. See editing Elementor global styles.
- You want to pick the model and keep working in Claude Code, Claude Desktop or Cursor. The client comparison shows how they differ.
- The task is wider than Elementor: posts, SEO fields, forms, media, WooCommerce, all in one conversation. WP MCP covers the whole site, with 407 tools in total (274 free and 133 Pro), though a site sees fewer when optional plugins are inactive.
- You need undo per operation or per session.
They also combine well. Draft copy and images with Elementor AI in the editor, then ask an agent to apply the result across the site’s templates.
Connecting a client to WP MCP
If you decide to try the MCP route with WP MCP, the short version is:
- Install the WP MCP plugin on WordPress 6.9 or later with PHP 8.1 or later.
- Create a WordPress application password for a dedicated user. The application password guide shows how.
- Point your client at
https://your-site.com/wp-json/mcp/wpmcp-serverwith the password sent as a Basic header. Claude Code takes it in one command. - Ask for something read-only first, such as “List my Elementor pages and tell me which use containers.”
- Then try a small write on a test page, and undo it.
Claude on the web needs OAuth, which WP MCP ships switched off. The custom connectors guide covers it. ChatGPT also needs OAuth and has not been fully tested with WP MCP, so treat it as experimental. If you are new to the whole flow, the MCP tutorial walks through it end to end.
The short answer
Elementor AI is a feature of the builder, strongest for copy, images and snippets in the page you have open. MCP is a connection that lets an agent you choose work across the site, which suits bigger and repeated jobs, provided you can undo. Elementor now offers both an in-editor assistant and its own MCP, so the question is less “which product” and more “which kind of job”.
For the Elementor tools in WP MCP, start at Elementor MCP. Running Divi sites too? Divi AI vs MCP makes the same comparison for Divi 4 and Divi 5.
Common questions
What is Elementor AI?
Elementor AI is Elementor's built-in assistant. Per Elementor's own pages it writes and translates text, creates and edits images, generates custom CSS and HTML, and drafts section content from a prompt, all from inside the editor. Elementor also offers Angie, an agent that builds layouts from a description.
Is Elementor AI free?
Elementor describes a free plan with daily-renewing credits for Angie, and says extra credits cannot be bought on their own for now. Elementor's pricing pages also tie AI to paid plans and credits, and the pages do not always agree, so check the live page before you rely on any figure.
What is the difference between Elementor AI and MCP?
Elementor AI is an assistant that lives inside the editor and works on the widget or page you have open. MCP is an open protocol that lets an outside AI client, such as Claude or Cursor, connect to your site and call tools. With MCP you choose the client and it can work across the whole site, not only one page.
Can I use Claude or ChatGPT with Elementor?
Yes, through MCP. Elementor now offers its own MCP connection, and WP MCP is an independent plugin that does the same job through its own validated tools. Claude Code, Claude Desktop and Cursor are well tested with WP MCP. ChatGPT needs OAuth and is not fully tested.
Can I undo what an AI agent changed in Elementor?
With WP MCP, yes. Every supported write is snapshotted before it happens, and you can undo one operation or a whole session from the AI or from wp-admin. Elementor documents drafts you review before publishing for its own MCP. Check what each tool does for undo before you let it write.
Do I need Elementor Pro for either?
For Elementor AI, Elementor's FAQ says you first need an active Elementor Pro plan. For WP MCP the tools work with free Elementor, and the Elementor deep editing tools are part of WP MCP Pro. Elementor's own MCP lists extra tools such as Forms and Popups on Pro plans.
All WP MCP guides, or see every plugin integration. Topic: Elementor.