API Orchestration
looot
A hosted catalog of data endpoints behind one token and prepaid balance, exposed to agents over a remote MCP server, CLI and REST API
Site owners and agencies can use MCP clients to update WordPress content in its builder-native format while reviewing draft page and post edits. Builder support varies by operation, and Site Editor structural writes require a per-site switch. Snapshots support rollback; direct live editing is optional, and plan application is cooperative rather than an independently enforced human approval.
WordPress plugin and MCP server that lets AI agents read and edit live sites in their page builder's own format, staging page and post edits on draft copies by default.
Overview
Respira for WordPress is a WordPress plugin with an MCP server that lets AI agents read and edit a live WordPress site in the native format of its page builder, such as Gutenberg, Elementor, Divi or Bricks. How deep the editing goes depends on the builder: most get module-level read and write, Thrive Architect gets text edits, SeedProd is audit only, and structural writes to the block Site Editor are off until the owner turns them on for the site. Agents connect through a local npm MCP server, through the site’s own remote MCP endpoint with a browser OAuth sign-in, through WebMCP in Chrome, or through the Respira CLI. Respira is built by Mihai Dragomirescu.
Site owners keep control of access: tool switches and the Observe, Content and Everything profiles apply on the npm server, the REST API and the site’s MCP endpoint alike, and an OAuth token works only on the one site it was approved for. Owners who want a hard gate can switch on owner approval (plugin 9.1.10 or later), which holds plugin installs and deletions, user deletion and option deletion until an administrator approves in wp-admin. The plugin is commercial software; the local npm MCP bridge and the CLI are MIT licensed, and the hosted OAuth sign-in runs through a respira.press account.
Listing decision
The qualifying capability sits in the commercial WordPress plugin, not in the MCP wrapper: the plugin reads and writes each page builder’s own data format, and its duplicate-first default for page and post edits, snapshots, plan mode and tool switches apply on every connection path. These are safeguards the owner configures, not an independent human gate on every write: direct editing can be turned on, and plan steps run when the client applies the plan.
Before you choose
Site owners, freelancers and agencies who want Claude, ChatGPT, Cursor, Codex or another MCP client to edit existing WordPress sites built with page builders, with page and post edits staged on draft copies for a person to publish.
Teams that need a fully open-source WordPress agent stack with no commercial dependency. The repository README states that the plugin is commercially licensed and that the MIT-licensed MCP server is a client for it.
The duplicate-first workflow covers page and post edits by default; with direct editing turned on, or a forced live edit, an edit lands on the live item, and plugin, user and settings actions are not staged copies. Plan mode needs plugin 9.1.0 and MCP server 8.4.0 or later; applying a plan is the client’s call, and it counts as the approval for steps that ask for one, so a person must be the one who asks for it. The wp-admin owner approval, which holds plugin installs and deletions, user deletion and option deletion until an administrator approves, needs plugin 9.1.10 or later and is off until the owner switches it on. Editing depth varies by builder: the builder matrix lists most builders, including Elementor, Divi, Bricks and Gutenberg, with module-level read and write, Thrive Architect with text edits only, and SeedProd as audit only, and its count of 17 builders counts Divi 4 and Divi 5, and Oxygen Classic and Oxygen 6, separately. Site Editor templates, template parts, patterns and navigation can be read on every site, but structural writes to them are off by default and the owner switches them on per site. Ongoing use requires a paid Respira licence. The seven-day trial without a card applies to the one-site Maker plan; Builder and Studio bill immediately. Maker, Builder and Studio carry a 14-day refund; Enterprise refunds are set in its contract, and the Founder and Founder Studio+ lifetime licences are final sale. The plugin must be installed on each WordPress site and connected to a respira.press account. Browser OAuth sign-in needs a site reachable over HTTPS. WebMCP needs Chrome 146 or later. The local MCP server and the CLI need Node.js. WooCommerce tools are a paid add-on below the Studio plan.
First-party pages give different tool and ability totals (the documentation pages and the MCP page do not match), so this listing states no count. No independent hands-on test was performed for this submission.
Sources
First-party unless marked otherwise. Each link supports only its adjacent claim.
Describes an MCP server that lets Claude, ChatGPT, Cursor or Codex read and edit a live WordPress site in 17 page builders (a count that lists Divi 4 and 5, and Oxygen Classic and 6, separately) and the Site Editor, writing in each builder's own format; the page does not break this down by operation, so the depth per builder and the Site Editor write switch are taken from the builder matrix below; three connection paths (browser sign-in by URL, URL plus API key, local npx bridge); duplicate-first page and post writes and 90 days of undo; plan mode; tool switches and Observe, Content and Everything profiles that hold on the npm server, the REST API and the site's own MCP endpoint; owner-gated search and invocation of other plugins' abilities; site AI Skills in session context; WebMCP and WordPress Abilities; and names Mihai Dragomirescu as founder.
official product page · accessed Oct 3, 2026Lists editing depth per builder: module-level read and write for most builders, Thrive Architect as text edits, SeedProd as audit only. Counts 17 builders with Divi 4 and 5, and Oxygen Classic and 6, as separate entries. Site Editor templates, template parts, patterns and navigation are readable everywhere; structural writes to them are off by default and switched on per site by the owner.
official documentation · accessed Oct 12, 2026Documents the per-site MCP URL at /wp-json/respira/v1/mcp, browser OAuth sign-in with respira.press as the authorization server, tokens bound to the one approved site, read and write permission levels, the need for the plugin and a Respira account, and disconnection from the dashboard.
official documentation · accessed Oct 3, 2026States that WebMCP is built into the plugin with no separate bridge, requires Chrome 146 or later, and uses the same duplicate-before-edit workflow as the desktop MCP server.
official documentation · accessed Oct 3, 2026Documents installing the plugin on the WordPress site, generating an API key in wp-admin, and running the @respira/wordpress-mcp-server npm package locally with a setup wizard to connect an AI assistant.
official documentation · accessed Oct 3, 2026Explains the default workflow for page and post edits: the edit is written to a linked duplicate post, the agent receives the duplicate's ID and preview URL, and the original stays unchanged until a person approves in WordPress, with snapshots underneath. It does not apply when the owner has turned on direct editing.
official documentation · accessed Oct 3, 2026Documents respira_begin_session with mode plan, where every write returns a proposed step instead of changing the site, in any MCP client. Waiting for the person to agree before applying is an instruction to the client; the apply call itself is what runs the plan.
official documentation · accessed Oct 3, 2026Runs the planned steps in order through the same checks as direct calls and returns one receipt; the apply call is treated as the approval for steps whose tool asks for one.
official documentation · accessed Oct 4, 2026Edits a page; by default a published page is edited on a draft duplicate, and a live edit is possible when the owner has turned on direct editing.
official documentation · accessed Oct 4, 2026An opt-in setting, off by default, that holds a defined set of high-risk actions (plugin installs and deletions, user deletion, option deletion) until an administrator approves in wp-admin.
official documentation · accessed Oct 4, 2026Documents logging of the tool or action performed, its timestamp, success or failure, and site identifier, used to trace safe-edit approvals and rejections.
official documentation · accessed Oct 3, 2026Describes @respira/cli, an MIT-licensed command line interface for Claude Code, Cursor and AI coding agents that reads and writes page builder content through the Respira plugin, with snapshot-backed writes and one JSON result envelope with a fixed exit code per command.
official product page · accessed Oct 3, 2026Lists paid Maker (EUR 9 a month or EUR 71 a year for one site), Builder, Studio, Enterprise and lifetime plans; the seven-day free trial without a card is Maker only, and Builder and Studio bill immediately. Its plan matrix gives Maker, Builder and Studio a 14-day refund, sets Enterprise refunds in the contract, and makes the Founder and Founder Studio+ lifetime licences final sale. No ongoing free plan is listed.
official pricing · accessed Oct 3, 2026Documentation only: the repository holds a README and the licence, not the plugin or the server source. The README states that the MIT-licensed npm server is a client for the commercially licensed Respira plugin and needs a licensed API key.
official repository · accessed Oct 3, 2026The MIT License covers the npm MCP server client, not the commercially licensed WordPress plugin.
official license · accessed Oct 3, 2026API Orchestration
A hosted catalog of data endpoints behind one token and prepaid balance, exposed to agents over a remote MCP server, CLI and REST API
UI & Frontends
Visual UI annotation and structured feedback for AI coding agents
UI & Frontends
Agent-era UI framework with WASM sandboxes for safe generated interfaces
Comments