Manage a full business directory: listings, categories, locations, tags, reviews, orders, pricing plans, and user favorites. Publish, expire and feature listings, approve reviews, and pull directory reports.
Listings, categories, locations, tags, reviews, orders and plans all have to stay consistent with each other. That is bookkeeping — and bookkeeping is what an agent should be doing.
Create, read, update, expire and feature listings through Directorist itself.
Categories, locations and tags — read and written, so listings never point at names that do not exist.
Read, approve and remove reviews without wading through a moderation queue.
Read orders and pricing plans to see what a listing is actually entitled to.
Read and add user favorites, useful for migrations and seeded demo data.
Removing listings, terms or reviews is flagged destructive and treated as such.
Ask in plain language and the Directorist integration turns it into typed calls — listings, taxonomy, reviews, orders and plans.
Create categories, locations and hundreds of listings from a source you already have.
Listings with no photo, no location or a stale expiry — found and fixed in place.
Read pending reviews, approve the genuine ones, remove the spam.
Chain expiry, featuring and moderation into a repeatable weekly workflow.
The NibWP Directorist integration exposes a business directory to any MCP-compatible AI agent — Claude, Cursor, Claude Code and others. Listings, taxonomy, reviews, orders and plans become typed tool calls.
Directories are consistency problems. A listing points at a category, a location and a plan; a review belongs to a listing; an expiry date decides whether any of it is visible. Keeping that straight by hand across hundreds of records is slow and error-prone, which is exactly why it suits an agent.
Listings are created through the plugin’s own fields and expiry handling rather than written straight into the database, so what an agent creates behaves like what you would have created yourself.
| Tool | Type | What it does |
|---|---|---|
| list_listings | read | Listings, filtered by status, category or location. |
| get_listing | read | One listing with its fields. |
| create_listing | write | Create a listing through Directorist's own fields. |
| expire_listing | write | Expire a listing without deleting it. |
| delete_listing | destructive | Remove a listing. |
| list_categories | read | Directory categories. |
| create_category | write | Add a category. |
| list_locations | read | Locations as Directorist stores them. |
| create_location | write | Add a location. |
| approve_review | write | Approve a pending review. |
| list_orders | read | Orders behind paid listings. |
| list_plans | read | Pricing plans and what they include. |
Yes. Once Directorist is active, NibWP detects it and its abilities go live instantly — no configuration needed.
Through Directorist, so its own fields, taxonomies and expiry handling apply exactly as they would in the admin.
Orders and plans are readable, so an agent can tell you what a listing is entitled to. It does not move money at your payment provider.
Deletes are flagged destructive and sit behind a permission an ordinary read-and-write connection never gets.
Activate the integration and it's live on your MCP endpoint instantly.