Elementor
Full IntelligenceNative widget access. 8 dedicated tools. Drop a section, swap a button, refresh the design system in one call.
Read the deep-dive Respira 7.0.51 MCP Server 6.18.6 172 tools
WordPress MCP with
page-builder superpowers
For production teams
Respira for WordPress is an MCP execution layer for real sites. 172 MCP tools — builder-aware tooling, WooCommerce operations,
and approval-mediated publish flow. Install in one command with add-mcp, run
--doctor to verify the connection.
Official WordPress MCP gives AI core access. Respira gives it page-builder superpowers with Full Intelligence for 6 builders (Elementor, Divi, Gutenberg, Bricks, Flatsome, Oxygen) and Smart Defaults for 5 more — with duplicate-before-edit safety so nothing ever breaks. Works on any hosting.
One-click install Pre-configured with every site on your account. Sign in and install in ten seconds.
Claude Desktop
Download the .mcpb bundle. Double-click to install.
Cursor
Opens Cursor and drops in the Respira MCP server for you.
One command Auto-detects your AI tool (Claude Code, Cursor, Windsurf, Codex, and 9+ more) and writes the correct config.
npx add-mcp "npx -y @respira/wordpress-mcp-server"Other installation methods
Interactive wizard
Step-by-step setup with connection testing.
npx @respira/wordpress-mcp-server --setup Manual JSON
Paste into your client's MCP config.
{
"mcpServers": {
"respira-wordpress": {
"command": "npx",
"args": ["-y", "@respira/wordpress-mcp-server"],
"env": {
"WORDPRESS_URL": "https://yoursite.com",
"WORDPRESS_API_KEY": "respira_your_api_key"
}
}
}
} Health check
npx @respira/wordpress-mcp-server --doctor9 diagnostic checks — Node.js, config, connectivity, plugin version, compatibility, and updates.
136+36 Desktop MCP 172 total tools with WooCommerce
85+36 WebMCP abilities 121 ability tools incl. v2 shortcuts
12 Builders Elementor, Divi, Bricks, and more
v6.18.6 MCP Server SOUL.md agent persona + search_docs + report_issue
Twelve builders, one server
WordPress is not one product.
It is a hub for a dozen page builders.
Every page builder stores "edit the hero section" differently. Elementor uses widget JSON. Divi 4 uses nested shortcodes. Divi 5 uses a new module system. Bricks has its own renderer. The same prompt has to be translated twelve different ways for the same outcome. Respira speaks every format natively, so the prompt stays the same regardless of which builder runs the site.
Deep Intelligence Full Intelligence Smart Defaults
Divi (Divi 4 + Divi 5 / Divi5 MCP)
Full IntelligenceBoth Divi 4 shortcodes and Divi 5 JSON. 200+ modules cataloged. Presets and global modules first-class.
Read the deep-diveBricks
Deep Intelligence20 specialised tools, ACSS-aware, cross-site element search. The deepest single-builder support Respira ships.
Read the deep-diveWPBakery
Smart DefaultsShortcode-aware reads and writes. Inline schemas pulled from the site before injection so nothing breaks.
Read the deep-diveGutenberg
Full IntelligenceBlock-native edits with schema for every registered block. Full Site Editing supported.
Read the deep-diveOxygen
Full Intelligence49 components cataloged. Oxygen Classic 4.x and Oxygen 6 detected automatically.
Beaver Builder
Smart DefaultsModule-level reads and writes. Font fields normalized so style fields never reset to theme defaults.
Brizy
Smart DefaultsStructure-preserving edits that keep the builder hierarchy intact through every update.
Visual Composer
Smart DefaultsSame shortcode treatment as WPBakery, with Visual Composer's newer schema bindings.
Thrive Architect
Smart DefaultsConversion-page edits without manual rebuilds. Useful for ongoing CRO iteration.
Breakdance
Smart DefaultsBuilder-aware reads and controlled section refreshes on component-heavy pages.
Flatsome
Full Intelligence55 element definitions. ThemeForest's #1 WooCommerce theme treated like a first-class builder.
Read the deep-dive Same safety workflow on every builder. The agent duplicates the page before editing. You approve the change before it goes live. Snapshots roll any edit back in one click. The builder you happen to be running does not change any of those rules.
Respira for WordPress is not officially affiliated with Elementor, Divi, Bricks, WPBakery, Gutenberg, Oxygen, Beaver Builder, Brizy, Visual Composer, Thrive Architect, Breakdance, Flatsome. All trademarks and product names belong to their respective owners.
New in v6.17 An MCP that knows
An MCP that knows
how to behave.
Every agent that connects to Respira reads SOUL.md before its first tool call. Identity, voice, values, rules. When something goes wrong, the agent does not panic and does not invent: it follows a five-step triage that ends at "ask the customer if they want to file a bug." Not before, not after.
The persona
SOUL.md
Loaded into the handshake so the agent reads it before any tool call. Lowercase i in first person. No "we." No em dashes. No phone-call offers. No customer names in changelogs. Builder-native edits only. Privacy is a hard line. Try yourself before asking the customer.
- Beautiful, accurate, fast. In that order.
- Ship the smallest correct change.
- Respect every token.
The first probe
respira_search_docs
Before offering to file a bug, the agent searches the Respira documentation. Most "bugs" are documented known issues with workarounds: Cloudflare allowlists, builder gotchas, the rest_route fallback, Divi 5 preset 404s. One read instead of one ticket.
- Postgres full-text search over the live docs repo
- Refreshed nightly
- Public, unauthenticated, free to call
The escalation
respira_report_issue
When docs and diagnose come up empty, the agent asks you. If you say yes, it files a structured bug from inside the chat with site URL, builder, MCP version, OS, and the diagnose snapshot auto-attached. The maintainer gets an email immediately.
- Privacy: no prompts, no args, no results, no WP content
- You own the decision to file
- Track status at /dashboard/bug-reports
The triage rule, baked into the handshake
- 1Tool errors → apply the structured hint, retry once.
- 2Same error →
respira_search_docs(likely already documented). - 3Docs do not cover →
respira_diagnose_connection. - 4Diagnose unclear → ask the customer if they want to file a bug.
- 5Customer says yes →
respira_report_issuewith full context.
Intelligence Levels
Full Intelligence vs Smart Defaults
Full Intelligence means component registries, JSON Schema generation, settings validators, and layout patterns. Smart Defaults means per-builder format preservation with tree-based element operations.
Full Elementor
9 dedicated tools, widget schemas, conversion validator, design system, global colors/typography.
Full Bricks
20 dedicated tools, ACSS integration, query loops, design system export.
Full Divi 5 + 4
Module registry, JSON + shortcode formats, 13-point validation.
Full Gutenberg
Block registry, simplified + native format, FSE support.
Full Breakdance
84 elements, nesting validation, fuzzy matching, 8 patterns.
Full Oxygen
49 components, fuzzy validation, data repair, Oxygen 6 detection.
Full Flatsome
Shortcode intelligence, auto section/row/col wrapping.
Smart Beaver Builder
Smart WPBakery
Smart Brizy
Smart Visual Composer
Smart Thrive Architect
Fidelity
Builder fidelity: clean extraction + lossless source
Respira can return a clean extraction view for AI tasks, then keep the original builder source intact for safe writes. That gives you readable context and layout fidelity in the same workflow.
Clean extraction for AI context
Use normalized content views for text, assets, and structure checks when you need concise context.
Lossless round-trips for builder source
Respira preserves source payloads such as Elementor JSON/meta and Divi structures so edits do not collapse page layouts.
Duplicate-first safety in both modes
Reads can be lightweight, but writes still follow duplicate-before-edit, then approval before live publish.
Positioning
Respira MCP vs Official WordPress MCP
Both matter. Official WordPress MCP provides core protocol access; Respira layers in builder and safety behavior for production operations.
Official WordPress MCP
Respira for WordPress MCP
Core WordPress entities and adapter-level discovery.
Builder-aware tools across 12 page builders with context-aware filtering.
Protocol and registration baseline.
Duplicate-before-edit with explicit approval mediation.
Typed DTOs + protocol version negotiation (2025-06-18 spec).
structuredContent in all tool results + improved error taxonomy for LLM self-correction.
Generic runtime capabilities.
Snapshot and fidelity-aware workflows for safer rollouts.
Foundational server path.
WooCommerce CRUD extensions plus audit-oriented operations.
Browser MCP Context
WebMCP is the browser protocol. Respira makes it production-safe for WordPress.
WebMCP covers browser-side discovery and invocation. Respira adds approval gates and fidelity-aware write behavior so teams can ship safely, not just quickly.
Chrome runtime
Live in Chrome 146+ with Experimental WebMCP enabled.
SourceCross-vendor editors
Current draft includes editors from Google and Microsoft.
SourceCommunity report
Published as a Web Machine Learning Community Group draft.
SourceOpen specification
Spec text and issue history are public on GitHub.
SourceRespira safety contract
Duplicate-first writes, approvals, snapshots, and rollback.
Source Discover tools in browser AI clients Keep approvals and rollback before publish Run one safety model across WebMCP and desktop MCP
Trusted by professionals
People shipping WordPress faster, without breaking live sites
Reviews are submitted by real users inside Respira for WordPress right after successful sessions.
Verified Reviews
32Average Rating
5.0/5Collection
In-product“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”
“This looks very promising to work with our wordpress middleware”
“claude + respira = POWER!”
“Respira hat die Art, wie ich mit WordPress arbeite, grundlegend verändert. Als MCP-Server integriert es sich nahtlos in Claude Code und bietet über 170 Tools, die praktisch jeden Aspekt einer WordPress-Site abdecken — von Content-Management über Bricks Builder bis hin zu WooCommerce. Was mich überzeugt: Umfassende Tool-Abdeckung: Seiten, Posts, Menüs, Medien, Benutzer, Plugins, Custom Post Types, Taxonomien — alles steuerbar über eine einheitliche Schnittstelle. Bricks Builder Support: Elemente finden, bearbeiten, verschieben und duplizieren funktioniert zuverlässig. Die find_element- und batch_update-Funktionen sparen enorm viel Zeit. Sicherheit durch Snapshots: Vor jeder Änderung kann ein Snapshot erstellt werden. Das gibt Sicherheit, besonders bei umfangreichen Umbauten. SEO & Accessibility: Eingebaute Analyse-Tools für SEO, Barrierefreiheit und Performance — direkt nutzbar, ohne zusätzliche Plugins. Kein direkter DB-Zugriff nötig: Alles läuft über die API, was das Risiko von Fehlern deutlich reduziert. Kleiner Verbesserungswunsch: Die Dokumentation könnte an einigen Stellen ausführlicher sein, besonders für fortgeschrittene Bricks-Builder-Workflows. Fazit: Wer WordPress-Seiten mit KI-Unterstützung verwalten und automatisieren möchte, kommt an Respira kaum vorbei. Es ist ausgereift, stabil und macht komplexe Aufgaben überraschend einfach.”
“Great tool to help automation and integrating AI with wordpress, with claude code it's really powerful and a complete new way to work with wordpress.”
“Still learning how powerful this plugin is, but so far a game changer for me and website development. Highly recommended.”
“Respira has been great! Now allows me to vibe code out tedious tasks on wordpress immediately.”
“Best app ever”
“Just discovered @Respira_cafe - Respira for WordPress! A safety layer for AI coding assistants that creates duplicates before any edits. Review before anything goes live. Perfect for WordPress developers! 🚀”
“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! 🎉🚀”
“This is fxxxxxg amazing! I had to upload 14 PDFs and find a way to show them on a complex page build more than 1 year ago on a WordPress site with a theme that is using WP Backery. I linked Cursor (auto-mode) to my site with this plugin and it uploaded the PDFs to Media Library (it asked me for an application password but that was easy) and created a stunning section (in a similar style with the other sections on the page) with a preview panel and all the PDFs displayed nicely and when somebody clicks a PDF it loads in the panel without opening a new tab. Everything took about 15 minutes in total. I did not even know how to do that myself, not to mention that just uploading the PDFs and putting them on the page would have take me at 3 hours and the result would have been a lot worse.”
“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.”
“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.”
“I have been using respira for only 3 days and i am amazed about how fast it help me finish projects, usually i finish a single project in 2 weeks at least , now within 2 to 3 days i finish and deploy my project.”
“Respira hat die Art, wie ich mit WordPress arbeite, grundlegend verändert. Als MCP-Server integriert es sich nahtlos in Claude Code und bietet über 170 Tools, die praktisch jeden Aspekt einer WordPress-Site abdecken — von Content-Management über Bricks Builder bis hin zu WooCommerce. Was mich überzeugt: Umfassende Tool-Abdeckung: Seiten, Posts, Menüs, Medien, Benutzer, Plugins, Custom Post Types, Taxonomien — alles steuerbar über eine einheitliche Schnittstelle. Bricks Builder Support: Elemente finden, bearbeiten, verschieben und duplizieren funktioniert zuverlässig. Die find_element- und batch_update-Funktionen sparen enorm viel Zeit. Sicherheit durch Snapshots: Vor jeder Änderung kann ein Snapshot erstellt werden. Das gibt Sicherheit, besonders bei umfangreichen Umbauten. SEO & Accessibility: Eingebaute Analyse-Tools für SEO, Barrierefreiheit und Performance — direkt nutzbar, ohne zusätzliche Plugins. Kein direkter DB-Zugriff nötig: Alles läuft über die API, was das Risiko von Fehlern deutlich reduziert. Kleiner Verbesserungswunsch: Die Dokumentation könnte an einigen Stellen ausführlicher sein, besonders für fortgeschrittene Bricks-Builder-Workflows. Fazit: Wer WordPress-Seiten mit KI-Unterstützung verwalten und automatisieren möchte, kommt an Respira kaum vorbei. Es ist ausgereift, stabil und macht komplexe Aufgaben überraschend einfach.”
“Honestly, I was a bit worried about how it would handle Divi v4 because those layouts can be touchy, but it works like a charm. With Divi v5 coming out, this is going to be a total game changer for our workflow. It actually understands the modules instead of just breaking everything.”
“I'm very happy with the time passed on this with you. I am very curious to get more time with it and get more aspect done. Excellent job done behind this technology. thank you”
“I just started using Respira for WordPress and I’m already impressed by how intuitive the interface is. It’s rare to find a tool that feels this clean and 'out of the way' while still providing the power I need to manage my site effectively. Looking forward to seeing what else it can do!”
“still testing this but i can see potential”
“"I run two websites on FLAVOR.PRESS and have been really impressed with how seamlessly it integrates with Claude Code. The workflow just works – I can manage both sites efficiently, and the combination of FLAVOR.PRESS's platform with Claude's capabilities has made my day-to-day so much smoother. It's one of those tools where everything clicks into place from the start. Highly recommended for anyone looking for a reliable, developer-friendly setup."”
“I've been searching for exactly this solution for months – and then I found Respira. What truly amazes me: it doesn't just do what you expect, it actually thinks along with you. For my work with mysolarplant.de, this is a real game changer.”
“This plugin definitely has a WOW factor. After helping me change slugs and adding new hero to multiple pages in one prompt in a couple of minutes, i have to say that editing my client's wordpress sites will never be the same. thank god for good tech!”
“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!”
“Plugin is a game changer”
“I've been testing Respira extensively over the past week, combining it with different page builders to explore what's possible for my web design workflow. My experience with Bricks Builder was genuinely impressive, the integration worked smoothly and opened up exactly the kind of AI-assisted editing I was hoping for. Being able to read and update page content directly through Claude is a game changer for the way I work with clients. With Brizy, things didn't work yet, we ran into a consistent PHP error in the Brizy integration that prevented any content from being read or edited. However, what happened next is what really stands out: I submitted a detailed bug report, and within the same day or the next, an update was already released addressing the issue. That kind of responsiveness is rare and genuinely impressive. We're still working through the Brizy integration, but I have every confidence it will get there, because this team clearly takes feedback seriously and moves fast.”
“I like how much this empowers my ai agents to help me build wordpress sites which have usually been difficult for ai agents to build without issues when using plugins like elementor”
“AI automations has never been easier”
“To be honest, I've been trying to find a workaround for AI with WordPress. A lot of it is tedious and really, really difficult. now that I have this, I want to build websites, but I don't want to go through all the clicking of the Divi modules and everything. It is too tedious, and I want to focus on my work in sales. However, having a good website out there really helps with my sales process. The notion of me as a salesperson going through that technical setup is really daunting, even when there is no coding required for Divi. Now that I have this, it's just amazing. It's like everything I wanted in a website, and it's being coded into Divi. So far, it looks good. :)”
“Honestly i am blown away. Respira is a major game changer Wordpress website management, especially for SEO.”
“I was able to connect with my claude code, very nice”
“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!”
“ALHUMDULILLAH great experience”
Every review shown here was submitted by a real Respira for WordPress user in-product.
Execution paths
Same workflow, two runtimes
Desktop MCP (CLI/editor)
Runs through the npm server package and connects assistants like Claude Code, Cursor, Windsurf, Codex, and other MCP-compatible clients.
- Use
npx -y @respira/wordpress-mcp-serverin your client config - Negotiates
respira/v2when available, clean fallback torespira/v1 - Aligned with MCP 2025-06-18 spec:
structuredContentin all tool results for programmatic access - Aligned with MCP Adapter
v0.5.0server registration + transport permission model - Tool inventory sourced from
mcp-server/src/server.ts
Browser AI (WebMCP)
Built into Respira for WordPress and exposed through WordPress Abilities/MCP Adapter. No second browser bridge plugin is required.
- Chrome 146+ with
Experimental WebMCPenabled - Ability IDs are rebased as
respira/<tool-name> - Tool inventory sourced from plugin WebMCP registry
Accuracy ledger
Tool inventory by surface
Numbers below are generated from source files at build time, not hand-typed marketing claims.
| Surface | WordPress Tools | Woo Tools | Total When Woo Active | Source of Truth |
|---|---|---|---|---|
| Desktop MCP server | 136 | 36 (conditional) | 172 | mcp-server/src/server.ts |
| WebMCP / Abilities | 85 | 36 (conditional) | 121 | class-respira-webmcp-integration.php |
WebMCP currently exposes 0 plugin-side shortcuts not present as separate desktop tool IDs:
none
Desktop catalog
What the desktop MCP server actually exposes
WooCommerce add-on tools (36)
These register only when WooCommerce add-on is both installed and licensed:
woocommerce_list_productswoocommerce_get_productwoocommerce_create_productwoocommerce_update_productwoocommerce_duplicate_productwoocommerce_list_orderswoocommerce_get_orderwoocommerce_update_order_statuswoocommerce_get_stock_statuswoocommerce_update_stockwoocommerce_sales_reportwoocommerce_list_categorieswoocommerce_get_categorywoocommerce_create_categorywoocommerce_update_categorywoocommerce_delete_categorywoocommerce_list_tagswoocommerce_get_tagwoocommerce_create_tagwoocommerce_update_tagwoocommerce_delete_tag Commerce
WooCommerce MCP
Respira extends WordPress MCP with WooCommerce operations for stores and agencies that manage product updates through AI assistants.
Current CRUD coverage
- Products: list, read, create, update, duplicate
- Orders: list, read, and status updates
- Stock operations: stock status + inventory updates
- Taxonomies: category and tag CRUD tools
Why this matters for teams
- Run catalog refreshes without touching live originals directly.
- Keep approved Woo product edits on the same live product ID for ad/catalog sync stability.
- Keep one approval model across pages, posts, and commerce tasks.
- Coordinate store edits from desktop MCP or browser WebMCP paths.
- Audit all operations through the same Respira safety contract.
WordPress AI infrastructure
Abilities + MCP Adapter + WebMCP
Ability IDs
Respira registers tools as WordPress abilities and rebases IDs to kebab-case:
respira/wordpress-list-pagesrespira/wordpress-apply-builder-patch Discovery endpoints
/wp-json/wp-abilities/v1/abilities /wp-json/mcp-adapter/v1/servers If both are present, Respira abilities are discoverable through the official adapter path and browser WebMCP.
Surface behavior
Desktop MCP and WebMCP share the same duplicate-before-edit and approval semantics. The browser path adds WordPress-native ability discovery.
Generic MCP server config snippet
{
"mcpServers": {
"respira-wordpress": {
"command": "npx",
"args": ["-y", "@respira/wordpress-mcp-server"],
"env": {
"WORDPRESS_URL": "https://yoursite.com",
"WORDPRESS_API_KEY": "respira_your_api_key"
}
}
}
}New in v6.0
Context-aware tool filtering
The MCP server automatically detects your site's active builder and plugins, then filters the tool list to show only what's relevant. A Divi site without WooCommerce sees ~130 tools instead of ~170. Less noise, faster AI responses, lower token usage.
All tools ~170
Divi (no Woo) ~130
Elementor + Woo ~150
Fail-open design. If context detection fails, the full tool list is returned. No tools are ever permanently hidden.
Context is cached for 1 minute and invalidated on site switch. Requires MCP server v6.0.0+.
Configuration
Hit a tool limit?
Some MCP clients enforce a hard cap on active tools — Antigravity limits you to 100, others vary.
Respira ships 172+ tools but context-aware filtering reduces this automatically.
Add enabledTools to your config to further limit the exposed tools.
~/.respira/config.json
{
"sites": [{ "..." : "..." }],
"preferences": {
"enabledTools": [
"respira_read_page",
"respira_update_page",
"respira_list_pages",
"respira_find_element",
"respira_update_element",
"respira_build_page",
"respira_get_site_context",
"respira_get_builder_info"
]
}
}Site management tools are always included. Unlisted tools still work if called — the filter only controls what your client sees. Requires MCP server v5.2.3+.
FAQ
Common WordPress MCP questions
Is there an Elementor MCP server?
Yes. Respira acts as an Elementor MCP server with builder-aware reads, safe duplicate-first writes, and approval before publish.
Is there a Divi 5 (Divi5) MCP server?
Yes. Respira supports Divi 4 and Divi 5 structures and keeps updates inside duplicate-before-edit approval flows.
Is there an MCP server for Bricks, WPBakery, or Gutenberg?
Yes. Respira covers Bricks MCP, WPBakery MCP, Gutenberg MCP, and other supported builders through one consistent MCP safety model.
Does Respira work with Claude Desktop, Claude Code, Cursor, and Codex?
Yes. The desktop MCP server works with MCP-compatible clients, and browser AI paths can use WebMCP through WordPress abilities.
Do I need my WordPress site publicly accessible?
Your MCP client must reach the site URL and authenticate with a Respira API key. Public internet exposure is not required when your network provides secure access.
Can MCP edit WooCommerce products?
Yes. Respira WooCommerce MCP tools cover product CRUD, order and stock operations, and taxonomy flows for categories and tags. Product approvals keep the original live product ID stable so Meta Catalog and Google Merchant Center mappings do not break.
What does duplicate-before-edit mean?
Respira edits a duplicate first, then you review and approve before anything goes live. The original remains untouched until approval.
How is Respira different from official WordPress MCP?
Official WordPress MCP gives AI core access. Respira gives it page-builder superpowers with Full Intelligence for 6 builders (Elementor, Divi, Gutenberg, Bricks, Flatsome, Oxygen) and Smart Defaults for 5 more — with duplicate-before-edit safety so nothing ever breaks. Works on any hosting.
How does Respira preserve builder fidelity?
Respira can return a clean extraction view for AI tasks while preserving lossless builder source for round-trips, so layouts remain stable after edits.
What is the difference between desktop MCP and WebMCP?
Desktop MCP runs through the npm server in your editor or CLI. WebMCP runs in browser AI paths through WordPress abilities and MCP Adapter.
How do I connect WordPress to MCP quickly?
Run npx add-mcp "npx -y @respira/wordpress-mcp-server", add your site URL and API key, then verify read access before your first duplicate edit.
My MCP client has a tool limit (e.g. 100 tools in Antigravity). What do I do?
As of v6.0, Respira automatically filters tools based on your site's detected builder and plugins (context-aware filtering). A typical site sees ~130 tools instead of ~170. If you still hit a limit, add an enabledTools array to your ~/.respira/config.json under preferences to further limit the exposed tools. Site management tools are always included automatically.
Discovery
Listed on
Find Respira in every major MCP directory and package registry.
Single next step
Connect your assistant and run a safe first edit
Start with the setup command, verify connection, then ask your assistant to read context, duplicate a page, and edit only the duplicate.
