Respira Review: The WordPress AI Editor We Use Daily
Practitioner notes on AI, SEO, PPC, and agency operations.
We run AI agents against live WordPress sites every day. The tool that makes that safe and fast is Respira, an AI infrastructure layer for WordPress. After months of daily use across many client sites, here is our honest review: what it does, where it shines, where it still has rough edges, and why we back the person building it.
What Respira Actually Is
Respira is not another chatbot that spits out HTML you paste in by hand. It is a plugin plus a Model Context Protocol layer that gives an AI assistant structured, permissioned access to your real WordPress install: pages, posts, menus, media, options, SEO metadata, and the page builder itself. The AI reads and edits the actual site, not a generic copy of it.
The name is fitting. Respira means breathe in Romanian, and the product is built to make AI edits feel calm and reversible rather than reckless.
Why Respira Over the Plain WordPress MCP
This is the question we get most. WordPress now has an official MCP server and a new Abilities API, so why pay for Respira? The short answer is reach. The bare WordPress MCP exposes a thin slice of what your site can really do, mostly core actions like creating a post or reading an option.
The bigger picture is the Abilities API. It is the emerging standard that lets any plugin register what it can do so an AI can call it directly. RankMath, Elementor, your forms plugin, your commerce plugin, each one can publish its own abilities. On a stock setup you are left with two bad options: stay limited to core WordPress actions, or stand up a separate MCP server for every plugin and juggle a dozen connections that all drift out of sync.
Respira solves this by aggregation. It reads the Abilities API from every installed plugin and rolls them all into one MCP server. SEO fields, builder widgets, media optimization, menus, custom post types, all reachable through a single connection. That is how Respira reaches more than 200 tools while a plain WordPress MCP gives you a handful. One server, every plugin’s powers, builder-native output. That is the real unlock, and it is why we reach for Respira instead of the bare WordPress MCP or a tangle of single-plugin servers.
How It Works: Duplicate First, Then Go Live
The safety model is the best part. Risky work is routed through a duplicate-first workflow, so the AI builds or edits a staged version before anything touches the live page. Pre-edit snapshots mean you can roll back instantly. The promise that every edit and optimization stays yours and is never silently undone is one Respira takes seriously.
It works across 16 page builders, including Elementor, Divi, Gutenberg, Bricks, and Oxygen, with more than 200 tools spanning WordPress core, builders, media, and SEO. Importantly, the output is native. A Divi build comes back as real, editable Divi modules, not locked code blocks a human cannot touch later.
It Ships Almost Every Day
Respira moves fast. The public changelog reads like a daily build log. A recent milestone, the 7.4.0 release nicknamed Clearing, was a verification pass whose whole point was making sure what the agent writes is what actually lands on the page, with explicit reporting when content cannot be persisted. That kind of release tells you the maker is listening to exactly the problems real users hit.
Where It Shines
For an agency, the speed is the headline. Building service and location pages, fixing SEO titles and descriptions, restructuring menus, optimizing images, and cleaning up content all happen at a pace manual editing cannot match. Because Respira speaks each builder natively, the work stays editable by a human afterward. It has quietly become a backbone of how we deliver.
The Honest Limitations
No tool is perfect, and we would not trust a review that pretended otherwise.
- One site context at a time. The connection holds a single active site, so juggling several sites in parallel sessions takes more care than we would like. You switch context deliberately rather than fanning out across many sites at once.
- Verify your writes. On heavily cached sites we have occasionally had to confirm an edit actually landed before clearing caches, because builder and page caching can mask a fresh change. The Clearing release directly targeted this, and it is noticeably better, but read-back verification is still a good habit.
- Solo-founder pace. This is built by one person, so the occasional rough edge appears. The flip side is that fixes land quickly, often within days of a report.
None of these are dealbreakers for us. They are the normal tradeoffs of an ambitious tool from an independent builder who ships in the open.
The Person Behind It
Respira is built by Mihai Dragomirescu, a solo founder in Brasov, Romania. He ships in public, answers his own support, and turns requested features around fast. The early-adopter licenses, the genuine help, and the speed of his fixes are why we recommend this tool by name. Buying Respira supports one builder who actually cares, not a faceless platform.
Our Verdict
If you run WordPress and want an AI editor that respects your real site, Respira is where we point people. There is a free Lite tier to try, and paid plans start at around $79/year. It is one of the best value tools in our stack.
We put together a fuller breakdown of how we use it and how to get started on our WordPress AI Editor page.
