## TL;DR

Get listed on agent-specific directories by finding them through agent communities and awesome lists, checking each one's inclusion criteria (many require an API, MCP server, or agent-readable docs), and writing the listing for agent operators: what the tool does, how an agent calls it, and what it costs per use. Operators skim for integration facts, not marketing.

```text
how to get listed on agent-specific directories
```

## Use this when

- Your tool is usable by AI agents and you want agent-operator distribution
- Building a submission list beyond general devtool directories
- The tool has an API, MCP server, or CLI agents can call

## Not for this skill when

- The tool has no agent-usable interface (fix the product first)
- The "directory" is a link farm with no real audience
- You are not ready to support agent users (docs, rate limits, auth)

## Steps

1. Find the directories. Agent communities, awesome-agent lists, and "AI agent tools directory" searches surface them; they cluster around MCP, agent frameworks, and tool discovery. Expected: a candidate list of real, maintained directories.

2. Check inclusion criteria per directory. Many require a working API endpoint, an MCP server, or machine-readable docs; some require the tool to be free or have a free tier. Expected: you know the gate before you apply.

3. Prepare the agent-facing kit. Beyond the standard listing kit, add: auth method, rate limits, pricing per call where relevant, and a link to agent-readable docs. Expected: an operator can evaluate integration in two minutes.

```
agent directory kit adds:
  auth:        [method, e.g. API key]
  interface:   [REST API / MCP server / CLI]
  rate limits: [published limits]
  agent docs:  [URL]
  pricing:     [per-call or tier info]
```

4. Write the listing for operators. Lead with what an agent can do with the tool and how it connects; skip the vision statements. Expected: copy a builder can act on.

5. Submit, log, and monitor for agent signups. Tag URLs and watch for the operator audience specifically. Expected: you learn which agent directories convert.

## Variant phrasings

### AI agent tool directories list

Found via agent communities and awesome lists; each has its own inclusion criteria.

### submitting to agent tool directories

Standard kit plus auth, interface, rate limits, and agent-readable docs.

### directories for MCP servers and agent tools

Check for API or MCP requirements first; write listings for operators, not buyers.

## Why it happens

Agent-specific directories serve builders choosing integrations, a different audience with different questions than general devtool directories. Listings that answer "how does my agent call this and what does it cost" win; listings that answer "our vision for the future" get skipped.

## Edge cases / pitfalls

- Some directories list only open-source tools; check before investing in the kit.
- Keep the agent docs URL stable; directories link to it for years.
- If your API changes, update these listings first; broken integration docs burn trust fast.
- Watch for directories that charge agents or operators; know the model before listing.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ZW_UYRybqIa5XDxqtotr7w