Documentation

Developer API

Agent Connector exposes abilities registered through the standard WordPress Abilities API over MCP. Any ability registered with core wp_register_ability() is exposed to your connected agent over MCP automatically, as long as mcp.public is set to true.

Every exposed ability shows up on the Abilities screen.

Register through Agent Connector

Whichever way you register, Agent Connector’s protections apply: every MCP-exposed ability gets its super-admin permission check, the domain lock (when enabled), and audit logging (when configured) — even if you supply your own permission callback, it is overridden. The helper agent_connector_for_wp_register_ability() is a convenience on top: it flips on MCP exposure for you and accepts a summarize callback that redacts sensitive input before it reaches the audit log.

agent_connector_for_wp_register_ability(
  'my-plugin/do-thing',
  array(
    'label'            => 'Do Thing',
    'description'      => 'Does the thing.',
    'execute_callback' => fn( $input ) => array( 'message' => 'done' ),
  )
);

Opting out of governance

By default, every MCP-public ability is governed, no matter who registered it. If an integration deliberately needs to manage its own protections, the agent_connector_for_wp_govern_ability filter exempts a named ability:

add_filter( 'agent_connector_for_wp_govern_ability', function ( $govern, $name ) {
  return 'my-plugin/do-thing' === $name ? false : $govern;
}, 10, 2 );

For the full guide, see Registering abilities with Agent Connector on GitHub.

← All documentation