Abilities and MCP

On WordPress 6.9 and newer, Octa Editor registers native Abilities. This gives agents an MCP surface without going through the REST API directly. Each ability is a thin adapter over the same pipeline, so the rules match every other surface.

The abilities

Ability	Kind	Purpose
octa-editor/get-document	read	Read a single record as the canonical document.
octa-editor/list-records	read	List records the caller may access, scoped anti-oracle.
octa-editor/save-document	write	Create or update a record (upsert), with dry-run support.

Defaults

The defaults favour safety.

• The two read abilities are MCP-public by default.
• save-document is off by default. Writing over MCP has to be enabled deliberately.

Enable writing with the octa_editor_ability_mcp_public filter.

add_filter( 'octa_editor_ability_mcp_public', function ( $public, $ability ) {
  if ( 'octa-editor/save-document' === $ability ) {
    return true;
  }
  return $public;
}, 10, 2 );

Same rules everywhere

Because the abilities wrap the same Data layer as the REST API, everything you know from the rest of the docs still applies. Identity comes from _match, _dry_run previews a write, _strict enforces validation, and warnings use the same octa_* codes. See Record identity and Dry-run, strict & warnings.