Agent Connector for WP

How ACPT's abilities are exposed through Agent Connector for WP's MCP server, with built-in audit logging

Agent Connector for WP (ACFW) is a separate plugin by Soflyy that turns a WordPress site into an MCP server, so AI agents and MCP clients can connect to it directly. This page covers how ACPT's abilities show up there. For everything else — installing ACFW, connecting an MCP client, the Connection screen, the audit log UI — see the Agent Connector for WP repository.

ACPT registers the exact same catalog of abilities described throughout this section — custom post types, taxonomies, meta field groups/boxes/fields, field values, option pages, forms, and dynamic blocks — through Agent Connector's own MCP server, in addition to the plain WordPress Abilities API integration. You don't get a different set of abilities or a different schema; you get the same ones, reachable from any MCP client connected to Agent Connector instead of only from code running inside WordPress.

Enabling it

There's no separate ACPT setting for this. If Agent Connector for WP is installed and active on the site, its abilities are on — activating/deactivating that plugin is the opt-in. This is deliberately different from the plain Abilities API integration, which has its own Enable Abilities API toggle under Content settings.

What's different from the plain Abilities API integration

Both integrations register abilities from the same source — ACPT's internal ability registry — but Agent Connector's own registration function changes a few things on the way in:

• Permission check. ACPT's per-ability capability check (manage_options for content-model abilities, edit_posts for content-data abilities — see Permissions) is not used here. Agent Connector forces its own admin/super-admin gate on every ability it registers, regardless of category.

• Audit logging. Every call made through Agent Connector's MCP server is wrapped and recorded by ACFW's audit logger, so you get a call-by-call log of what an agent actually did — including the input it sent.

• MCP exposure. Agent Connector marks every ability public for MCP and show_in_rest, so all of it is discoverable from an MCP client out of the box.

Everything else — the request/response envelope, error codes, read/write/destructive/idempotent annotations — is identical to what's documented in How it works.

If both the plain Abilities API integration and Agent Connector for WP are active at once, Agent Connector reclaims ownership of every ACPT ability so its audit logging and MCP exposure still apply, even though the plain integration normally registers first during boot. In practice this means: whenever Agent Connector for WP is active, its behavior (forced permission check, audit log) is what governs ACPT's abilities — not the plain integration's.

Requirements

• Everything listed under Requirements for the plain Abilities API integration still applies — Agent Connector's registration function is a thin wrapper around the same WordPress-core wp_register_ability(), so WordPress 6.9+ is required either way.

• The Agent Connector for WP plugin, installed and active.