Brizy MCP server, with undo on every edit.
A Brizy MCP server lets Claude, ChatGPT or Cursor read and edit Brizy pages on a live WordPress site, element by element. With Respira every edit lands on a copy first, and you can undo it for 90 days.
7 days free. No card. Runs on the AI subscription you already have.
- Support
- Partial
- Brizy tools
- Core set
- Latest release touching it
- 9.2.4
- Releases touching it
- 25
Respira is an independent MCP server. Not affiliated with, endorsed by, or sponsored by Brizy. Brizy is a trademark of its owner.
What works today. What still needs you.
Read from the current MCP server release, core reads and writes work; some edges need a human pass.
Works now
- Reads and writes go through the storage Brizy keeps for a page, so the Brizy editor opens what Respira wrote. After a write the page is marked for Brizy to compile again on its next view.
- Every element carries its Brizy
_idas its id, sorespira_find_element,respira_update_elementandrespira_move_elementwork by id. - A text edit sent as plain text keeps the element's existing tag and formatting; HTML is stored as sent. Elements you did not touch keep their exact stored form, and a write that changes nothing is skipped.
- A move only moves: the rest of the page stays as it was, and moving an element into itself is refused before anything changes.
- Content sent without Brizy's section structure is wrapped in a Section, SectionItem and Wrapper, the shape the Brizy editor and compiler read.
- Full-page writes are checked against the Brizy element catalogue Respira carries, and
respira_get_page_outlinelists each section with its first heading and element count.
Where a human still steps in
- Brizy has no documented write API, so Respira writes conservatively. Text edits and small changes to existing pages are the safe path; review a whole page an agent built before it goes live.
- Brizy compiles the page after a write, and that compile depends on Brizy's compiler service, so the site needs an internet connection for a change to show.
- There are no Brizy-specific tools. Global blocks, popups and Brizy Cloud are not managed through the MCP.
Hit one of these and the snapshot gives you a clean way back.
Brizy runs on the universal tools.
Find, update, move and remove elements, build whole pages, snapshot and roll back. Reads return the builder structure and writes keep it intact.
Three prompts you can paste right now.
Each one assumes Respira is connected to a Brizy site. Paste it into your AI tool and run.
-
Rewrite a hero headline
On the Brizy page "Home", find the first heading and change it to "Websites that load in a second". Keep its formatting, and make the change on a copy. -
Outline a long page
Show me the outline of the Brizy page "Services": each section with its first heading and how many elements it holds. -
Fix vague button labels
Find every Brizy button on published pages whose label is "Click here". Suggest a clearer label for each from the text around it, then apply them on copies after I approve.
More recipes, per builder, in the Prompt Book.
Connect a Brizy site in two minutes.
Pick your client and paste. The site URL and key come from your setup page, or from Respira › Setup in wp-admin. Node.js 20 or newer for the local server.
Claude Code
claude mcp add respira-wordpress --env WORDPRESS_URL=https://yoursite.com --env WORDPRESS_API_KEY=respira_your_api_key_here -- npx -y @respira/wordpress-mcp-server@latest Put in your own site URL and key, run it, then check with /mcp. Every site at once: pass --env RESPIRA_CONFIG_B64=… from your setup page instead of the two values. The full Claude Code guide covers the first edit and undo.
Claude Desktop and Cursor
{
"mcpServers": {
"respira-wordpress": {
"command": "npx",
"args": ["-y", "@respira/wordpress-mcp-server@latest"],
"env": {
"WORDPRESS_URL": "https://yoursite.com",
"WORDPRESS_API_KEY": "respira_your_api_key_here"
}
}
}
} - Claude Desktop, macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Claude Desktop, Windows:
%APPDATA%\Claude\claude_desktop_config.json - Cursor:
.cursor/mcp.jsonin your project
The file is claude_desktop_config.json, not config.json. Every site at once: replace the two env values with RESPIRA_CONFIG_B64 from your setup page.
Codex
codex mcp add respira-my-site --url https://yoursite.com/wp-json/respira/v1/mcp
codex mcp login respira-my-site Run them one at a time. The second opens your browser to sign in to Respira; no key goes in the config. By hand, in ~/.codex/config.toml, then run the login command:
[mcp_servers.respira-my-site]
url = "https://yoursite.com/wp-json/respira/v1/mcp" Browser sign-in, no key
https://yoursite.com/wp-json/respira/v1/mcp Claude Desktop, claude.ai, ChatGPT and Cursor: add a custom connector, paste your site's MCP URL, leave Client ID and Client Secret blank, and approve the sign-in on respira.press. One connector per site.
Any other client
npx add-mcp "npx -y @respira/wordpress-mcp-server@latest" Detects Claude Code, Cursor, Codex, Windsurf and more, and writes the config. Set WORDPRESS_URL and WORDPRESS_API_KEY afterwards.
Common errors
- The server does not show up in /mcp, or the client says it failed to start.
- Cause Node.js is older than 20, or the site URL and key are missing.
- Fix Run
npx @respira/wordpress-mcp-server --doctorin the same shell. It names the missing setting, a bad URL or a refused key.node -vmust print 20 or newer. - ENOENT errors that mention
/_npx/ornode_modules. - Cause The npx cache is damaged, often by an interrupted install.
- Fix Run
rm -rf ~/.npm/_npxand restart the client. Or install once withnpm install -g @respira/wordpress-mcp-serverand userespira-wordpress-mcpas the command. - The browser sign-in opens a "Page not found" on
yoursite.com/authorize. - Cause A Client ID was filled in on the connector, usually the
respira_site_key. - Fix Remove the connector and add it again with the MCP URL only. Leave Client ID and Client Secret blank. Sign-in happens on respira.press, never on your site.
- The MCP address returns 404.
- Cause WordPress is on plain permalinks, so
/wp-json/addresses do not resolve. - Fix In wp-admin open Settings › Permalinks, choose Post name and save once.
- Calls fail with 401, 403, or HTML where JSON belongs.
- Cause A firewall, a bot filter or a challenge page answers before WordPress does, or the host strips the Authorization header.
- Fix Open Respira › Troubleshoot in wp-admin. It runs the checks from the site's own server, names what is in the way and writes a report for your host.
- The agent says it saved, and the live Brizy page looks the same.
- Cause The edit is on a draft duplicate, waiting for your approval. That is the default on a published page.
- Fix Approve the duplicate in wp-admin under Respira, or from its preview page. Until then the live page stays as it was.
Still stuck? Troubleshooting in the docs, or write to word@respira.press with the first error line.
What changed for Brizy lately.
The last 5 releases that mention Brizy, filtered from the same changelog the releases page reads.
-
- WPBakery pages with many addon elements can be read and edited again. On a WPBakery site running The7 with Ultimate VC Addons, Revolution Slider, Go Pricing and WooCommerce, every builder tool failed: finding an element, reading the page's structure, duplicating it, and every edit, even a one word change on a small draft.
-
- Every builder says what it can write. get_builder_info now carries write_capabilities for every builder: whether it builds pages, adds elements or only edits text, and whether a new element is native, written as core blocks, or partial.
-
- Share links show Beaver Builder and Brizy drafts. Both builders refused to draw a draft for a logged-out visitor, so a shared draft rendered as an empty page. A share link also no longer redirects to a draft's permalink, which sent a draft without a slug to the home page.
-
- find_element by content, text or class works on every builder. A search for text that was not on the page answered HTTP 404, which agents read as a broken tool, and a class search on Elementor never read the custom class setting.
-
- wordpress_find_element searches content, text and class on every builder (plugin 9.1.11). The description says each match names its field with a snippet and that no match is a normal answer with found: 0. wordpress_apply_builder_patch points at it for pages other than Divi 4.
Questions people ask about Brizy and MCP.
Is there an MCP server for Brizy?
Yes. Respira is an independent MCP server that reads and writes Brizy in its own format, with core reads and writes work; some edges need a human pass. It is not made by the Brizy team.
Which tools does it use for Brizy?
Brizy runs through the universal tools: find, update, move and remove elements, build pages, snapshot and roll back. Reads return the builder structure, and writes keep it.
What happens when the agent gets an edit wrong?
Nothing on the live page. The agent edits a copy first, you approve it inside WordPress, and every write is snapshotted with 90 days of undo.
Do I need a developer or a terminal?
No. Sign in with your browser from Claude, ChatGPT or Cursor and approve the connection once. Coding tools get a one-line command.
Does it work with a Brizy site that also runs WooCommerce?
Yes. The WooCommerce add-on adds 104 store tools on the same connection, with the same duplicate-first approval flow.
The other builders, same server.
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.