Integrations

ACF

Structured content your AI can scaffold and fill, without the usual footguns.

Structured content the AI can scaffold and fill, without the usual footguns. Describe the fields you need in plain English and your AI builds whole field groups, sets values on posts, and keeps ACF's own JSON sync in step.

What it does

Ask your AI for structured content and it works through ACF's own model. It can create a whole field group in one pass, use any of ACF's field types, and write field values onto your posts and pages. JSON sync stays in step as it goes.

Whole field groups in a single pass, location rules included.
All ACF field types, from text and image to relationship and link.
Field values written onto posts, pages, and other content.
JSON sync kept current so your field definitions can live in version control.
On ACF Pro, custom post types and taxonomies registered through ACF, plus options pages.

Coming soon

Screenshot of the AI building an ACF field group with a hero headline, image, and CTA link, shown next to the resulting ACF field group editor.

How it works

Every write goes through ACF's own functions, so its hooks and JSON sync fire the same way they would if you built the field by hand. Nothing is poked into the database behind ACF's back.

A built-in guard always resolves a field reference to its canonical key before writing a value. That means the silent key versus name corruption (where a value saves against the wrong reference and quietly disappears) cannot happen from the MCP layer.

Location rules are validated before the group is saved, so you never end up with a field group that saves cleanly but never shows up anywhere. If a rule cannot match, your AI tells you instead of leaving a silent no-op group.

Register any single post type on exactly one surface: ACF, or JetEngine, or WordPress core. Never two at once. Two registrations for the same post type collide and produce confusing results. Your AI follows this rule, so pick one home for each post type and stay there.

Trigger the AI

Talk in plain English. Here are prompts you can paste straight into your MCP client.

Add a field grouptext

Add a field group to the Page editor with a hero headline, subheadline, background image, and a CTA link.

Repeater scoped to one page (needs ACF Pro)text

Create a repeater for team members with name, role, and photo, shown only on the About page.

Repeater fields need ACF Pro. See the Requirements section below for the full list of what each tier covers.

Set a field valuetext

Set the hero headline on the homepage to "Build faster with BuildPress".

Coming soon

Short walkthrough of asking the AI to add a hero field group to the Page editor, then setting the hero headline value on the homepage and verifying it renders.

Requirements

You need one of ACF Free, ACF Pro, or SCF (Secure Custom Fields) installed and active. The integration auto-detects the plugin and only registers its tools when one is present.

ACF Pro is required for the following:

Repeater, flexible content, clone, and gallery fields.
Options pages (ACF Pro 6.2 and up).
The post-type and taxonomy tools that register custom post types and taxonomies through ACF (ACF Pro 6.1 and up).

Building a content site

ACF is one path for modeling a content site. JetEngine is the primary path and ACF or ACF Pro is the fallback. See the content site guide for the full flow, from registering a post type to building the archive and single templates.

Read the full step flow in Build a content site.