Manage post types, taxonomies, meta groups, and option pages via the ACPT framework.
ACPT keeps its post types, taxonomies and meta groups in its own registry. Reading that registry is what lets an agent extend your model instead of guessing at it.
List what ACPT already registers, then add new types with their labels and supports.
Read and create taxonomies, bound to the post types you name.
Meta groups and their boxes are read from ACPT, then extended.
Type names and field keys come from your install, never invented.
Registrations go through ACPT so they behave as they do in the admin.
No exports, no SQL, no brittle scripts — just protocol.
Ask in plain language and the ACPT integration turns it into typed calls against the ACPT registry — post types, taxonomies and meta groups.
Turn a brief into post types, taxonomies and meta groups in one pass.
See what is actually registered rather than what the documentation says.
Add fields and taxonomies to an existing model without touching what is there.
Chain ACPT changes into multi-step agent workflows.
The NibWP ACPT integration exposes the Advanced Custom Post Types framework to any MCP-compatible AI agent — Claude, Cursor, Claude Code and others. Post types, taxonomies and meta groups become typed tool calls.
ACPT holds its own registry of what a site models. Because an agent can read that registry first, it extends the structure you already have rather than inventing parallel names that only look right.
Scaffold the types and fields from a description, check the registry, then fill the model with real content — all without leaving the conversation.
| Tool | Type | What it does |
|---|---|---|
| list_post_types | read | Every post type ACPT registers, with its configuration. |
| create_post_type | write | Register a post type with labels, supports and settings. |
| list_taxonomies | read | Taxonomies and the post types they are bound to. |
| create_taxonomy | write | Register a taxonomy against one or more post types. |
| list_meta_groups | read | Meta groups with their boxes and fields. |
| create_meta_group | write | Define a meta group and the fields inside it. |
Yes. Once ACPT is active, NibWP detects it and its abilities go live instantly — no configuration needed.
No. It works alongside it. Anything created through an agent appears in the ACPT screens exactly as if you had built it there.
Yes, and that is the point — an agent that can read your registry extends your model instead of guessing at names.
No. The ACPT integration works on the Pro plan. Pro Skills are for design-to-build builder output.
Activate the integration and it's live on your MCP endpoint instantly.