list_directories
List directories you own (only tool named explicitly)
LABSCO SUMMARY
A header that pins the connection to one directory is worth using even though it is optional.
If you run several directories, a connection that can reach all of them is a wider grant than the work usually needs. Setting X-Directory-ID at configuration time means an agent working on one site cannot wander into another — the same instinct as DigitalOcean's per-service endpoints, done with a header instead of a hostname.
What it is
Directify's endpoint for their directory-building product. Four tools by their documentation, of which one is named: listing the directories you own.
What you get
list_directories is the tool named explicitly; the other three are documented as a group. An X-Directory-ID header narrows the connection to a single directory.
Requirements
A bearer API token with an optional X-Directory-ID header, or OAuth for clients with native remote support.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Seeing what you own
List the directories on the account before doing anything.
02
Working on one site only
Pin the connection with the directory header so the others are out of reach.
4 tools
Listed in project docs. Your client may show a different list.
(area) Listings
list, get, create, update, delete, bulk-create, check-exists, set custom field values, link organizers
(area) Categories / Tags / Custom Fields / Organizers
list, get, create, update, delete each
(area) Articles / Custom Pages
list, get, create, update, delete, toggle published
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- Bearer API token + optional X-Directory-ID header, or OAuth for native remote MCP clients
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.directify.app/mcpRequirements
- Bearer API token + optional X-Directory-ID header, or OAuth for native remote MCP clients
