Skip to content

For developers

Directories.ai for developers and AI builders

Directories.ai exposes a standards-based MCP server (JSON-RPC 2.0 over Streamable HTTP, OAuth 2.1 with PKCE) and a REST API, so your own agents and apps can read and manage directory data. Tools carry readOnly and destructive annotations, writes are audit-logged, and changes to your site’s code arrive as pull requests rather than direct pushes.

Start your directory Connect your AI assistant

A tool surface designed for agents

The MCP server returns usage instructions on initialize, annotates every tool with readOnlyHint and destructiveHint, and exposes guided workflows as both MCP prompts and plain tools for clients without prompt support. Tokens are scoped to a single organization and every handler checks directory ownership.

  • OAuth 2.1 with PKCE and dynamic client registration; organization API keys for static-header clients
  • Prompts: ranking_best_practices_audit, ai_era_design_review, run_playbook
  • Task queue for long-running or recurring agent work
  • Cookieless visitor tracking script and an events endpoint for server-side use

Integrations through pull requests

Site features such as claim links and visitor tracking are shipped as playbooks. The agent reads the live account setup, performs the account-side steps with MCP tools, and opens a pull request implementing the contract in your stack. Secrets are created in the dashboard and never pass through the agent.

Connect and build

  1. 1

    Connect a client

    Point an MCP client at https://directories.ai/mcp and complete OAuth, or use an API key for static headers.

  2. 2

    Explore the tools

    List directories, then call read-only tools to understand your data.

    list_directoriesget_directorylist_listings

  3. 3

    Add integrations

    Run the integration playbooks and review the pull requests they open.

    list_playbooksget_playbooksuggest_repo_change

Frequently asked questions

Is there a REST API as well?

Yes. See the API documentation for endpoints, and the MCP integration guide for client setup.

How is access scoped?

A token only reaches the directories of the organization that approved it, and OAuth tokens stop working if the approving user leaves the organization.

Can an agent push straight to production?

No. suggest_repo_change opens a pull request for a person to review and merge, and workflow files are off limits.

Keep reading

MCP integration guideStep-by-step client setup for Claude, Cursor and more.API documentationREST endpoints for reading and managing directory data.Manage a directory with MCPRun listings, categories, content and claims from Claude, ChatGPT or any MCP client.AI task board & recurring workQueue, schedule and review recurring directory work done by your own AI agent.

Ready to run your directory with AI?

MCP access is included on the Growth plan. Pay per directory, cancel any time.

Start your directorySee pricing