MCP server
GreenShift MCP server, with undo on every edit.
A GreenShift MCP server lets Claude, ChatGPT or Cursor read and edit GreenShift pages on a live WordPress site, block by block. 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
- Full
- GreenShift tools
- Core set
- Latest release touching it
- 9.2.7
- Releases touching it
- 29
Respira is an independent MCP server. Not affiliated with, endorsed by, or sponsored by Wpsoul. GreenShift is a product of Wpsoul.
What works today. What still needs you.
Read from the current MCP server release, first-class reads and writes across the builder structure.
Works now
- GreenShift is detected under each name it has shipped as, and its version is read from the plugin itself. A page counts as a GreenShift page when it holds at least one
greenshift-blocks/*block. - One namespace covers the builder and its five add-ons (GSAP animation, Query and Meta, WooCommerce, SEO and Chart), so their blocks are read and edited like the rest.
- GreenShift builds a block's CSS from its style attributes instead of storing it in the block. When a write touches a GreenShift block with styles, Respira marks it for GreenShift to render that CSS on the server, so the edited page keeps its styling.
- A style sent as a single value is turned into the responsive shape GreenShift reads (desktop, tablet, mobile landscape, mobile portrait). A GreenShift element whose saved HTML is missing gets it rebuilt from its attributes, so its text shows on the page.
- Children sent under
elements,modules,rowsorcolumnsare folded into the block's inner blocks instead of being dropped, and the write says how many it folded. - New elements are GreenShift blocks (plugin 9.2.7) when the agent passes builder "greenshift" to
respira_build_page,respira_inject_builder_contentor an add_* tool, or when the page already holds GreenShift blocks. Sections, rows, columns, headings, text, buttons, images, spacers, dividers, lists and accordions are each GreenShift's Advanced HTML Element (greenshift-blocks/element), with sections laid out the way GreenShift's own guidance recommends and the CSSRender flag GreenShift needs. - Tested on WordPress 7.1 with GreenShift 13.2.1: every block written opens in the block editor without an "unexpected or invalid content" warning, and adding to a page leaves the existing content byte for byte.
- Every write is render-checked: the saved markup is parsed the way WordPress parses it and each block is rendered in process. The result names any broken block, with the
snapshot_uuidthat undoes the write.
Where a human still steps in
- An icon, tabs and a video are written as core blocks (the core icon and tabs blocks, a video embed), not as GreenShift blocks, and each is named in a
library_core_fallbackwarning. On a new page with no builder named, elements are core blocks, and the answer names the builder value to pass. - Exhale, the HTML to page conversion, still writes core blocks on a GreenShift site.
- Custom JavaScript set on a block attribute is stored and does not run, because GreenShift loads block scripts from a site option. The write warns about it; a script that has to run belongs in an HTML block.
- There are no GreenShift-specific tools: pages run on the block editor tools and the universal page tools. GreenShift settings kept outside the page content are not written through them.
Hit one of these and the snapshot gives you a clean way back.
GreenShift 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 GreenShift site. Paste it into your AI tool and run.
-
Change a button label across pages
Find every GreenShift element whose text is "Learn more" on published pages and change it to "See how it works". Keep the styling, and make the changes on copies. -
Audit add-on blocks
List every page that uses GreenShift add-on blocks, such as charts, comparison tables or animation containers, with the block names per page. Do not change anything. -
Shorten section headings
On the GreenShift page "Features", list every heading with its level and length. Suggest shorter versions for any over 60 characters, then apply them on a copy after I approve.
More recipes, per builder, in the Prompt Book.
Connect a GreenShift 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@latestPut 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-siteRun 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/mcpClaude 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 GreenShift 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 GreenShift lately.
The last 5 releases that mention GreenShift, filtered from the same changelog the releases page reads.
-
- Kadence Blocks, Spectra, GenerateBlocks and GreenShift pages get their own blocks. Until now, a new element on a block library site was a WordPress core block: ask for a Kadence row with two columns and you got a core group and core columns, with none of Kadence's controls.
- A generic section on a Beaver Builder page shows its content. The shape agents send to every builder, a section holding a heading and text, was saved on Beaver with "section" and "text" as module names. Beaver has neither, so the page showed nothing but its title while the write said success.
- GreenShift elements without styles open cleanly in the editor. An element written with a localId but no styles carried that id as a class, which GreenShift's editor does not save, so it flagged the block as invalid. The class is now written only on styled elements, as GreenShift does.
-
- Agents are told that Spectra, Kadence Blocks, GenerateBlocks and GreenShift write their own blocks. The block library guidance, the native_generation note in respira_get_builder_info and build_page's builder parameter now say that passing builder "kadence", "spectra", "generateblocks" or "greenshift", or writing to a page that already has the library's blocks, writes the library's blocks, and that anything a library has no block for comes back as a core block in a library_core_fallback warning.
-
- 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.
-
- Builders are detected however early detection runs. Each builder used to be detected only once it had booted in the current request, so a check that ran before the theme loaded saw no Bricks, no Divi on a renamed or child theme, and no GreenShift, then cached "block editor only" for an hour.
Questions people ask about GreenShift and MCP.
Does Respira write GreenShift blocks or core blocks?
GreenShift blocks, since plugin 9.2.7, when the agent passes builder "greenshift" or the page already uses GreenShift: sections, rows, columns, headings, text, buttons, images, spacers, dividers, lists and accordions are each written as GreenShift's Advanced HTML Element. An icon, tabs and a video are core blocks, and the answer names them.
Is there an MCP server for GreenShift?
Yes. Respira is an independent MCP server that reads and writes GreenShift in its own format, with first-class reads and writes across the builder structure. It is not made by the GreenShift team.
Which tools does it use for GreenShift?
GreenShift 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 GreenShift 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.
