ASE + MCP: let AI manage Admin and Site Enhancements custom content and fields

ASE is the Swiss-army knife a lot of agencies install on every site, and its content-model modules — custom field groups, custom post types, custom taxonomies — quietly replace two or three other plugins. NibWP exposes those modules as typed tools: list what exists, create what is missing, and read and write values through ASE so field types behave in the admin as they should.

That makes the same conversation work on every client site that runs ASE: 'a Testimonial type with author, company, rating and a Service taxonomy' becomes registered structure, and 'fill the rating field for every testimonial that has none' becomes a bulk backfill with a plan you approve.

Admin and Site Enhancements is one of the 45+ integrations inside NibWP's WordPress MCP server — 8 typed Admin and Site Enhancements tools on top of 190+ WordPress tools. The full tool reference lives on the Admin and Site Enhancements integration page; this page is about what those tools let you do.

What AI can do in Admin and Site Enhancements

The Admin and Site Enhancements tools NibWP exposes

Every Admin and Site Enhancements 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 ASE field group with its fields.
• create_field_group — Define a field group and its fields.
• list_post_types — Post types registered through ASE.
• create_post_type — Register a post type with labels and supports.
• list_taxonomies — Taxonomies and their bound post types.
• create_taxonomy — Register a taxonomy.
• get_values — Read field values for a post.
• update_values — Write field values through ASE rather than raw meta.

Example prompts

Plain English is the interface. These are the kinds of requests agencies run against Admin and Site Enhancements every day:

• “Create a 'Testimonial' post type with author, company, rating and quote, plus a 'Service' taxonomy.”
• “List every ASE field group and which post types use it.”
• “Set rating to 5 on every testimonial that has no rating.”
• “Add an 'external URL' field to the Partner field group.”
• “Which posts of type FAQ have an empty answer field?”

How it works with Admin and Site Enhancements

There is no new dashboard to learn. You describe an outcome, NibWP plans it, and you approve before anything is written.

1. Connect — install NibWP, connect Claude, Cursor, ChatGPT or any MCP client. Admin and Site Enhancements is detected automatically and its tools appear in the client.
2. Describe — describe the type, field group, taxonomy or backfill. NibWP lists what ASE already registers and reads current values before writing.
3. Approve — NibWP shows the plan: which records it will create or change, and what will stay untouched. Nothing happens until you say yes.
4. Done — it writes real Admin and Site Enhancements 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 Admin and Site Enhancements; it cannot safely operate it. The difference is structure, context and control.

A generic assistant

• Writes PHP snippets or raw post meta ASE fields do not recognise
• Does not know which groups and types ASE already registers
• Cannot do a backfill without an export and a re-import

Admin and Site Enhancements + NibWP

• Registers types, taxonomies and groups through ASE's modules
• Reads and writes values through ASE with field types respected
• Runs backfills and audits in place, with a plan first

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 Admin and Site Enhancements's own functions and APIs — your data stays on your server, nothing is copied to a third-party service.
• Creating a group, type or taxonomy adds one; value updates touch only the fields you name. Large writes can run in draft mode and are rate-limited.

Related integrations

Most sites pair Admin and Site Enhancements with other plugins NibWP already speaks: Meta Box + MCP, ACF + MCP, Pods + MCP, ACPT + MCP, WordPress + MCP, JetEngine + MCP. All of them ship in the same plugin — see pricing for what each plan includes.