Spectra MCP server, with undo on every edit.

A Spectra MCP server lets Claude, ChatGPT or Cursor read and edit Spectra 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.

Start free Connect in one command

7 days free. No card. Runs on the AI subscription you already have.

Support
Partial
Spectra tools
Core set
Latest release touching it
9.2.4
Releases touching it
24

Respira is an independent MCP server. Not affiliated with, endorsed by, or sponsored by Brainstorm Force. Spectra is a product of Brainstorm Force.

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

  • Spectra is detected whether the site runs Spectra Legacy (Ultimate Addons for Gutenberg) or the newer Spectra Blocks plugin. A page counts as a Spectra page when it holds at least one spectra/* or uagb/* block; a page with neither is treated as plain Gutenberg.
  • Both namespaces are read side by side, because Spectra leaves legacy uagb/* blocks in place when a site moves to spectra/*. The block names the agent is offered come from the site's own block registry.
  • Existing Spectra blocks are edited in place with respira_find_element + respira_update_element, keeping their attributes and inner blocks. Blocks you did not ask to change are written back byte for byte.
  • The add_* tools and respira_update_element were run against Spectra 2.20.3 and the published page was read after each call.
  • 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_uuid that undoes the write.
  • Custom CSS sent with a page update is stored, printed on the page and covered by the snapshot.

Where a human still steps in

  • A new element an agent adds, through respira_build_page, an add_* tool or an append, is written as WordPress core blocks (group, heading, paragraph, buttons, image), not as a Spectra block. Existing Spectra blocks stay Spectra blocks.
  • There are no Spectra-specific tools: Spectra pages run on the block editor tools and the universal page tools. Spectra settings kept outside the page content are not written through them.
  • The block editor's own save-time validation is a separate check from Respira's render check; a block whose markup renders but whose editor schema disagrees still shows a validation prompt the next time a person opens the page.

Hit one of these and the snapshot gives you a clean way back.

Spectra 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.

Browse every tool

Three prompts you can paste right now.

Each one assumes Respira is connected to a Spectra site. Paste it into your AI tool and run.

  1. Change a call to action across pages

    Find every Spectra button whose text is "Get a quote" on published pages. Change it to "Request a quote" and keep its styling. Snapshot each page first.

  2. Map legacy and current blocks

    List every page that still uses legacy uagb/* blocks next to spectra/* blocks, with the block names and a count per page. Do not change anything.

  3. Fix the heading order on one page

    On the page "About", list every Spectra heading with its level. Make sure there is one H1 and no level is skipped. Make the changes on a copy.

More recipes, per builder, in the Prompt Book.

Connect a Spectra 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.json in 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 --doctor in the same shell. It names the missing setting, a bad URL or a refused key. node -v must print 20 or newer.
ENOENT errors that mention /_npx/ or node_modules.
Cause The npx cache is damaged, often by an interrupted install.
Fix Run rm -rf ~/.npm/_npx and restart the client. Or install once with npm install -g @respira/wordpress-mcp-server and use respira-wordpress-mcp as 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 Spectra 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 Spectra lately.

The last 5 releases that mention Spectra, filtered from the same changelog the releases page reads.

  1. 9.2.4 Oct 14, 2026
    • 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.
  2. 9.2.0 Oct 13, 2026
    • 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.
    • The new Spectra Blocks plugin is detected as Spectra. Spectra split into Spectra Legacy and the new Spectra Blocks in 2026, and sites on the new plugin reported no Spectra at all.
  3. 9.1.20 Oct 3, 2026
    • Custom CSS on block pages is stored and renders. update_page, update_post and update_custom_post silently dropped custom_css on Gutenberg, Kadence, Spectra, GenerateBlocks and GreenShift pages while reporting success.
  4. 9.1.11 Oct 2, 2026
    • 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.
  5. mcp-8.4.10 Oct 2, 2026
    • 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.

All 24 releases that touched Spectra

Questions people ask about Spectra and MCP.

Is there an MCP server for Spectra?

Yes. Respira is an independent MCP server that reads and writes Spectra in its own format, with core reads and writes work; some edges need a human pass. It is not made by the Spectra team.

Which tools does it use for Spectra?

Spectra 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 Spectra 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.

Everything the WordPress MCP doesWooCommerce MCP

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.

Start free Email Mihai
Summarize with Google AI Mode