Manage Pods, custom post types, advanced content types, add fields, list/create/update items.
Pods can model post types, taxonomies, settings pages and its own Advanced Content Types. Building one is a long sequence of admin screens; describing one is a sentence.
Post types, taxonomies, settings pages and Advanced Content Types are all reachable.
Read a Pod with its field definitions, then add fields with the right types and options.
List, create and update items through the Pods API, including ACT rows in their own tables.
Pod names and field keys are read from your install, never guessed.
Writes run through Pods so values land in the shape it expects.
No exports, no SQL, no brittle scripts — just protocol.
Ask in plain language and the Pods integration turns it into typed calls against the Pods API — Pods, fields and items.
Describe the content you need and get a Pod with its fields, ready to fill.
Populate a field across every item in a Pod at once.
Find items with gaps or inconsistent values and fix them in place.
Chain Pods actions into multi-step agent workflows.
The NibWP Pods integration exposes Pods to any MCP-compatible AI agent — Claude, Cursor, Claude Code and others. Pods, their fields and their items become typed tool calls instead of a sequence of admin screens.
Pods models more than custom post types. Settings pages and Advanced Content Types store data outside the post table entirely, and items in those tables are invisible to the standard WordPress REST API. Reading and writing through the Pods API keeps all of it reachable and correctly validated.
Describe the structure you need, get a Pod with its fields, then seed it with real items — without leaving the conversation.
| Tool | Type | What it does |
|---|---|---|
| list_pods | read | Every Pod with its type and label. |
| get_pod | read | One Pod with its full field definitions. |
| create_pod | write | Create a Pod — post type, taxonomy, settings page or Advanced Content Type. |
| add_field | write | Add a field to a Pod with its type and options. |
| list_items | read | List items belonging to a Pod. |
| create_item | write | Create an item through the Pods API. |
| update_item | write | Update an existing item. |
Yes. Once Pods is active, NibWP detects it and its abilities go live instantly — no configuration needed.
Yes. ACTs store rows in their own tables rather than the post table, and items are read and written through the Pods API so those tables are handled correctly.
Yes. Fields are added with their type and options, so a Pod can be modelled end to end in one conversation.
No. The Pods integration works on the Pro plan. Pro Skills are for design-to-build builder output, which is a different job.
Activate the integration and it's live on your MCP endpoint instantly.