Integration

Directoryz integration

Directoryz publishes searchable directories (tool stacks, local guides, resource libraries, job boards and the like) on a Directoryz URL, a custom domain or a path of an existing website. Through its workspace REST API, list, search, create, update and delete directories (name, slug, colours, layout, SEO text, draft or published) and their listings (descriptions, links, category, location, tags, featured flag and the directory's custom field values). This API covers directories and listings only: submissions, leads, analytics, webhooks and CSV import are not part of it, nor is Directoryz's separate OAuth surface, whose clients exist only through dynamic registration. Authentication is a workspace API key (dz_live_...) created in the dashboard's Workspace API settings with the permissions it needs (directories:read, directories:write, listings:read, listings:write), sent as a Bearer token. Keys are shown once, expire after 30, 90 or 365 days, and are limited to 120 requests per minute.

Connect Directoryz How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Directoryz.Built from the 10 Directoryz tools below, on the connection you add once.

What you can do with Directoryz

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Directory, 5 operations

create_directoryCreate directoryPOSTAgents: ask firstCreates a directory in the API key's workspace. status published makes it public at public_url at once. A slug left out is generated; one already in use returns 409. Needs directories:write, editor role.
delete_directoryDelete directoryDELETEAgents: ask firstPermanently deletes a directory together with all its listings. Irreversible. Needs directories:write and the owner role.
get_directoryGet directoryGETAgents: ask firstReturns one directory by UUID: name, slug, status, public_url, listing count, colours, layout, SEO fields and the custom listing field definitions (listing_fields) its listings use. Needs directories:read, viewer role.
list_directoriesList directoriesGETAgents: ask firstLists the directories of the API key's workspace, with name, slug, status (draft or published), public_url, listing count, look and SEO fields. Search with q, filter by status; paginated (meta). Needs directories:read, viewer role.
update_directoryUpdate directoryPATCHAgents: ask firstChanges the fields you send on a directory and leaves the rest as they are (send at least one). Setting status to published makes it public. Needs directories:write, editor role.

Listing, 5 operations

create_listingCreate listingPOSTAgents: ask firstCreates a listing in a directory; custom_values are validated against the directory's custom listing fields. status published shows it in the directory once that is published. Needs listings:write, editor role.
delete_listingDelete listingDELETEAgents: ask firstPermanently deletes a listing from its directory. Irreversible. Needs listings:write, editor role.
get_listingGet listingGETAgents: ask firstReturns one listing of a directory by UUID: name, slug, descriptions, links, image and icon, category, location, tags, featured flag, status and custom field values. Needs listings:read, viewer role.
list_listingsList listingsGETAgents: ask firstLists the listings of a directory: name, slug, descriptions, links, category, location, tags, featured flag, status and custom field values. Search with q, filter by category, status or featured; paginated (meta). Needs listings:read, viewer role.
update_listingUpdate listingPATCHAgents: ask firstChanges the fields you send on a listing and leaves the rest as they are (send at least one); the slug changes only when supplied. Needs listings:write, editor role.

Use Directoryz from Claude Code, Cursor or Codex

Connect Directoryz in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Directoryz operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Directoryz

Create your workspace
Sign up free. Nothing to install.
Connect Directoryz once
Add your Directoryz connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.