MCP server
Elementor MCP server, with undo on every edit.
An Elementor MCP server lets Claude, ChatGPT or Cursor read and edit Elementor pages on a live WordPress site, classic widgets and Atomic elements alike. With Respira every edit lands on a copy first, and you can undo it for 90 days.
7 days free. No card. Runs on the AI subscription you already have.
- Support
- Full
- Elementor tools
- 8
- Latest release touching it
- 9.1.20
- Releases touching it
- 103
Respira is an independent MCP server. Not affiliated with, endorsed by, or sponsored by Elementor Ltd. Elementor is a trademark of Elementor Ltd.
What this page says about Elementor's own tools was checked against Elementor's pages on 22 September 2026.
Elementor's own MCP edits Atomic pages. Respira edits every page, with undo.
Elementor opened its MCP to beta testers on September 15, 2026. It builds and edits pages made in the new Atomic editor, which a site has to switch on, and saves each change as a draft. Pages built with classic widgets are outside it. You can use both: Respira runs Elementor's own abilities too, with a snapshot of the page first.
| Topic | Elementor's own MCP (beta) | Through Respira |
|---|---|---|
| Pages it can edit | Pages built in the Atomic editor. | Classic widget pages and Atomic pages. |
| Where a change lands | Elementor says the MCP saves what it generates as a draft. The editor tools shipped in 4.2.4 also carry save-publish and save-update, so an agent working in the editor can publish. | Made on a copy first, approved by you in WordPress, with 90 days of undo. |
| Site colours and fonts | Global classes and variables on Atomic pages. | Also on classic pages: colours and fonts from Site Settings stay linked, so changing a global updates the page. |
| A page that changed after the agent read it | Elementor warns when its editor and the agent change the same page. | Refused when the agent passes the content_version it read. |
| What you switch on first | The beta tester flag in Version Control, the latest beta build, and the Atomic Editor. An administrator connects it per site. | Nothing to switch on in Elementor. Connect the site once and the same connection covers every page. |
| Which AI tools connect | Claude Code, Claude Desktop, Codex, Cursor, and other MCP clients. | The same clients, plus ChatGPT and anything else that speaks MCP, on one connection for every site you run. |
| Your other client sites | Elementor only. | The same tools on 17 page builders. |
| Global classes, variables and default styles | Changed in place. They are not pages, so page revisions do not hold them. | Snapshotted together before the change. One restore puts all of them back, deleted classes included. |
| Elementor's own abilities | Called directly. | Called through Respira: snapshot first, logged in Activity, undo handle returned. |
Elementor's MCP needs its beta and the Atomic editor. Respira works on the Elementor you run today. When you add Elementor's MCP, opt its abilities in under Respira > Abilities and your agent calls them through the same Respira connection.
Their documentation: Elementor's MCP beta announcement
What works today. What still needs you.
Read from the current MCP server release, first-class reads and writes across the builder structure.
Works now
- Reads classic widgets (v3), Pro widgets and Atomic elements (v4), and tags each one
widget_v3orwidget_v4so the agent writes the right format. - Writes Atomic elements with per-breakpoint and per-state styles (hover, focus, active and more), and validates each tree before it is saved.
- Colours and fonts taken from Site Settings stay linked on classic widgets, so changing a global updates every element that uses it. A new colour set on a linked element replaces the link, as it does in the Elementor editor.
- Global colours and the design system, read and written through dedicated tools (
wordpress_elementor_design_system,wordpress_update_elementor_global_colors). - Pro widgets are detected: with Pro active they appear in
wordpress_list_elementor_widgetsnext to the Free ones. - The add_* tools write the controls Elementor reads and render on the page: 20 of 22 checked on Elementor 4.1.1 without Pro. The search box, gallery and pricing table are built from free widgets; the form and slider need Elementor Pro and say so.
- Elementor's own MCP abilities run through Respira with a snapshot first: the page, or for global classes, variables and default styles, the whole design system as one restore point.
- A style written as plain CSS lands as Elementor's own typed values, because it goes through Elementor's converter:
padding: 6rem 4rembecomes all four logical sides. What the converter cannot take becomes that element's custom CSS, and what it refuses is named in a warning. Needs Elementor 4.2 or newer; older releases keep the value as sent. - The stylesheet Elementor keeps for v4 styles is rebuilt after every write, so a style shows on the page instead of waiting for someone to open the editor.
- Every widget and element reports whether it is atomic or classic, whether it can hold children and whether it needs Pro, read from Elementor rather than a list.
wordpress_list_elementor_widgetslists elements too, so containers are findable. - The design system export returns v4 variables and global classes next to the kit colours and fonts, each with the reference to write, so an agent reuses what the site has instead of minting a one-off style per element.
- A change can name the page version it read (
expected_version) and is refused, with nothing written, if the page changed in the meantime.
Where a human still steps in
- Atomic element types Respira does not model yet are refused with a list of the supported types instead of being dropped. Edit those in the Elementor canvas for now.
- Elementor gives elements new internal IDs when it saves in its own editor, so after an editor session compare by content, not by ID.
- Some Pro display conditions, such as date ranges and geolocation, read fine but cannot be written through the MCP yet.
- Theme Builder templates (header, footer, single, archive) are listed, but editing their structure through the MCP is not supported yet.
Hit one of these and the snapshot gives you a clean way back.
8 tools made for Elementor.
Registered in the MCP server at build time. Each name is the id your client calls, on top of the universal set: find, update, move, remove, build, snapshot, roll back.
wordpress_list_elementor_widgetswordpress_get_elementor_widget_schemawordpress_elementor_design_systemwordpress_update_elementor_global_colorswordpress_update_elementor_global_typographywordpress_elementor_add_custom_jswordpress_add_stock_imagewordpress_validate_elementor_json
Three prompts you can paste right now.
Each one assumes Respira is connected to a Elementor site. Paste it into your AI tool and run.
-
Refresh CTA copy on every landing page
Find every Elementor button widget whose text is "Get started" on pages tagged "campaign". Change the text to "Start free" and the URL to /pricing. Show me the diff first. -
Find colours that should be globals
List every colour used on pages built with Elementor that is not linked to a Site Settings global. Group them by value, and suggest which ones should become globals. -
Audit Pro widget usage
Which Elementor Pro widgets are actually used on this site, and on how many pages each? Output a markdown table.
More recipes, per builder, in the Prompt Book.
Connect a Elementor site in two minutes.
Chat apps sign in with the browser. Coding tools take one command. Anything else takes the config below.
One command
Detects Claude Code, Cursor, Codex, Windsurf and more, and writes the config.
npx add-mcp "npx -y @respira/wordpress-mcp-server@latest"Or paste the config
Get the site URL and key from your setup page.
{
"mcpServers": {
"respira-wordpress": {
"command": "npx",
"args": ["-y", "@respira/wordpress-mcp-server@latest"],
"env": {
"WORDPRESS_URL": "https://yoursite.com",
"WORDPRESS_API_KEY": "respira_your_api_key_here"
}
}
}
}- Claude Desktop on macOS reads
claude_desktop_config.json, notconfig.json. - Prefer no terminal at all? Sign in with your browser from Claude, ChatGPT or Cursor.
What changed for Elementor lately.
The last 5 releases that mention Elementor, filtered from the same changelog the releases page reads.
-
- Elementor append works with Elementor's own format. mode append merged
-
- find_element by content, text or class works on every builder. A
-
- wordpress_find_in_page (plugin 9.1.11). Finds text in the HTML a visitor gets for a page, head included, and names the snippet or setting on the site that holds it: Elementor Custom Code, WPCode, the header and footer co
- wordpress_find_element searches content, text and class on every builder (plugin 9.1.11). The description says each match names its field with a snippet and that no match is a normal answer with found: 0. wordpress_apply
-
- Elementor 4.3: a page with an Accordion can be edited again. Respira
- Elementor 4.3: untouched v4 elements are left alone. Edits rewrote
- Elementor 4.3: a style added to an element with a class list shows
-
- Edits work again on Elementor 4.3 pages with the new headings and
- A new v4 heading no longer comes out empty on Elementor 4.3. Text
Questions people ask about Elementor and MCP.
Elementor has its own MCP now. Do I still need Respira?
Elementor's MCP edits pages built in its new Atomic editor, and it is in beta. Respira edits those and classic widget pages, makes every change on a copy you approve, keeps 90 days of undo, and works the same way on your client sites that run other builders. Respira can also call Elementor's own abilities, with a snapshot of the page first.
How do I connect Elementor to Claude, ChatGPT or Cursor?
Install the Respira plugin on the WordPress site, then add Respira in your AI tool: Claude and ChatGPT sign in through the browser and ask you to approve the site once, Cursor and Codex take a one-line command. Nothing is installed inside Elementor, and the same connection covers every site on your account.
Is the Elementor MCP a plugin or a server?
Both words describe one setup. The MCP server is the piece your AI tool talks to; the WordPress plugin is what it talks to on the site. With Respira you install the plugin on the site and your AI tool connects to the server, and you do not run anything yourself. Elementor's own MCP works differently: it is part of Elementor, switched on from inside it.
Is Elementor's own MCP free, and what does it need?
It follows the Elementor plan you already have, so the basics are free and Pro elements need Pro. It is in beta: you enable the beta tester flag in Version Control, update to the latest beta build and activate the Atomic Editor, then an administrator connects it for that site. Some features, such as custom widgets and WordPress-wide actions, need Elementor's Angie installed as well. Checked against Elementor's announcement on 22 September 2026.
Can an agent break an Elementor page through the MCP?
It can write something you did not want, the way a person can. What it cannot do with Respira is land that on the live page unseen: the edit goes to a copy, you approve it in WordPress, and every write is snapshotted with 90 days of undo. A page that changed since the agent read it is refused rather than overwritten.
Is there an MCP server for Elementor?
Yes. Respira is an independent MCP server that reads and writes Elementor in its own format, with first-class reads and writes across the builder structure. It is not made by the Elementor team.
Which tools does it use for Elementor?
8 Elementor-specific tools on top of the universal set: find, update, move and remove elements, build pages, snapshot and roll back. The list on this page is read from the MCP server source at build time.
What happens when the agent gets an edit wrong?
Nothing on the live page. The agent edits a copy first, you approve it inside WordPress, and every write is snapshotted with 90 days of undo.
Do I need a developer or a terminal?
No. Sign in with your browser from Claude, ChatGPT or Cursor and approve the connection once. Coding tools get a one-line command.
Does it work with a Elementor site that also runs WooCommerce?
Yes. The WooCommerce add-on adds 104 store tools on the same connection, with the same duplicate-first approval flow.
Looking for the Elementor overview, with visuals and the conversion story? Elementor features
What is Elementor Angie, and how Respira relates to it
Elementor Angie is Elementor's own AI assistant for WordPress: a free plugin, listed on WordPress.org under the name Angie, that opens a chat panel in wp-admin and in the Elementor editor. From that panel Angie generates Elementor pages, widgets and code snippets and runs site tasks by conversation, on a free tier with daily credits. Since version 1.1.14 Angie also has Angie MCP, which lets an AI client connect to the site through Angie.
Respira is a different thing, and not made by Elementor. Respira is an MCP server for the AI client you already use, Claude, ChatGPT, Cursor or Codex, and reads and writes Elementor pages in Elementor's own format, next to 17 page builders in total. Every edit lands on a copy first, you approve it inside WordPress, and you can undo it for 90 days.
The two can meet. When Angie is installed, the Respira plugin can register Respira as an MCP server inside Angie, so Angie's chat reaches Respira's tools. Respira does not need Angie, and Angie does not need Respira.
Their page: Angie on WordPress.org
The other builders, same server.
Start with one site. Free for 7 days.
Maker is €9 a month after the trial. No card for the trial, and it runs on the AI plan you already have, so there is no extra AI bill.
