The decision before a write
A successful write can still hide a bad page change
A landing-page heading may change alongside its button link, media, and surrounding blocks. Compare discovering that result after storage with reviewing it while the editor can still choose what to keep.
Before: the request succeeds
The response reports that the operation completed. The changed page is already stored, so the editor must find an unwanted relationship or visual result after the fact.
After: the change is checked
The assistant presents the altered Gutenberg result for review before storage. The editor can accept the version that preserves the intended page behavior and appearance.
A content editor’s route
Keep the approval point visible from first inspection to final authorization
Use this order when the editor needs a reasoned approval point, not only a completed request.
01
Read the page in context
Start with the existing nested Gutenberg document and inspect the surrounding authoring context. This establishes what the next operation must respect.
02
Define the block change
Tell the assistant which part of the document should change and what must remain attached. Keeping the edit scoped to the relevant block gives the later review a clear before-and-after comparison.
03
Choose what WordPress will store
Review the returned findings for the exact target, the changed result, and its place on the page. Approve only the version that meets the editor’s purpose and the site’s presentation requirements.
04
Save the version the editor chose
The assistant can save the chosen Gutenberg block state in WordPress, so the editor’s selected version becomes the document used for the next revision.
What the editor is actually changing
The tree carries the meaning of the edit
A visible heading is one node in a nested Gutenberg document. MCP Abilities – Block Editor can parse and serialize the tree, transform, lock, insert, duplicate, move, bind, edit text, normalize headings, and save it. Those operations let an AI client work on the structure behind the editor’s request.
The plugin can also generate sections, query sections, and landing pages or update an existing document. For content creation, it can inspect the active theme, block styles, registered blocks, categories, patterns, synced patterns, and reusable authoring guidance. It can read and manage block-theme templates, template parts, navigation entities, synced patterns, and their usage relationships.
Its checks cover structure, design, copy, links, media use, and rendered context. The result gives the editor specific evidence about what the page will contain and how it will appear.
After a failed check
Correct the failed condition without disturbing the rest of the page
Use the reported problem to bound the next edit. The new candidate should fix that issue and preserve everything that already worked.
Three conditions for a clean correction
The original issue no longer appears
The affected node, connection, wording, or visual effect now matches the editor’s stated intent.
Unrelated content stays intact
Blocks outside the correction keep their meaning, order, links, and media relationships.
The check reflects the corrected candidate
Repeat the relevant inspection after the edit so its findings describe the current candidate rather than the discarded one.
Review the corrected candidate only after all three conditions are true.
Required runtime
Install the runtime that connects the assistant to WordPress
The plugin depends on these named pieces. Each has one job in the path from an AI client to a block-editor ability.
WordPress 6.9 or newer
WordPress Abilities APIProvides the native ability registration layer used to expose the block-editor operations.
PHP 8.0 or newer
PHP 8.0Provides the server runtime required by the plugin.
Installed and active
WordPress MCP AdapterExposes the registered WordPress abilities to MCP clients.
The next useful step
Start with a reviewable Gutenberg change
Download the MCP Abilities – Block Editor ZIP when an AI client needs to inspect and update Gutenberg content in WordPress. The plugin gives that client the block-editor abilities for its next proposed change, so the editor can examine the result before choosing what to store.