20 dedicated tools across the full Bricks design system: global classes, theme styles, color palette, typography, components, query loops, ACSS, page diagnostics, and one-call design-system export.
Respira gives AI coding agents a structure-aware way to read and write Bricks content through a duplicate-first workflow. Page and element writes are snapshotted, and changes can be reviewed before going live.
Everything below is read from this repo at build time: tool registrations come from the MCP server adapter files; changelog entries are filtered from the same source the /releases timeline uses.
Globals are now versioned. Deleting a Bricks global class, a Divi preset, or an Elementor kit color now leaves a recovery point. "The agent deleted my global class" used to be unrecoverable; now you can roll it back. Res
Code signatures (Respira_Bricks_Signatures). Bricks refuses to render code / svg / queryEditor elements on the frontend unless they carry a signature minted by Bricks with the site secret. Elements pushed through the RES
Structural autofix (Respira_Bricks_Autofix). Pre-validation repair pass on the build / inject path: strips bare px (skipping raw-CSS / text / url keys), renames div → block, regenerates invalid or duplicate IDs and rewri
Quirks coercion + warnings (Respira_Bricks_Quirks). Centralises Bricks settings footguns with a clear split: silently coerce the safe ones (link.postId / _link.postId int → string so the href actually emits; harvest imag
write_was_noop detector is now builder-aware. Pre-fix the v7.0.61 byte-conservation check snapshotted post_content before and after the write. Four of the seven adapters (Elementor, Bricks, Beaver, Oxygen, Breakdance, Br
The companion plugin v7.0.64 bundles five plugin-side fixes; the most important is making write_was_noop builder-aware so Elementor / Oxygen / Bricks / Beaver writes stop tripping the noop signal on every successful call
respira_update_element exposes edit_target + confirm_live_edit at the top level. [#3](https://github.com/respira-press/respira-wordpress-mcp/issues/3) (madeat3am, 2026-05-21). On a Bricks site with respira_allow_direct_e
Automatic.css (ACSS) detection + import: utility classes flow into the Bricks global class registry with source tagging (wordpress_bricks_detect_acss, _import_acss).
Query loop discovery across the site, filterable by post type (wordpress_bricks_query_loops).
Style profile learning: analyse a page's patterns and create matching content (wordpress_bricks_style_profile).
One-call design system export (wordpress_bricks_design_system) — classes, colors, styles, typography, components — for AI context.
HTML → native Bricks element-tree conversion for prototypes.
Known limits
Where you still need a human pass
Honest list of edges. If you hit one of these, the snapshot workflow gives you a clean rollback path.
Bricks Templates CPT supports first-class CRUD via PATCH / DELETE, but condition trees with deeply nested logic still need a human review pass.
Optimistic locking prevents concurrent overwrites; if two agents try to write the same page in parallel, the second is rejected — by design.
Bricks Pro license is detected but not validated by Respira. License-gated features are accessible if the Pro plugin says so on the site side.
Tools
25 Bricks-specific tools
Registered in mcp-server/src/bricks-tools.ts at MCP server build time. Each tool name is the canonical id you call from the MCP client.
Each one assumes Respira is connected to your WordPress site through the MCP server below. Copy a prompt, paste into your MCP client, run.
Export the design system for AI context
Call wordpress_bricks_design_system. Return the result so I can use it as context for the rest of this session.
Find every page using a specific global class
Search every Bricks page and template for elements using the global class "btn-primary-lg". Group results by page title.
Run a health check on the home page
Run wordpress_bricks_health_check on the home page. List orphaned elements, duplicate IDs, and heading hierarchy issues. Suggest fixes for the top 5.
Setup
Connect Respira's MCP server
Drop this into your MCP client config (Claude Desktop, Cursor, Codex, Windsurf — any MCP-compatible client). Generate an API key from your Respira dashboard first.
cookies. the legal kind. one click and i'll get out of your way.
what you'd actually be saying yes to
tune your cookie preferences
essentials stay on regardless. the rest is opt-in. nothing fires until you tap save.
essentials
the cookies that make logging in work and remember which partner sent you. switching these off would just break the site, so the law does not let me make you opt out.
first-touch source on a /respira_acq cookie, plus a flag if an ai chatbot referred you. helps me figure out what is working without turning you into a tracking pixel statue.
messaging
customer.io for in-app notes, chatwoot when you click the support bubble. off by default. on means i can actually answer you in the app.