Claude
Claude Cowork
Cursor
ChatGPT
Codex
Hermes Agent
Elementor
Full IntelligenceNative widget access. 8 dedicated tools. Drop a section, swap a button, refresh the design system in one call.
Elementor MCP guide Respira 8.6.42 MCP Server 8.3.8 320+ tools
WordPress MCP with
page-builder superpowers
An MCP execution layer for real WordPress sites. 320+ builder-aware tools across 17 page builders plus the native Site Editor, duplicate-before-edit safety, and approval-gated publishing. Install in one command.
One-click install Pre-configured with every site on your account. Sign in and install in ten seconds.
Claude Desktop
Connect by URL with a browser sign-in. No key, no file. Or download the .mcpb bundle. Guide.
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.
Three ways to connect
Connect any AI app to your WordPress site.
Same site, same tools. Pick the method your app supports. The first one needs no API key and no file.
New · no key, no file
Browser sign-in (OAuth)
Add your site as a custom connector by URL. Approve access once in your browser. Nothing to paste, nothing to download. Disconnect anytime from your dashboard.
Works with Claude Desktop, claude.ai, Claude Code, ChatGPT web in Developer mode, Cursor, OpenAI desktop, Codex, and Hermes.
In ChatGPT web: turn on Settings → Apps → Advanced settings → Developer mode, return to Apps, choose Create, and paste the link as the Server URL. Set Authentication to OAuth, choose Create, then sign in to Respira and approve. In OpenAI desktop or Codex, run the two dashboard commands: codex mcp add, then codex mcp login. Custom MCP apps are not available in the ChatGPT mobile apps yet.
Any remote client
Remote URL + API key
Point any MCP client at the same site URL with your key in an Authorization header. For clients that support remote servers but haven't shipped OAuth yet.
Config-file clients
Local install (one command)
One npx command writes the config for Cursor, Codex, OpenCode, Antigravity, Windsurf, Hermes, and more. Runs the bridge on your machine.
Every tool you already use
One server.
Every assistant, editor, and automation you already work in.
If it speaks MCP, it speaks Respira. Come in through the chat app on your desktop, the editor in your terminal, or your automation platform. Same site, same tools, same duplicate-before-edit safety, whichever door you pick.
Apps & web
Claude Desktop the app on your computer
one-clickbrowser link tools only
Claude Cowork New one file for all your sites
config file full plugin
claude.ai claude.ai in your browser
browser link tools only
ChatGPT web New chatgpt.com in a desktop browser
browser link
ChatGPT mobile
iPhone, iPad, and Android
Chat & team channels
Slack / Microsoft Teams New
via Viktor, your AI coworker in chat
browser link
Coding tools
Claude Code in your terminal
one commandconfig file full plugin
Conductor Claude Code or Codex, in Conductor
one commandconfig file full plugin
Cursor the coding editor
one-clickconfig file
VS Code New the code editor
one-clickconfig file
Continue New
the open-source extension in VS Code or JetBrains
config file
OpenAI desktop / Codex New desktop app, CLI, or editor
one command
Antigravity New the AI browser
config fileone command
OpenCode New open-source coding tool
config fileone command
Hermes Agent New the open-source agent from Nous Research
one-clickconfig fileone command
Automation & other
n8n the automation platform
config file
Other tool
any MCP client
config fileone command
Already signed in? Open your setup page for one-click connect per site, with your key and access scope prefilled.
214+105 Desktop MCP 319 total tools with WooCommerce
172+105 WebMCP abilities 277 ability tools incl. v2 shortcuts
17 Builders Elementor, Divi, Bricks, plus the native Site Editor
v8.3.8 MCP Server Site Editor and design-token tools, Woo reporting, published tool catalog
Seventeen builders and the Site Editor, one server
WordPress is not one product.
It is a hub for a dozen page builders and more.
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 17 different ways for the same outcome. Respira speaks every format natively, so the prompt stays the same regardless of which builder runs the site. Since 8.0 that includes the sites running no page builder at all: the native Site Editor is a target of its own, with block templates, template parts, patterns, block navigation, and global styles.
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.
Divi MCP (Divi 4 + Divi 5 / Divi5 MCP) guideBricks
Deep Intelligence20 specialised tools, ACSS-aware, cross-site element search. The deepest single-builder support Respira ships.
Bricks MCP guideWPBakery
Smart DefaultsShortcode-aware reads and writes. Inline schemas pulled from the site before injection so nothing breaks.
WPBakery MCP guideGutenberg
Full IntelligenceBlock-native edits with schema for every registered block, plus the native Site Editor: templates, template parts, patterns, navigation, and global styles.
Gutenberg MCP guideOxygen
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.
Flatsome MCP guide 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. Structural writes go further: fingerprint-guarded against a stale base, read back through WordPress, and server-render verified before they report success. Every audit entry links to its snapshot, proposal, approval, or rollback, and your agent can read that history back. 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, Spectra, Kadence Blocks, GenerateBlocks, GreenShift, SeedProd. All trademarks and product names belong to their respective owners.
Agent posture 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, native format, Site Editor templates, patterns, navigation, and global styles.
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 page 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 17 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.
Core entity coverage.
Native Site Editor targets: block templates, template parts, patterns, block navigation, and theme.json design tokens.
Generic write path.
Structural writes are fingerprint-guarded, snapshotted, read back through WordPress, and server-render verified. One result contract: dry_run, pending_approval, verified, stored_unverified, no_match, failure.
Foundational server path.
WooCommerce CRUD extensions, bounded revenue and order reporting, 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 with the WebMCP flag 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
In-product reviews
Built in public. Judged after real work.
These reviews are submitted inside Respira after people use it on their own WordPress sites.
- Verified reviews
- 38
- Average rating
- 5.0/5
- Collected
- In product
“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
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 with WebMCP enabled with
Experimental WebMCPenabled - Ability IDs are rebased as
respira/<tool-name> - Tool inventory sourced from plugin WebMCP registry
How to ask
Great results start with how you prompt
Most disappointing results are a prompting gap, not a bug. One habit fixes the rest: prime the assistant first so it reads your builder and edits through native modules instead of raw HTML.
Prime first (paste once per session)
Before doing anything, detect my page builder and read my site, then follow Respira's safe workflow: edit through the builder's native modules, never raw HTML, and duplicate a page before changing it live.
Build a section
Add a 3-column features section below my homepage hero using my page builder's native modules, not an HTML block. Keep it on-brand with the existing page.
Audit first
Audit this site with Respira: check the builder, list my pages, and give me the top 5 improvements for clarity and conversions. Don't change anything yet.
Accuracy ledger
Tool inventory by surface
Numbers below are generated from source files at build time, not hand-typed marketing claims. 210+ tools and abilities come with every core plan; the WooCommerce surface is the paid add-on on top.
| Surface | WordPress Tools | Woo Tools | Total When Woo Active | Source of Truth |
|---|---|---|---|---|
| Desktop MCP server | 214 | 105 (conditional) | 319 | mcp-server/src/server.ts |
| WebMCP / Abilities | 172 | 105 (conditional) | 277 | class-respira-webmcp-integration.php |
WebMCP currently exposes 0 plugin-side shortcuts not present as separate desktop tool IDs:
none
8.0 publishes the same inventory for machines: a tool catalog and a machine-readable capability manifest, so an agent can ask what this server can do before it calls anything. Browse the catalog →
Desktop catalog
What the desktop MCP server actually exposes
WooCommerce add-on tools (105)
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
New in 8.0: reporting and configuration
- Revenue and time-series reporting, bounded so a question cannot pull the whole order table.
- Top-product, order, and customer reporting on the same bounds.
- Store configuration discovery: payment gateways, shipping zones, tax rates. Read-only.
- Webhook management, approval-gated, because a webhook change is a change to a live integration.
- Needs the WooCommerce add-on at 4.0.4 or later, on plugin 8.6.42 or later.
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 a filtered subset per site, out of 319 total. Less noise, faster AI responses, lower token usage.
Everything registered, Woo add-on active 319
WordPress site, no Woo add-on 214
After context-aware filtering a subset per site
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 319 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.
Can MCP edit the native WordPress Site Editor (FSE)?
Yes, in 8.0, with a stated limit. Block templates and template parts with their hierarchy and source, synced and unsynced user patterns, block navigation edited by exact block path, and theme.json design tokens are all addressable. Registered theme and plugin patterns stay read-only. 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. Read-only discovery works everywhere.
How does Respira know a structural write actually worked?
It checks. 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 rendered it. Tools answer on one shared contract: 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.
What versions does the 8.0 tool set need?
The Site Editor and design-token tools need Respira for WordPress 8.6.42 or later on the site. WooCommerce reporting, store configuration discovery, and webhook management need the WooCommerce add-on at 4.0.4 or later.
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 be able to reach the site URL. Remote OAuth connections need a valid HTTPS address; local API-key connections can also work over a private network that your client can reach.
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 across 17 builders, with Deep or Full Intelligence on Elementor, Divi, Bricks, Gutenberg, Oxygen, and Flatsome, and native read plus write on the rest. Version 8.0 "Canopy" adds the native WordPress Site Editor as a first-class target: block templates and template parts with hierarchy and source discovery, synced and unsynced patterns, block navigation edited by exact block path, and theme.json design tokens. Structural writes to site-level objects are beta-gated per site and off by default; read-only discovery works everywhere. Playbooks, agent-creatable custom post types and ACF field groups, and a native in-WP endpoint you can connect to directly are all in there too. Duplicate-before-edit safety so nothing ever breaks, 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?
Open the Respira MCP Setup page and choose your AI surface. ChatGPT web uses the site link and browser sign-in. OpenAI desktop and Codex use two copied commands followed by browser OAuth. Other clients can use the local installer.
My MCP client has a tool limit (e.g. 100 tools in Antigravity). What do I do?
Since v6.0, Respira automatically filters tools based on your site's detected builder and plugins (context-aware filtering), so a client sees a subset of the catalog rather than all of it. 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.
