An agent can discover ACF field groups, custom post types, and custom taxonomies that the site owner has opted into AI access, then list, read, create, update, and delete items of those content types along with their custom field values.
View Advanced Custom Fields on WordPress.org
ACF must be installed and active on WordPress 6.9 or later, with Enable ACF AI turned on in its settings. Listing and registering field groups, post types, and taxonomies checks ACF's own configurable admin capability (acf_get_setting('capability'), manage_options by default), while the generated per-type query, create, view, update, and delete abilities check the underlying post type or taxonomy's own capabilities (read, create_posts, edit_posts, delete_posts, or manage_terms).
Beyond what the Bridge discovers here, Agent Abilities for MCP also maintains its own built-in integration for Advanced Custom Fields, which we build and keep up to date ourselves rather than read from Advanced Custom Fields's code. See the built-in Advanced Custom Fields abilities.
6 abilities are fixed (list/register field groups, post types, taxonomies); the other 10 are generated per registered, AI-access-enabled, REST-visible custom post type and per custom taxonomy (5 abilities each: query, create, view, update, delete), so the real total on a given site varies. The rows below show the fixed abilities plus one representative row per templated shape.
Grouped by what each one can change. Every one starts off until you enable it.
Lists ACF field groups that have AI access and REST exposure turned on.
Lists ACF-registered custom post types.
Lists ACF-registered custom taxonomies.
Lists items of one AI-exposed custom post type, including its ACF field values. Templated per post type, e.g. acf/books.
Reads one item of an AI-exposed custom post type by ID. Templated per post type.
Lists terms of one AI-exposed custom taxonomy. Templated per taxonomy.
Reads one term of an AI-exposed custom taxonomy by ID. Templated per taxonomy.
Creates a new ACF field group schema with field definitions.
Registers a new custom post type definition through ACF.
Registers a new custom taxonomy definition through ACF.
Creates a new item of one AI-exposed custom post type. Templated per post type.
Updates one item of an AI-exposed custom post type. Templated per post type.
Creates a new term in one AI-exposed custom taxonomy. Templated per taxonomy.
Updates one term of an AI-exposed custom taxonomy. Templated per taxonomy.
Deletes one item of an AI-exposed custom post type. Templated per post type.
Deletes one term of an AI-exposed custom taxonomy. Templated per taxonomy.
No abilities match that search.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Advanced Custom Fields registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from Advanced Custom Fields starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Conditionally. ACF's whole Abilities API integration is off by default: it only loads at all once the plugin's own 'Enable ACF AI' setting is turned on, and even then a field group, post type, or taxonomy only gets abilities once its own 'Allow AI Access' toggle is also on and it is REST-visible.
The site-wide 'enable_acf_ai' ACF setting must be turned on; it defaults to off, and no abilities register at all until then.. Each ACF field group needs its own Allow AI Access setting turned on, and show_in_rest enabled, before its fields are exposed to any ability.. A custom post type or taxonomy must be active, have its own Allow AI Access flag turned on, and be REST-visible before ACF generates the query/create/view/update/delete abilities for it..
ACF must be installed and active on WordPress 6.9 or later, with Enable ACF AI turned on in its settings. Listing and registering field groups, post types, and taxonomies checks ACF's own configurable admin capability (acf_get_setting('capability'), manage_options by default), while the generated per-type query, create, view, update, and delete abilities check the underlying post type or taxonomy's own capabilities (read, create_posts, edit_posts, delete_posts, or manage_terms).
An agent can list and inspect tables, charts and media on the site, read the plugin's system info, licence tier and changelog, and create or edit Simple tables and charts, upload images from a URL, and update table, chart, or global plugin settings.
An agent can list, read, create, update and delete docs, doc categories/tags/glossary terms, FAQs and FAQ groups, attach FAQ groups to a doc, read per-doc view analytics, read the plugin's status, and read or update its settings.
An agent can read and set whether the featured image is hidden on a post's singular view, do that in bulk across a list of posts, and check which public post types the plugin is currently enabled on.
Verified from Advanced Custom Fields's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, WP Engine or Advanced Custom Fields. Back to the full directory.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.