Gutenberg MCP server, with undo on every edit.

Works now

• Block tree reads with respira_read_page return the actual block structure, not just rendered HTML.
• Per-element writes via respira_find_element + respira_update_element preserve block attributes and innerBlocks.
• Full-page replacement via respira_update_page works for raw HTML imports (Word doc → blocks), with snapshot rollback on every write.
• Pattern, reusable block, and template-part awareness through standard WP REST endpoints.
• Custom blocks register via the same path as core blocks. If the block exposes a REST shape, Respira can edit it.
• A generic accordion, tabs, icon, video, spacer, divider or list sent to respira_build_page is saved as the core block WordPress itself saves: the WordPress 7.1 accordion and tabs blocks with their items and panels (details blocks on versions without them), the core icon block, a video embed, and spacer, separator and list blocks with their markup (plugin 9.2.7).
• On a page that already holds Kadence Blocks, Spectra, GenerateBlocks or GreenShift blocks, new elements follow the page's library even when the agent names builder "gutenberg", and the answer says so in library_blocks_hint. Core block names such as core/heading still write core blocks.
• Every block editor write is render-checked, the same as the other builders: Respira reads the saved markup the way WordPress's block parser does and renders every block in process, on a draft or a duplicate too. The result carries render_validator_pass, validator_warnings naming each problem with its block and path, and the snapshot_uuid that undoes the write. A closing comment with no opener, a block never closed, attribute JSON that does not parse, a heading whose text sits only in its attributes, or a block whose render throws is named; an unregistered block type or an attribute WordPress will drop is a warning. Kadence, Spectra, GenerateBlocks and GreenShift pages take the same check.

Where a human still steps in

• The block editor's own save-time validation is a separate check from Respira's render check. Respira names a broken block, an attribute that does not parse or an unregistered type in the write result; a block whose markup WordPress renders but whose editor schema disagrees with it still shows a validation prompt the next time a person opens the page.
• Some block-locking patterns (locked templates, restricted block transforms) are honored at write time but not surfaced as a tool-level error yet.
• Synced patterns inserted as references update on the next page render, no live preview from the MCP side.

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