The useful distinction
Keep each result at the scope that owns it
A design request becomes easier to control when its scope is explicit before a change is made: site-wide, reusable, or local.
01
Site-wide result
A rule meant to affect the whole site belongs with the theme surface, where its reach can stay intentional across the site.
02
Reusable result
A shared element or panel belongs in reusable structure, so a correction can serve the places that depend on it.
03
Local result
A block or page detail should remain local when the result is meant for one context, keeping a narrow correction from changing unrelated content.
Before any change
Map the controls the site exposes
Start with the surface, not the symptom: establish which controls exist and which reusable starting points are available before deciding what to change.
Inventory the control surfaces
List the GeneratePress controls, setting keys, options, modules, module settings, Elements, and overlay panels. List the GenerateBlocks controls and options, and read the product information that identifies the available surface.
Read the current design state
Read GeneratePress settings, typography, theme modifications, module settings, options, blog-archive settings, custom CSS, page metadata, and individual Elements. Read GenerateBlocks global styles and options before choosing a mutation.
Find patterns and page signals
List GenerateBlocks pattern categories and libraries, search those libraries for a reusable starting point, and audit duplicate headlines, featured-image sizes, and page-layout metadata.
A controlled change
Move from evidence to one deliberate result
Use this order as operator practice. The plugin exposes the operations; the person responsible for the site chooses the intended change and confirms the result.
01
Connect the authenticated WordPress surface
Make the plugin’s WordPress ability surface available to the authenticated AI client before it acts on the site. The client can then work through the controls the site exposes.
02
Choose the owning surface
Decide whether the result belongs to global design, a reusable structure, GenerateBlocks, or one page; use the current-state evidence to select the narrow owner before mutation.
03
Apply the narrow change
When the owner is clear, update GenerateBlocks global styles or options. At the GeneratePress level, update settings, global design settings, typography, theme modifications, modules, module settings, options, or blog-archive settings; update page metadata or custom CSS, or patch only part of that CSS. Create, update, delete, or restore a GeneratePress Element; attach a menu item to a mega menu; create or update a block Element or overlay panel; and regenerate featured-image sizes when the asset dimensions are the problem.
04
Refresh and verify the generated result
Inspect the current Site Library cache state when generated output may be stale. Clear the GenerateBlocks cache, GeneratePress cache, custom-CSS cache, or Site Library cache when the corresponding output needs refreshing, then confirm the frontend result after the change.
The boundary
WordPress keeps permission and site policy in charge
The plugin exposes reusable GeneratePress and GenerateBlocks controls through WordPress. It does not choose the site’s presentation policy, invent a design system, or make every vendor feature available.
Administrative GeneratePress operations remain behind WordPress’s manage_options capability. An authenticated AI assistant can request only what that permission boundary permits, so control stays with the site’s policy.
Before you start
Use the runtime that owns the WordPress controls
These named components provide the runtime, native ability registration, and authenticated MCP transport the plugin needs.
6.9 or later
WordPress 6.9Supplies the native WordPress runtime and theme settings APIs used by the add-on.
8.0 or later
PHP 8.0Provides the minimum PHP runtime for the add-on.
Active in the WordPress installation
WordPress Abilities APIRegisters the native abilities that the add-on exposes to an AI assistant.
Active for the authenticated MCP connection
WordPress MCP AdapterTransports the registered WordPress abilities to authenticated MCP clients.
The next useful step
Download it for one focused WordPress design change
Download MCP Abilities – GeneratePress when you have one concrete GeneratePress or GenerateBlocks result to change. The ZIP gives an authenticated AI assistant the native WordPress controls for that change, while the site’s permissions and presentation policy stay in charge.