Manage meta boxes, Custom Content Types (CCT), options pages, and read/write dynamic content values.
Custom Content Types live in their own database tables, outside the post table entirely. An assistant that only knows WP_Query cannot see a single row of them.
CCTs sit in their own tables, invisible to WP_Query. Listing and writing rows goes through JetEngine itself.
Read every meta box with its fields and the post types it is bound to, then define new ones.
Field names and types come from your install, never guessed from a naming convention.
Seed or backfill a content type across hundreds of rows in one pass.
Creates run through JetEngine so a row lands in the shape the plugin expects.
No exports, no direct SQL against JetEngine tables, no brittle scripts.
Ask in plain language and the JetEngine integration turns it into typed calls against JetEngine's own API — meta boxes, content types and their rows.
Describe the data you need and get a CCT with its fields, ready to fill.
Import hundreds of CCT rows without touching a spreadsheet or an importer.
Find rows with missing or inconsistent fields and fix them in place.
Chain JetEngine writes into multi-step workflows your team can reuse.
The NibWP JetEngine integration exposes the JetEngine data model to any MCP-compatible AI agent — Claude, Cursor, Claude Code and others. Meta boxes, Custom Content Types and their rows become typed tool calls instead of screens to click through.
Custom Content Types are the reason this matters. JetEngine stores them in dedicated database tables that never appear in the WordPress REST API, so an assistant working through the standard API is blind to them. This integration reads and writes them through JetEngine itself, which means validation, field types and relations behave exactly as they do in the admin.
Model a new content type from a description, seed it with hundreds of rows, audit existing rows for gaps, or backfill a field across the whole set — all in plain language, all through one typed tool.
| Tool | Type | What it does |
|---|---|---|
| list_meta_boxes | read | Every JetEngine meta box with its fields and bound post types. |
| create_meta_box | write | Define a meta box and its fields against the post types you name. |
| list_cct | read | Custom Content Types and their schemas. |
| create_cct | write | Create a Custom Content Type with its field definitions. |
| get_cct_items | read | Read rows out of a Custom Content Type. |
| create_cct_item | write | Insert a row into a Custom Content Type. |
Yes. Once JetEngine is active, NibWP detects it automatically and its abilities go live in your connected AI client — no configuration needed.
Custom Content Types are not posts. They live in their own tables and never appear in the WordPress REST API, so without this integration an assistant simply cannot see them.
Both. Meta boxes, content types and their rows can all be created, and writes go through JetEngine rather than raw SQL.
No. It is one typed tool with six operations, which keeps the tool list short in your AI client while covering the whole surface. The operation is chosen per call.
Activate the integration and it's live on your MCP endpoint instantly.