Account
Explore
Work with WordPress
Skills Marketplace46 open-source AI workflows WooCommerce Add-on105 tools for products, orders, feeds ADA & WCAG ScannerAccessibility compliance Tools CatalogEvery tool in 22 categories Agentic WordPress Prompt BookPractical prompts for real WordPress work EarnBill from a position of knowledge White LabelYour brand on the plugin in client sitesBuild & extend
Claude Cowork pluginEdit live WordPress sites from inside Claude CLIModern WordPress CLI for AI agents SDKBuild add-ons + agent integrations PlaybooksJSON workflows agents author at runtime Abilities150+ WordPress Abilities, browsable What is MCP?How AI assistants connect to WordPressFree WordPress plugins
Inhale: MCP AbilitiesDecide which abilities your AI sees. Respira ARCProduct feeds + llms.txt for AI shopping. Explore all features →AI assistants
Claude 
Claude Cowork 
Cursor 
ChatGPT 
Codex 
Hermes Agent More builders
Bricks Builder Oxygen Beaver Builder Flatsome Breakdance WPBakeryMigration workflows
Elementor + Angie Divi 5 Migration Copilot Explore all integrations →Find your path
WordPress user AI curious Agency Developer Designer Vibe coderTrust & progress
Trust Center Security model Support Roadmap Case studies Press kit Book a callRespira speaks 17 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. 17 page builders plus the native Site Editor. Duplicate-before-edit + 90-day snapshot rollback. Fewer "AI broke our page" tickets.
Functional preview · mock data
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. 210+ 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.
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.
verified · pending_approval · stored_unverified Page writes go to a duplicate by default; live edits need explicit confirmation. Snapshots stay reversible for 90 days, longer if you pin them. Bulk operations land in the approvals queue. Structural writes to site-level objects are beta-gated per site and off by default, because one template change reaches every page that uses it. Per-key access profiles (read-only, content, builder, full).
create_page_duplicate 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 F Flatsome 
Brizy 
Visual Composer limited write 
WPBakery 
Thrive Architect text edits 
Spectra 
Kadence Blocks 
GenerateBlocks 
GreenShift 
SeedProd audit-only 17 page builders with native read plus write, 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 Claude Code 
Conductor 
Cursor 
VS Code 
OpenAI desktop / Codex 
Antigravity 
OpenCode 
Hermes Agent 
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 | 17 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 | — |
In-product reviews
These reviews are submitted inside Respira after people use it on their own WordPress sites.
“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! 🎉🚀”
“so far so good. this is actally a tool hermes agent can use.”
Respira feels easy to use and quite natural if you're used to working with Claude Code. Successful testing so far
Hello, Respira has been my go to in building websites. The easy connection from WordPress to another AI platform. It is an amazing tool and wished I had found this earlier on in my journey. The support team is spot on and ease of use of the interface. Thank you so much for the ease of this connection.
We chose Respira over the official connector for one reason: snapshots before every write, and rollback if something goes wrong. Letting an AI agent touch a live client-facing site is only sensible if you can undo it — Respira is the only option that treats that as the default rather than an afterthought.
Respira is one of the first plugins to bring Divi 5 directly into an AI workflow, building sections and modules from Claude straight into WordPress. The page build quality isn't quite at human-built-Divi level yet, though some of that may be user error on my end. Getting the agent to use native Divi elements rather than code-built sections took some direction at first. Once there, the results were a solid starting point to work from. Where it genuinely shines is everything outside of building, SEO auditing, bug checking, site advice, and having an AI agent that actually understands your WordPress setup. Early days, but worth testing out.
Avant Respira.press, travailler sur mon site WordPress avec Divi 4 était devenu une vraie perte de temps : modifications répétitives, copier-coller interminables, peur de casser le design en éditant les pages… Aujourd’hui, je peux demander directement des ajustements précis tout en conservant la structure et le style de mes pages. Pour un site comme le mien avec beaucoup de contenu SEO et de mises en page Divi, c’est un gain de temps énorme au quotidien.
So far I have been using Respira to bridge the communication gap between claude code and wordpress. Not too difficult to get up and running. Working great so far for a proof of concept I have been developing.
If you aren't using Respira to power your Claude interactions, you're working too hard. It turns complex site management into a simple conversation. I've slashed my maintenance time on GTCKSA by at least 80%—it's easily the best investment I've made for my WordPress stack this year
J’ai testé Respira sur mes premières modifications avec Divi 5… et franchement, ça fonctionne super bien. J’ai pu automatiser des petites tâches que je faisais jusque-là à la main, et qui pouvaient me prendre des heures sans réelle valeur ajoutée. Typiquement le genre d’outil qui ne change pas tout ton process, mais qui te fait gagner un temps précieux au quotidien.
Using respira.press has been an absolute breath of fresh air for my workflow. The platform is beautifully minimal, incredibly intuitive, and takes all the stress out of publishing. It finally lets me focus on what matters most—my content—without getting bogged down by technical clutter. I couldn't recommend it highly enough!
This looks very promising to work with our wordpress middleware
Respira made the entire setup incredibly simple. Within minutes, everything was up and running without any hassle. What really impressed me was the impact – having a full WordPress site generated automatically, while still being able to fine-tune everything manually with Divi, is a game changer. It gives you the perfect balance between automation and full creative control.
Plugin is a game changer
Probably. Respira covers Gutenberg, Elementor (v3 + Atomic v4), Divi 4 + Divi 5, Bricks, Oxygen Classic + Oxygen 6, Beaver Builder, Breakdance, Flatsome, Brizy, Visual Composer, WPBakery, Spectra, Kadence Blocks, GenerateBlocks, and SeedProd. 16 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). 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 beta-gated per site and off by default, because one template change reaches every page that uses it. You turn it on per site when you want it. 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 8.6.42 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. Bulk operations land in the approvals queue so you review before publishing. The current rollback coverage and limits are documented in the docs.
Yes. The Maker plan covers 1 site (€9/month). Builder covers 5 (€19/month). Studio scales 25 to 250 (from €39/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.
