Account
Explore
Respira speaks 19 page builders plus the native Site Editor, snapshots page and element edits before they land, and gives every AI client (Claude Code, Cursor, Codex) a single MCP endpoint to work through. Run 5 to 25 sites without hiring.
One operator covers 5 to 25 client sites because every screen rolls up: audit log, approvals queue, snapshot timeline, activity report. Each audit entry links back to its snapshot, proposal, approval, or rollback, and your agent can read that history too. Page-by-page hand-holding is the old model.
Generate a 400-700 word client report your AI shapes into prose. Six framings (client report, case study, internal recap, testimonial draft, build-in-public, personal recap). Anonymize toggle for case studies.
Edits go through the builder's own write surface instead of raw HTML. 19 page builders plus the native Site Editor. Duplicate-before-edit + 90-day snapshot rollback. Fewer "the AI broke the page" tickets.
The plugin admin is React-first, built around live telemetry, a public add-on SDK for third-party authors,
and generate_activity_report, the MCP tool that turns your audit log into a structured report
your own agent shapes into prose. Below is that React admin running with stub data. Every screen renders,
every tab clicks, every form responds. Nothing here writes to a real site.
Reads, writes, builds, audits. Every action goes through the same duplicate-first + snapshot-backed safety model, and structural writes are verified against what WordPress actually rendered. Per-key access profiles let you give read-only access to a junior, full access to a senior, and content access to a copywriter. 260+ tools and abilities are included on every core plan.
Respira reads pages in the builder's own data shape (Gutenberg blocks, Divi shortcodes, Bricks JSON, Elementor atomic envelopes). Your agent gets the structure, not opaque HTML.
MCP server
extract_builder_content find_element + update_element + move_element + duplicate_element + remove_element. The page stays intact; only the target widget changes.
update_element build_page takes a structured description and writes a complete page in the active builder's format. 27 widget shortcuts (heading, button, image, gallery, etc.) for the common moves.
build_page New in 8.0. Your agent reads and edits block templates and template parts with their hierarchy and source, synced and unsynced user patterns, block navigation by exact block path instead of rewriting the menu document, and the theme.json design tokens. Registered theme and plugin patterns stay read-only.
list_site_templates · update_site_navigation Every structural write is fingerprint-guarded against a stale base, snapshotted, read back through WordPress, and server-render verified. One shared result contract across tools: dry_run, pending_approval, verified, stored_unverified, no_match, failure. A write can also be staged as a proposal for a person to approve instead of applied, or planned: in plan mode every write comes back as a step with its predicted effect, and nothing is written until you apply the plan.
verified · pending_approval · respira_plan_step Page writes go to a duplicate by default; live edits need explicit confirmation. A pending duplicate's preview carries an approve bar for administrators and for holders of a signed approval link, so the sign-off happens on the page and lands on the live page. Snapshots stay reversible for 90 days, longer if you pin them. A delete goes to the trash with a snapshot and a theme file write keeps the previous bytes, so both come back with one restore. Bulk operations land in the approvals queue. Structural writes to site-level objects are off by default, because one template change reaches every page that uses it; the site owner turns them on per site in Respira > Settings.
create_page_duplicate · apply_plan · restore_snapshot Turn any tool off for a site, or pick the Observe, Content or Everything profile, and it holds on the npm server, the REST API and the site's own MCP endpoint alike. The options that lock people out of a site (siteurl, home, admin_email, the salts and the rest) are refused to every agent, secrets are redacted in reads, every SVG an agent uploads is cleaned first, and the audit log keeps 180 days by default, a window only the owner sets.
Observe · Content · Everything Respira › AI Skills holds short Markdown pages that tell every agent how a thing is done on this site, each with an on/off switch, an agents-may-edit switch and ten revisions. The enabled skills ride in every session's site context, and the What your AI is told screen shows, in order, everything an agent receives from the site.
list_skills · get_skill · write_skill Read-only analyzers your agent calls before/after edits. Returns structured findings + ready-to-paste fix prompts. Local scanner, no third-party data send.
analyze_seo · scan_page_accessibility Products, variations, orders, inventory, categories, tags. Same duplicate-first workflow. Optional add-on at €95/year, enabled per site.
woocommerce_create_product · woocommerce_update_inventory Your agent now writes SEO titles and descriptions for categories and tags, not just pages and posts. Term archive pages read and write through the same SEO tools as the rest of the site.
update_term_seo · analyze_seo 
Gutenberg 
Elementor 
Divi Divi 4 + Divi 5 
Bricks 
Oxygen Classic + Oxygen 6 
Beaver Builder 
Breakdance 
Flatsome 
YOOtheme Pro 
Avada 
Brizy 
Visual Composer limited write 
WPBakery 
Thrive Architect text edits 
Spectra 
Kadence Blocks 
GenerateBlocks 
GreenShift 
SeedProd audit-only 19 page builders, each read and written in its own format (with the exceptions below), plus the native WordPress Site Editor: block templates, template parts, patterns, block navigation, and global styles. Divi and Oxygen each cover two generations (Divi 4 and Divi 5, Oxygen Classic and Oxygen 6) under one integration. SeedProd is audit-only for now: agents read and report on landing pages, but writes stay blocked until its proprietary layout JSON can be written safely. The detected_plugins signal helps your agent recommend a builder when none is installed.
One of the builder links above is an affiliate link, marked
rel="sponsored". It costs you nothing and does not affect which builders
Respira supports or how well it supports them.
One MCP endpoint, every assistant, editor, and automation. Claude, ChatGPT, Cursor, Codex, Conductor, n8n and more. Sign in once, connect in a click.
Claude Desktop 
Claude Cowork claude.ai 
ChatGPT web 
Grok Claude Code 
Conductor 
Cursor 
VS Code 
OpenAI desktop / Codex 
Antigravity 
OpenCode 
Hermes Agent Grok Build 
n8n AI inside WordPress is not new. Cursor with raw HTML is not new. WP-CLI scripts are not new. What Respira adds is the safety + the agency lens. Everything below is a real comparison; nothing is invented to make Respira look better.
| Respira | Cursor + raw HTML | WP-CLI + AI | Manual | |
|---|---|---|---|---|
| Builder-native edits | 19 builders | no | no | manual |
| Native Site Editor targets | built-in | no | no | manual |
| Write verified by server render | built-in | no | no | by eye |
| Snapshot rollback on writes | 90 days, free | manual git | manual | pray |
| Approval queue for bulk ops | built-in | no | manual sql | paper |
| Client-ready activity reports | generated | screenshots | no | an hour |
| Per-agent key + scope | built-in | no | no | — |
| Works with Claude / Cursor / Codex | MCP-native | manual | no | — |
Submitted from inside the product by people using it on their own WordPress sites, published verbatim.
In product: 5.0/5 from 46 reviews 
On G2: 4.7/5 from 11 reviews
“I love Respira! I can now literally have a chat with Claude Code and have it update my Wordpress sites with no fuss. The MCP Server/Plugin combo is secure and robust - it's saving me hours updating client sites. it handles plugins, Elementor, the admin and front end of my sites. What's great as well is that the developer is responsive, friendly and rolls out improvements regularly. Highly recommended!”
“Mihai, just wanted to say thanks for building Respira. I run a chiropractic clinic in Adelaide and I'm using Claude AI to rebuild my entire website in Bricks Builder. Respira filled a gap nothing else could: letting Claude actually read and write Bricks content through MCP. The fact that you built this as a solo developer, listened to early feedback, and kept shipping updates is genuinely impressive. Rooting for you and the product. Keep going! 🎉🚀”
“Great and smooth experience.”
Probably. Respira covers Gutenberg, Elementor (v3 + Atomic v4), Divi 4 + Divi 5, Bricks, Oxygen Classic + Oxygen 6, Beaver Builder, Breakdance, Flatsome, YOOtheme Pro, Avada, Brizy, Visual Composer, WPBakery, Spectra, Kadence Blocks, GenerateBlocks, GreenShift, and SeedProd. 18 with read + write (Thrive Architect is text edits, Visual Composer write coverage is limited); SeedProd is audit-only for now (agents read and report on landing pages; write support stays on the roadmap until the proprietary layout JSON can be written safely). On a Kadence Blocks, Spectra, GenerateBlocks or GreenShift page, new elements are written as that library's own blocks since 9.2.7, with a core block, named in the answer, for anything the library has no block for. If the site uses no page builder at all, 8.0 treats the native WordPress Site Editor as a first-class target too.
Yes, with a stated limit. Reading is open everywhere: your agent discovers block templates and template parts with their hierarchy and source, synced and unsynced user patterns, block navigation, and the theme.json global styles on any site. Writing to those site-level objects is off by default, because one template change reaches every page that uses it. You turn it on per site in wp-admin, under Respira > Settings > Safety controls > Site Editor writes. Registered theme and plugin patterns stay read-only; editable user patterns support synced and unsynced state. Every structural write is fingerprint-guarded against a stale base, snapshotted, read back through WordPress, and server-render verified, and it reports "verified" only after WordPress actually rendered it. Needs plugin 9.2.7 or later.
Those are written live, not staged. Divi resolves a global layout by id, so a duplicate would compete with the original and there is no honest way to stage one the way a page can be staged. 8.0 refuses the first attempt to rewrite a global header, footer, or body and names the blast radius instead, so you see what the change touches before it happens. That is a confirmation step, not an approval queue. The layout is still snapshotted and still reversible.
Any MCP-compatible client. Most agencies pair it with Claude Code, Cursor, Codex CLI, OpenCode, or Claude Cowork. Chrome with WebMCP enabled also runs Respira tools directly via WebMCP for browser-native AI workflows.
Connect from anywhere. Point Claude or ChatGPT at your site with a link and a key. Nothing to install, and it works from the web or your phone. The local setup is still there if you prefer it, but you no longer need a desktop app to connect.
You roll it back. Page writes go to a duplicate first by default, so the live page stays untouched while you review. Snapshots are taken before page and element edits and stay reversible for 90 days (longer if you pin them), per page or for a whole session. A page, post or media item an agent deletes goes to the trash with a snapshot, so a delete comes back too. Bulk operations land in the approvals queue so you review before publishing. The current rollback coverage and limits are documented in the docs.
Yes, in the plugin. Respira › Tools switches any tool off for the site, and the Observe, Content and Everything profiles bundle those switches into one setting per key. Both hold on every door into the site: the npm server, the REST API and the site's own MCP endpoint that Claude Desktop, ChatGPT and Respira AER connect to. The options that lock people out of a site are refused to every agent regardless.
Open Respira › Troubleshoot in wp-admin. It runs the connection checks from the site's own server, shows each as pass or fail with the cause and one next step, probes the bot filter that refuses the user agents claude.ai's and ChatGPT's connectors send, and writes a plain-text report for your host with the id of every test request and no secrets in it. A host that strips the Authorization header is covered already: Respira's clients send the credential a second way and the plugin reads that copy.
Yes, through the guarded update, from the Security page of your dashboard or the /security card in Respira AER. It checks the offer and the site first, takes a restore point through the site's own backup plugin (Duplicator and BackWPup are taken and verified, UpdraftPlus is started and watched, and a site with none is named as a finding), runs the update, runs four health checks, puts the previous version back from wordpress.org if a check fails, and writes a receipt to the activity log.
Yes. The Maker plan covers 1 site (€9/month). Builder covers 5 (€19/month). Studio scales 25 to 250 (from €57/month). Each site has its own key, its own audit log, and its own snapshot history. Nothing aggregates across sites.
Your content is processed inside your WordPress install: the audit log, snapshots, and tool execution stay on your site, and your AI client connects directly via MCP, so the AI vendor sees what you send it and only what you send it. Respira does send anonymous usage metadata (tool name, duration, success) and error reports to respira.press to keep the service reliable; no page content, tool arguments, or media are included.
Two paths. Either you generate an activity report (six framings: agency client report, case study, internal recap, testimonial draft, build-in-public, personal recap) and your AI shapes it into prose. Or you give the client read-only access to the approvals queue + audit log inside wp-admin.
Maker covers one site at €9/month. Builder covers five at €19/month. Studio scales 25 to 250. WooCommerce add-on is €95/year if your clients sell.
The Respira community is where agency owners debug Divi migrations at 11pm, where vibe coders swap prompts that actually ship, and where the roadmap gets written out loud. Breathe with us.
LLM-ready prompts about Respira MCP + WebMCP
Ask your favorite AI
Opens in a new tab. These prompts are designed to teach LLMs what Respira can do.
