MCP serverThe WordPress MCP that speaks your page builder.
A WordPress MCP server lets Claude, ChatGPT, Cursor or Codex read and edit a live WordPress site. Respira is one that speaks 17 page builders and the native Site Editor: every change lands on a copy first, you approve it, and you can undo it for 90 days.
7 days free. No card. Runs on the AI subscription you already pay for. See plans
- Plugin 9.1.23
- MCP server 8.4.16
- 250+ core tools
- 350+ WebMCP abilities
One command. Any coding tool.
It detects Claude Code, Cursor, Codex, Windsurf and nine more, and writes the right config for you.
npx add-mcp "npx -y @respira/wordpress-mcp-server"Something off? npx @respira/wordpress-mcp-server --doctor runs nine checks: Node, config, connectivity, plugin version, compatibility, updates.
Three ways in. Same site, same tools.
Pick the one your app supports. The first needs no key and no file.
-
Sign in with your browser
Add the site as a connector by URL and approve it once. No key, no file. Disconnect from the dashboard any time.
Claude Desktop, claude.ai, Claude Code, ChatGPT, Codex, Cursor
Setup guide -
URL and API key
Point any remote MCP client at the site URL with your key in the Authorization header.
Any client that speaks remote MCP
Get your URL and key -
One command on your machine
One npx command detects your tool and writes its config. The bridge runs locally.
Claude Code, Cursor, Codex, Windsurf, OpenCode, Hermes and more
Copy the command
Or skip the client. Respira AER puts Respira's builder intelligence in a chat connected to all your WordPress sites, in your dashboard and on your phone, with your own provider key.
When a host gets in the way
Respira's clients send the credential a second way, in a header of Respira's own, and the plugin reads that copy when a request arrives with none, so a host that strips the Authorization header does not end the connection. Respira › Troubleshoot in wp-admin runs the connection checks from the site's own server: the REST address, the sign-in discovery document, the Authorization header and its backup, the bot filter that refuses the user agents claude.ai's and ChatGPT's connectors send, and the security plugins and CDNs in front of the site. It writes a plain-text report for your host and a prompt to paste into your agent so it connects itself. An error that does reach the agent names its cause and says whether sending the call again can help.
Signed in? Install with every site on your account already configured.
Works with the AI you already use.
If it speaks MCP, it speaks Respira. Chat apps, coding tools, automation.
Apps & web
-
Claude Desktop the app on your computer -
Claude Cowork one file for all your sites - claude.ai claude.ai in your browser
-
ChatGPT web chatgpt.com in a desktop browser - ChatGPT desktop the macOS and Windows app
-
Grok grok.com in your browser
Chat & team channels
-
Slack / Microsoft Teams via Viktor, your AI coworker in chat
Coding tools
- Claude Code in your terminal
-
Conductor Claude Code or Codex, in Conductor -
Cursor the coding editor -
VS Code the code editor -
Continue the open-source extension in VS Code or JetBrains -
OpenAI desktop / Codex desktop app, CLI, or editor -
Antigravity the AI browser -
OpenCode open-source coding tool -
Hermes Agent the open-source agent from Nous Research - Grok Build the terminal agent from xAI
Automation & other
-
n8n the automation platform -
Other tool any MCP client
Open your setup page for one-click connect per site, with the key and access scope prefilled.
One page per builder.
Respira writes in each builder's own format, so the page still opens in its editor. Each builder has its own page with the tools it gets, the prompts that work, and the limits.
-
Gutenberg. The block editor, block by block, with block templates, template parts and patterns.
Gutenberg MCP server -
Elementor. Classic widgets and Atomic elements, with Site Settings colours and fonts kept linked.
Elementor MCP server -
Divi. Divi 4 shortcodes and Divi 5 blocks, with a Migration Copilot for the move between them.
Divi MCP server -
Bricks. Pages, global classes, components and theme styles, with undo that covers the global styles too.
Bricks MCP server -
WPBakery. Nested vc_* shortcodes on legacy Visual Composer sites, attribute order kept on the round trip.
WPBakery MCP server -
Oxygen. The element tree of Oxygen Classic 4.x and Oxygen 6, patched with parent and child references intact.
Oxygen MCP server -
Beaver Builder. Rows, columns and every module Beaver Builder 2.10 registers, plus Beaver Themer layouts.
Beaver Builder MCP server -
Breakdance. Elements, Global Blocks and Global Styles on Breakdance Free and Pro.
Breakdance MCP server -
Flatsome. UX Builder shortcodes on the Flatsome WooCommerce theme, product grids and banners kept intact.
Flatsome MCP server
8 more builders, from Kadence to GenerateBlocks, run on the universal tools. Every supported builder
Your live site is never the experiment.
The same three steps on every builder, on every write.
-
Duplicate first
The agent edits a copy of the page. The live page stays as it was.
-
You approve
Review the change inside WordPress, then publish it or send it back.
-
Undo for 90 days
Every write is snapshotted. Roll any change back in one click.
Structural writes go further. Each one is guarded against a stale base, read back through WordPress and render-verified, the block editor included. The result says verified only after WordPress rendered it. A delete moves the item to the trash with a snapshot, a theme file write keeps the previous bytes, and respira_restore_snapshot brings either back.
- Tools and abilities
- 360+
- Page builders
- 17
- WooCommerce tools
- 104
- Undo window
- 90 days
Plan first. Nothing is written until you say so.
Start a session in plan mode and every write comes back as a step with its predicted effect. You read the plan, then apply it, in any MCP client.
-
respira_begin_session(mode: 'plan')From here every write answers with a step instead of changing the site: the tool, its arguments with secrets hidden, the predicted effect, and whether it would land on a draft copy or the live item. Reads run as usual.
-
respira_get_planThe steps so far, in order, for the person to read before anything runs. A write the connection could never make is refused rather than planned.
-
respira_apply_planRuns the accepted steps in order, each through the same checks and the same approval gate as a direct call, and returns one receipt with every step's outcome, snapshot ids and preview links.
-
respira_discard_planEmpties the plan. Ending the session turns plan mode off and says how many steps never ran. One write can also be planned on its own with _respira_plan: true on the call.
It is only tool results, so it works in Claude Code, Cursor, Claude Desktop, ChatGPT and any client that speaks MCP, with nothing to install on the client side. Respira AER shows the same plan in the chat as a card of steps you run one at a time or all at once: one idea, two surfaces.
The same rules on every door.
A site has three ways in: the npm server, the REST API and its own MCP endpoint. What the owner allows holds on all three.
-
Tool switches and profiles hold on every door
A tool switched off in Respira › Tools stays off, and the Observe, Content and Everything profiles hold, whether the agent arrives through the npm server, the REST API or the site's own MCP endpoint that Claude Desktop, ChatGPT and AER use.
Observe · Content · Everything -
Other plugins' abilities, on the owner's terms
respira_search_abilities searches every ability registered on the site, ranked, and says for each whether Respira can invoke it now and, when it cannot, why. One owner setting, off unless turned on, lets an agent run the abilities other plugins declare read-only. Anything that can change the site is enabled by name.
respira_search_abilities · respira_invoke_ability -
Instructions the site keeps for its agents
Respira › AI Skills holds short Markdown pages on how a thing is done on this site. The enabled ones ride in every session's site context, four tools read and, when asked, write them, and the What your AI is told screen shows everything an agent receives from the site, in order.
respira_list_skills · respira_get_skill
One workflow, two runtimes, and WebMCP.
The same duplicate-first, approve, undo loop whether the agent lives on your desktop or in a browser tab.
-
Desktop MCP server
The npm package your coding tool or chat app talks to. Runs on your machine or connects by URL.
250+ core tools -
WebMCP in the browser
Built into the plugin. Chrome with WebMCP lets Claude or ChatGPT in a tab call the site directly, no bridge to install.
350+ abilities -
WordPress Abilities
Every tool is also a WordPress ability with a stable id, so the official MCP adapter and any future host can discover it.
respira/<tool-name>
Watch Claude in Chrome edit a site over WebMCPBrowse the abilities
Next to the official WordPress MCP.
Both matter. The official server gives an agent core access. Respira adds the builders and the safety a production site needs.
An MCP that knows how to behave.
When something goes wrong, the agent does not panic and does not invent a fix.
-
Reads SOUL.md first
Identity, voice and rules load in the handshake, before the first tool call, on the npm server and on the site's own MCP endpoint alike. A plan step or an approval request is a question for the person, never for the agent.
Read SOUL.md -
Searches the docs before guessing
A tool error triggers one retry, then a search of the live documentation. Most surprises are already written down.
Browse the docs -
Files a bug only when you say so
When docs and diagnostics come up empty, it asks you. A yes files a structured report from inside the chat. No prompts, no content, no results leave the site.
Bug reports
Running a store? The same MCP runs it.
The WooCommerce add-on adds 104 store tools: products and variations, coupons, orders and refunds, bounded revenue reporting, store configuration. Refunds dry-run by default. Every write snapshotted.
Listed where MCP servers are found.
Questions people ask before connecting.
Is there an Elementor MCP server?
Yes. Respira reads and writes Elementor in its own format, classic widgets and Atomic elements alike. The tools, prompts and limits are on its own page.
Is there a Divi 5 MCP server?
Yes. Respira reads and writes Divi 4 shortcodes and Divi 5 blocks, inside the same duplicate-first approval flow. The detail is on its own page.
Is there an MCP server for Bricks, WPBakery or Gutenberg?
Yes. Bricks, WPBakery, Gutenberg and 14 more builders share one safety model, and each has its own page with the tools it gets.
Can the MCP edit the native Site Editor?
Yes. Block templates and template parts with their hierarchy, synced and unsynced patterns, block navigation by exact path, and theme.json design tokens. Classic theme files and plugin PHP stay out of reach on purpose.
How does Respira know a structural write actually worked?
It checks. A structural write is guarded against a stale base, snapshotted, read back through WordPress and render-verified, the block editor included. The result says verified only after WordPress rendered it, and a problem is named with its block and path.
Can I see what the agent would do before it does it?
Yes. Start a session with mode plan, or send _respira_plan: true on one write. Every write then comes back as a step with its predicted effect and nothing is written. respira_get_plan shows the steps, respira_apply_plan runs the ones you accept in order through each tool's own approval gate, and respira_discard_plan drops them. It is only tool results, so it works in Claude Code, Cursor, Claude Desktop, ChatGPT and any other MCP client.
Do tool switches apply when Claude Desktop or ChatGPT connects to the site directly?
Yes. A tool switched off in Respira › Tools, and the Observe, Content and Everything profiles, hold on the npm server, the REST API and the site's own MCP endpoint alike. The switch lives in the plugin, so every door reads the same list.
My host strips the Authorization header. Does the connection still work?
Yes. Respira's clients send the credential a second way, in a header of Respira's own, and the plugin reads that copy when a request arrives with no credential. Respira › Troubleshoot in wp-admin runs the connection checks from the site's own server, names what is in the way, and writes a plain-text report for your host.
Can a delete be undone?
Yes. A page, post, custom post or media item an agent deletes goes to the trash with a snapshot first, and the answer carries the snapshot id. respira_restore_snapshot brings it back with its old status and slug. A theme file write keeps the previous bytes the same way.
Can an agent use abilities from other plugins?
Yes, on the owner's terms. respira_search_abilities searches every ability registered on the site and says for each whether Respira can invoke it now. Abilities another plugin declares read-only run behind one setting the site owner turns on; anything that can change the site is enabled by name in Respira › Abilities.
Does it work with Claude Desktop, Claude Code, Cursor and Codex?
Yes. Any MCP client works: a browser sign-in for the apps, one command for the coding tools, or a URL and key for anything else.
Does the site need to be public?
The client has to reach the site URL. Browser sign-in needs HTTPS. A local API-key connection also works on a private network the client can reach.
Can it edit WooCommerce products?
With the WooCommerce add-on: 104 tools for products, variations, coupons, orders, refunds and bounded reporting. Approvals keep the live product ID stable, so catalogs and feeds do not break.
What does duplicate-before-edit mean?
The agent changes a duplicate first. You review and approve before anything goes live. The original is untouched until you say so.
Do I pay for AI usage?
No. Respira runs on the AI subscription you already have. The price covers the sites, not the tokens.
Start with one site. Free for 7 days.
Maker is €9 a month after the trial. No card for the trial, and it runs on the AI plan you already have, so there is no extra AI bill.
