Advanced Custom Fields is one of the plugins NIBWP turns into a set of typed, agent-callable tools. Agents understand Advanced Custom Fields and can safely operate on it at scale — something no generic AI can do. The moment Advanced Custom Fields is active on your site, NIBWP detects it, reads its data model, and exposes it over the same secure MCP endpoint as everything else — no exports, no SQL, no brittle glue scripts. An AI agent connected through NIBWP can then read and operate on Advanced Custom Fields data through schema-validated calls that are scoped to your token and recorded in the audit log.
That means the work you used to do by clicking through Advanced Custom Fields’s admin — creating records, updating fields, fixing data across hundreds of items — becomes something you can describe in plain language and have an agent carry out, safely and in bulk.
Agents understand Advanced Custom Fields and can safely operate on it at scale — something no generic AI can do. Active plugin in, typed tools out — read and write Advanced Custom Fields through any connected MCP client, with scopes, draft-mode and an audit log keeping it safe.
Your custom-fields layer, programmable
Connecting Advanced Custom Fields to your agents changes what is possible with it:
- Structured access — Read and write Advanced Custom Fields data through typed, schema-validated calls.
- Bulk operations — Apply changes across hundreds of records in one operation.
- Full management — Create, update and configure Advanced Custom Fields — not just read it.
- Dynamic data — Feed Advanced Custom Fields values into templates, query loops and other tools.
- Safe by default — Scoped tokens and draft-mode keep large edits under control.
- Zero glue code — No exports, no SQL, no brittle scripts — just protocol.
What it exposes
NIBWP turns Advanced Custom Fields into the following typed abilities. Read tools gather context; write tools make changes — always within your token’s scope.
| Ability | Type | What it does |
|---|---|---|
nibwp/acf-list | read | List Advanced Custom Fields records via typed MCP calls. |
nibwp/acf-get | read | Read Advanced Custom Fields records via typed MCP calls. |
nibwp/acf-create | write | Create Advanced Custom Fields records via typed MCP calls. |
nibwp/acf-update | write | Update Advanced Custom Fields records via typed MCP calls. |
nibwp/acf-configure | write | Configure Advanced Custom Fields records via typed MCP calls. |
nibwp/acf-delete | destructive | Delete Advanced Custom Fields records via typed MCP calls. |
From hours to one prompt
Ask in plain language and the Advanced Custom Fields integration turns it into a couple of typed calls — no exports, no SQL, no plugin spelunking.
nibwp/acf-manage (run)
✓ applied · 8 tools · 2.1sYou describe the outcome; the agent chooses the right tools, validates each call, and reports what it did. What used to be an afternoon of repetitive admin becomes a single instruction.
What you can build
A few of the things teams do with the Advanced Custom Fields integration:
Bulk backfills
Populate or update a field across an entire dataset at once.
Content generation
Have an agent draft and fill structured Advanced Custom Fields data from a brief.
Audits
Find empty or inconsistent records and fix them in place.
Automation
Chain Advanced Custom Fields actions into multi-step agent workflows.
How it stays safe
Capability without control is a liability, so NIBWP wraps every Advanced Custom Fields call in the same safety model as the rest of the platform:
- Scoped tokens — grant read-only or write access per agent, and revoke any token independently.
- Draft-mode — keep force-draft on so writes land as drafts you approve before they go live.
- Rate limits — per-token throttling stops a runaway loop from hammering your database.
- Audit log — every call is recorded with status, timing, the calling token and the result.
Getting started
Three steps to put the Advanced Custom Fields integration to work:
- Activate Advanced Custom Fields — NIBWP only exposes plugins that are active, and detects it automatically.
- Connect an MCP client — Claude, Cursor or your own code, using a scoped application-password token. See the overview.
- Describe the work — ask the agent what you want; it picks the right Advanced Custom Fields tools and carries it out under your review.
FAQ
Does it work with Advanced Custom Fields?
Can it write, not just read?
Is bulk writing safe?
Do I need a Pro Skill?
Connect Advanced Custom Fields
Activate the plugin, connect an MCP client, and let agents operate it safely.
Browse integrations