Integrations / Advanced Custom Fields

Governed integration

Advanced Custom Fields (ACF) MCP abilities

7 governed ACF abilities for AI agents. They appear on your WordPress MCP server only while Advanced Custom Fields is active, and stay off until you enable them. Read and write ACF field data.

7 governed abilities Requires Advanced Custom FieldsGuarded write

Reaches real personal data

This set can read real customer or field data, so it sits behind a clear admin notice before you enable it. It stays off until you switch it on, runs only for the capabilities of the user you connected, and nothing is sent anywhere: your AI client reads the data it asked for, and the plugin makes no outbound calls of its own.

  • Active only while Advanced Custom Fields is installed and active
  • Off by default, enabled one ability at a time
  • Capability-gated on every call, discovery and execution separately
  • Logged like core, denials included, keys and identifiers, never free-text

How to turn it on

Activate Advanced Custom Fields, then open the Agent Abilities for MCP screen and enable the Advanced Custom Fields abilities you want. Connect your client to the endpoint on the Connection tab. The address below is illustrative; your real one shows there.

Illustrative endpoint (your real one shows on the Connection tab)https://your-site.com/wp-json/…/mcp

Try it with a prompt

Example requests you could paste to your agent once Advanced Custom Fields abilities are on.

  1. List the ACF field groups so I can see which custom fields exist and their types.
  2. Read the custom fields on post 214 and tell me which ones are still empty.
  3. Set the subtitle and reading time custom fields on post 214.
  4. Fill in the ACF fields on the Guides category term.

These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.

Back to all integrations

Add Advanced Custom Fields, keep the same control.

Every integration ability is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.

Active only while its host plugin is on, and gated like core.