Directories integration

MCP for Directories

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.

Get the free plugin Read the docs

list-post-typeslist-postsget-postcreate-postupdate-post

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

Just ask.

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 real calls.

wpmcp, directories

list-posts({ post_type: "<directory-bundle>" }), listings are ordinary CPT posts

create-post({ post_type: "<directory-bundle>", title: "…", meta: {…} }), snapshotted

Frequently asked

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.

More integrations