Directories integration
Directories MCP
The Directories plugin registers each directory content type (its "bundles") as a WordPress custom post type, so directory listings are ordinary posts. WP MCP's content tools are post-type-agnostic: list-post-types discovers the directory bundles, list-posts lists their entries, get-post reads one listing (including its non-protected meta), and create-post / update-post add and edit listings, with every write snapshotted first. So an agent can inventory and manage directory listings with no Directories-specific integration. A regression test verifies the content tools list, read, create, and update an arbitrary custom post type.
In practice
How Directories work goes with an agent.
Directories has no adapter of its own in WP MCP, and that is a deliberate scope. Each directory content type is a registered post type, so an agent reaches listings with the same content tools it uses for any custom post type: find the type, list its entries, read one, add or edit one. What it sees is what WordPress itself stores for a post: title, content, status, terms and ordinary custom fields. Fields that the plugin keeps in its own tables are not read or written by these tools, so treat this page as listing management, not a full Directories editor.
Which post types does this site use for the business directory and the events directory?
Runs list-post-types. It shows public types by default, so the agent passes public_only:false if a directory type is missing from the answer. Read only, nothing is snapshotted.
Show me the 20 newest listings in the business directory with their status and custom fields.
Runs list-posts with the directory post type, then get-post on the ones that matter. get-post returns the post's non-protected meta only; keys that start with an underscore are skipped.
Add a draft listing for Acme Bakery with this description and tag it Bakery.
Runs create-post with the directory type and status draft, then set-post-terms for the tag. The creation is recorded in the operation ledger, and undoing it moves the post to the trash.
Fix the typo in the opening hours text of listing 842.
Runs get-post, then update-post with only the changed field. The post is snapshotted before the write, and rollback-operation restores the earlier values.
What your AI can do
Real Directories operations, every write reversible.
- Discover the directory content types (bundles) via list-post-types
- List and read directory listings as custom posts
- Create and update listings, snapshotted and reversible
- Read a listing's non-protected custom fields
Example prompts
Example Directories prompts.
What directory content types does this site have?
List the newest 20 listings in the business directory.
Create a draft listing titled "Acme Bakery" with this description.
Under the hood
The Directories calls, under the hood.
list-posts({ post_type: "<directory-bundle>" }), listings are ordinary CPT posts
create-post({ post_type: "<directory-bundle>", title: "…", meta: {…} }), snapshotted
Safety and access
What can be undone on Directories, and what costs what.
Recoverable on Directories
- update-post snapshots the post and its meta first, and rollback-operation restores them.
- create-post is recorded rather than snapshotted, because a new post has no earlier state. Undoing it moves the post to the trash, and restore-post brings it back.
- delete-post moves a listing to the trash by default, which is reversible.
Directories limits and opt-ins
- Meta keys that start with an underscore or are registered as protected are refused on write and hidden on read.
- Permanent deletion with force:true is off until a site opts in with the wpmcp_enable_delete_post filter, and it needs confirm:true.
- Data the plugin keeps in its own drts_ tables is outside these tools. A curated reader for it is not built yet.
Free or Pro: Everything here is free. The content tools that manage directory listings (list-post-types, list-posts, get-post, create-post, update-post and the rest of the core set) ship with the free plugin, and there is no Directories-specific Pro layer to buy. Pro does not add listing fields on top. If you want bulk edits across hundreds of listings, the free session rollback (rollback-session) already undoes a whole batch in one step.
In the free plugin
The Directories integration is in the free plugin.
The core Directories tools ship in the free, GPL plugin with the full snapshot and undo engine, and no trial clock. Pro adds 133 more tools, including Elementor deep editing, the other page builders, the forms adapter pack and, for some integrations, extra operations. The pricing page lists what each tier includes.
Frequently asked
Directories MCP: questions, answered.
Is there a dedicated Directories integration?
Directory listings are custom post types, so WP MCP's content tools already list, read, create, and update them, snapshotted, with no Directories-specific adapter. That core coverage is verified by a regression test against an arbitrary custom post type.
What about the plugin's extended fields?
Directories keeps some structured field data in its own drts_ tables beyond standard postmeta. Standard fields and content are covered through the content tools now; a curated reader for the plugin's extended field storage is future work, and we will not claim it until it ships.
With Directories, can the agent bulk-edit hundreds of listings?
Yes, as a series of update-post calls under one session. Each call is snapshotted separately, and rollback-session undoes the whole batch in one step. There is no directory-specific batch tool, so the agent loops over the listings it found with list-posts, and you can review the change set before keeping it.
Why does a directory type not show in list-post-types?
list-post-types returns only public post types unless public_only is false. If the Directories plugin registers a bundle as non-public, the agent asks again with public_only:false. You can also name the post type directly in list-posts or get-post if you already know its slug.
Does the Directories integration publish listings without my review?
Only if you ask it to. create-post defaults to draft, and the allowed statuses are draft, publish, pending, private and future. For a moderated directory, ask for pending, so listings sit in your review queue exactly as submitted ones would.
Related integrations
More integrations for the same agent.
MCP for BuddyPress
FreeCommunity, 2 tools.
MCP for bbPress
FreeCommunity, 2 tools.
MCP for Gravity Tables
FreeData tables, 3 tools.
MCP for Elementor
ProPage builders, 14 tools.
MCP for Gutenberg
FreePage builders, 4 tools.
MCP for Bricks
ProPage builders, 3 tools.
Browse the full Integrations hub, or read more on the WordPress MCP plugin.