Know what a page edit will change
MCP Abilities – Block Editor gives your AI client the page structure
Move a registration section, reuse a contact block or update a shared pattern. Start by reading the page’s blocks and finding where the content is used.
One change can appear on several pages
An event page has a contact section. Is it ordinary content on that page, or a synced pattern used by other events? The answer determines where an edit will appear.
Ordinary blocks: the content belongs to that page. A synced pattern: the page refers to a shared object. Change that object and every reference can show the change.
Ask the client to inspect the pattern and find its usage before changing a deadline, address or button. A date meant for one event should not spread to the others.
One shared source, three references. Check those relationships before editing the source.
A form is a group of working parts
Suppose the registration form should follow the programme. Its fields, submit button and enclosing block need to remain together. The venue details should stay in their own section.
Read the current tree, identify the enclosing form block and inspect the proposed result. Moving visible text alone does not establish that the form still has its fields or correct destination.
The client can return a changed block document for review. Saving is a separate action. Compare the complete result with the current page before writing it.
The fields and button belong inside the form. Review the complete unit when changing its position.
From a specific request to a checked page
1. Read the current content
Name the exact page. Inspect its blocks, the available block types and existing patterns. Identify the section to change and the content that must remain.
2. Prepare the edit
Use the site’s existing components. Inspect shared references first. Generation and transformation abilities return proposed content; creation and update abilities write WordPress objects.
3. Review before saving
Check the block structure, headings, links and media. Resolve errors and compare the full document with the original. Automated findings support this review but do not replace it.
4. Check what visitors receive
Open the saved page on desktop and mobile. Follow its buttons and inspect the reading order. If form submission testing is part of the task, test it separately with suitable test data.
Build with the components already on the site
The add-on can inspect registered blocks, styles and patterns before the client creates content. It also covers synced patterns, block-theme templates, template parts and navigation objects.
Use a normal pattern when each page needs independent content. Use a synced pattern when the content should stay shared. Inspect usage before changing shared Site Editor objects.
What you need
Install the add-on on the WordPress site you want to work on. It requires WordPress 6.9 or newer with its built-in Abilities API, PHP 8.0 or newer, and the WordPress MCP Adapter for the client connection.
The connected WordPress account needs permission to edit the selected content. Site Editor writes require permission to edit theme options. Blocks supplied by other plugins still depend on those plugins.
The plugin’s core operations run in WordPress. They do not require an external validation service. Your MCP client supplies the AI connection, and ordinary editing in WordPress remains available.
Start by reading one page
Install Block Editor and ask your client to show the current blocks and shared references. Decide what should change before choosing a write operation.