Bricks MCP server, with undo on every edit.

A Bricks MCP server lets Claude, ChatGPT or Cursor read and edit Bricks Builder pages, global classes, components and theme styles on a live WordPress site. Respira checks every element against the schemas Bricks publishes before it writes, puts each edit on a copy first, and keeps 90 days of undo that covers the global styles too.

Start free Connect in one command

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

Support
Deep
Bricks tools
25
Latest release touching it
9.2.22
Releases touching it
102

Respira is an independent MCP server. Not affiliated with, endorsed by, or sponsored by Bricks Builder GmbH.

Bricks MCP in 81 seconds.

81 seconds, with captions. Also on YouTube.

Bricks 2.4 ships its own tools for agents. Respira adds the undo Bricks revisions do not cover.

Since September 16, 2026, an agent can edit a Bricks 2.4 site through Bricks' own abilities, and each page edit is kept as a Bricks revision. Bricks' documentation says global classes, variables, theme styles and components are not covered by those revisions. You can use both: Respira runs Bricks' own abilities too, with a snapshot first.

Bricks' own AI abilities compared with Through Respira
Topic Bricks' own AI abilities Through Respira
A page edit Kept as a Bricks revision. Made on a copy first, approved by you in WordPress, with 90 days of undo.
Global classes, colours, variables, theme styles, components Not covered by revisions, per Bricks' documentation. Snapshotted together before the change. One restore puts all of them back.
Bricks versions 2.4 and later, once an admin turns on Bricks > AI. Every Bricks version Respira supports. The add_* tools were checked on 2.3.4 and 2.4.
A page that changed after the agent read it Refused when the agent passes the digest it read. Refused when the agent passes the content_version it read.
Your other client sites Bricks only. The same tools on 19 page builders.
Bricks' own abilities Called directly. Called through Respira: snapshot first, logged in Activity, undo handle returned.

To use both, turn on the abilities you want in Bricks > AI, then opt each one in under Respira > Abilities. Your agent reaches them through the same Respira connection it already uses.

Their documentation: Bricks' AI abilities documentation

What works today. What still needs you.

Read from the current MCP server release, dedicated tools, design-system awareness and cross-site search.

Works now

  • Every add_* tool writes the settings Bricks reads, checked against the element schemas Bricks publishes. All 21 render on Bricks 2.3.4 and 2.4.
  • Global CSS classes: list, create, update and delete (wordpress_list_bricks_global_classes, _create, _update, _delete), with a snapshot before every change.
  • Theme styles, colour palette and typography, read and write (wordpress_get_bricks_theme_styles, _color_palette, _typography).
  • Saved components: list, get, and insert into pages with fresh element IDs (wordpress_list_bricks_components, wordpress_apply_bricks_component).
  • Search every page and template by element type, class or setting in one call (wordpress_search_bricks_elements).
  • Page health check: orphaned elements, duplicate IDs, broken references, heading order (wordpress_bricks_health_check).
  • Automatic.css detection and import into the global class registry (wordpress_bricks_detect_acss, _import_acss).
  • Query loops across the site, by post type (wordpress_bricks_query_loops), and a style profile of any page to build new sections that match it (wordpress_bricks_style_profile).
  • The whole design system in one read for the agent: classes, colours, styles, typography, components (wordpress_bricks_design_system).
  • HTML to native Bricks elements for prototypes and landing pages.
  • Bricks' own AI abilities (2.4) run through Respira with a snapshot first, and global classes, colours, variables, theme styles and components are snapshotted together.
  • A change can name the page version it read (expected_version) and is refused, with nothing written, if the page changed in the meantime.

Where a human still steps in

  • Template conditions with deeply nested logic save, and still deserve a human look before they go live.
  • Bricks' own AI abilities are off until an admin turns them on in Bricks > AI, and each one is also opted in under Respira > Abilities before an agent can call it through Respira.
  • Bricks' own PHP ability stays off unless the site defines BRICKS_ENABLE_PHP_ABILITIES. Respira does not turn it on.

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

25 tools made for Bricks.

Registered in the MCP server at build time. Each name is the id your client calls, on top of the universal set: find, update, move, remove, build, snapshot, roll back.

  • wordpress_list_bricks_global_classes
  • wordpress_create_bricks_global_class
  • wordpress_update_bricks_global_class
  • wordpress_delete_bricks_global_class
  • wordpress_get_bricks_theme_styles
  • wordpress_update_bricks_theme_styles
  • wordpress_get_bricks_color_palette
  • wordpress_update_bricks_color_palette
  • wordpress_get_bricks_typography
  • wordpress_update_bricks_typography
  • wordpress_list_bricks_components
  • wordpress_get_bricks_component
  • wordpress_apply_bricks_component
  • wordpress_search_bricks_elements
  • wordpress_bricks_health_check
  • wordpress_bricks_detect_acss
  • wordpress_bricks_import_acss
  • wordpress_bricks_import_design_tokens
  • wordpress_bricks_list_section_presets
  • wordpress_bricks_insert_section_preset
  • wordpress_bricks_scaffold_bem
  • wordpress_bricks_lint_bem
  • wordpress_bricks_query_loops
  • wordpress_bricks_style_profile
  • wordpress_bricks_design_system

Source: mcp-server/src/bricks-tools.ts

Browse every tool

Three prompts you can paste right now.

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

  1. Find every page using a global class

    Search every Bricks page and template for elements using the global class "btn-primary-lg". Group the results by page title.

  2. Run a health check on the home page

    Run wordpress_bricks_health_check on the home page. List orphaned elements, duplicate IDs and heading order issues, and suggest fixes for the top 5.

  3. Restyle the buttons, safely

    Update the global class "btn-primary" to use the brand colour from the palette and a 12px radius. Tell me the snapshot id so I can undo it, then list the pages that use the class.

More recipes, per builder, in the Prompt Book.

Connect a Bricks 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 Bricks 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 Bricks lately.

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

  1. 9.2.22 Oct 24, 2026
    • On a Bricks site, asking for the theme builder's headers and footers now points to the right tools. An agent working on a Bricks site called the Divi Theme Builder tools for the header and footer and got only "Divi Theme Builder is not available", with nothing about where Bricks keeps them, so it guessed.
    • A Bricks health check with a missing or wrong page id explains itself. bricks_health_check called without a numeric page id came back as a bare "no route" error. It now says it needs the id of the page, post or Bricks template to check, and where to get one; a page id that does not exist says the same.
  2. 9.2.17 Oct 21, 2026
    • get_builder_info no longer runs out of memory on Bricks sites with a 128M limit. The Bricks element reference that ships with the plugin was read separately by three parts of the plugin, and again for every element a write checked, and the builder information cache never hit on a site without Divi, so every call rebuilt it.
  3. 9.2.7 Oct 15, 2026
    • 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.
    • Fidelity mode runs on Flatsome. A designed page now converts in fidelity mode on Flatsome, as it does on Divi, Elementor, Bricks and the others: one root section carries the page, the source sections, rows and boxes become Flatsome rows and columns with their own classes and ids, each element keeps its markup and its classes in an HTML element, forms stay real forms, and the page's stylesheet travels with it, scoped to the page.
  4. 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.
  5. 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.

All 102 releases that touched Bricks

Questions people ask about Bricks and MCP.

Bricks has its own AI tools now. Do I still need Respira?

Bricks 2.4's abilities edit Bricks well, and page edits become revisions. Respira adds what they do not have: undo for global classes, colours, variables, theme styles and components, changes made on a copy you approve before anything goes live, and the same tools on your client sites that run other builders. Respira also calls Bricks' own abilities, with a snapshot first, so you do not have to choose.

Is there an MCP server for Bricks?

Yes. Respira is an independent MCP server that reads and writes Bricks in its own format, with dedicated tools, design-system awareness and cross-site search. It is not made by the Bricks team.

Which tools does it use for Bricks?

25 Bricks-specific tools on top of the universal set: find, update, move and remove elements, build pages, snapshot and roll back. The list on this page is read from the MCP server source at build time.

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

Looking for the Bricks overview, with visuals and the conversion story? Bricks features

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