Meta Box + MCP: let AI model post types, field groups and relationships
Connect Meta Box to Claude, Cursor or ChatGPT through NibWP's MCP server. Describe the content model — 'a Property type with price, bedrooms, agent and a gallery' — and the AI registers the post type, the taxonomy, the field group and the relationship through Meta Box itself, then fills values the same way.
Meta Box registers post types, taxonomies, field groups and relationships as code-shaped configuration. Describing that structure is exactly what a language model is good at — if it can write through Meta Box rather than raw post meta. NibWP exposes the Meta Box API as typed tools, so field types, clones and groups behave in the admin exactly as if you had built them by hand.
That compresses the first day of a custom build into a conversation, and makes the long tail easy: backfill a field across an entire post type, find posts with empty or inconsistent values and fix them in place, relate two types that grew up separately.
Meta Box is one of the 45+ integrations inside NibWP's WordPress MCP server — 7 typed Meta Box tools on top of 190+ WordPress tools. The full tool reference lives on the Meta Box integration page; this page is about what those tools let you do.
What AI can do in Meta Box
Scaffold a content model
Post types, taxonomies and field groups from one brief — registered through Meta Box, visible in the admin immediately.
Relationships
Relate post types, users or terms to each other; Property ↔ Agent, Course ↔ Instructor, without custom code.
Field groups, typed
Text, number, image, gallery, group, clone — created with the right types and options so validation works.
Bulk backfills
Populate or normalise a field across every post of a type in one pass — prices, units, SKUs, dates.
Audits
Find posts with empty required fields, values in the wrong format or orphaned terms, and fix them in place.
Values in and out
Read and write meta through Meta Box, so clones, groups and file fields come back in the shape your templates expect.
The Meta Box tools NibWP exposes
Every Meta Box capability is a typed MCP tool with a schema the AI client can read, so it calls the right thing with the right arguments instead of guessing at your database. Read tools are free to explore; write tools go through the approval flow.
list_field_groups— Every Meta Box field group with its fields and locations.create_field_group— Define a field group and its fields.register_post_type— Register a custom post type with its labels and supports.register_taxonomy— Register a taxonomy and bind it to post types.create_relationship— Relate post types, users or terms to each other.get_values— Read meta values through Meta Box, with field types respected.update_values— Write meta values through Meta Box rather than raw post meta.
Example prompts
Plain English is the interface. These are the kinds of requests agencies run against Meta Box every day:
- “Create a 'Property' post type with price, bedrooms, bathrooms, area, a gallery and a relationship to 'Agent'.”
- “List every Meta Box field group and which post types they are attached to.”
- “Add a 'listing status' taxonomy to Property with For sale, Under offer and Sold.”
- “Find properties with no price and set them to 'Price on request'.”
- “Normalise every area value to square metres and round to whole numbers.”
How it works with Meta Box
There is no new dashboard to learn. You describe an outcome, NibWP plans it, and you approve before anything is written.
- Connect — install NibWP, connect Claude, Cursor, ChatGPT or any MCP client. Meta Box is detected automatically and its tools appear in the client.
- Describe — describe the model or the change — a new type, a field group, a backfill. NibWP lists existing groups, types and relationships first so it extends what is there instead of duplicating it.
- Approve — NibWP shows the plan: which records it will create or change, and what will stay untouched. Nothing happens until you say yes.
- Done — it writes real Meta Box data through the plugin's own APIs and reports back in plain English, with every change in the audit log.
Why not just a generic AI?
A general-purpose assistant can write text about Meta Box; it cannot safely operate it. The difference is structure, context and control.
A generic assistant
- Writes a register_post_type() snippet for you to paste into functions.php
- Writes raw post meta that Meta Box fields do not recognise
- Has no idea which field groups and types already exist
Meta Box + NibWP
- Registers types, taxonomies, groups and relationships through Meta Box's API
- Reads and writes values with field types respected
- Lists the existing model first and extends it
Safe by default
NibWP is built for agencies running client sites, so control and traceability come first:
- Nothing is written without your approval — you see the plan first, and you can run in draft mode.
- Every action is recorded in a full audit trail, per site and per user.
- It runs on Meta Box's own functions and APIs — your data stays on your server, nothing is copied to a third-party service.
- Creating a group adds one; updating values touches only the fields you name. Destructive structural changes are never part of an ordinary connection.
Related integrations
Most sites pair Meta Box with other plugins NibWP already speaks: ACF + MCP, Pods + MCP, ACPT + MCP, Admin and Site Enhancements + MCP, JetEngine + MCP, WordPress + MCP. All of them ship in the same plugin — see pricing for what each plan includes.
Questions, answered
Everything about running Meta Box with NibWP.
Do I need Meta Box installed?
Does it work with Meta Box extensions?
Can it write values, not just structure?
Will it overwrite my existing field groups?
Which NibWP plan do I need?
Model content by describing it.
Get the Bundle and let NibWP scaffold and maintain Meta Box content models — types, fields, relationships and values, with an approval step.