← All seven roles

Composition axis

Directory MCP servers

Helps you find capabilities. Doesn't hold the data itself. It points you to the servers that do.

Example · WealthMCP

A Directory server does not hold data. It tells an agent what exists and how to connect it.

That distinction matters more than it sounds. WealthMCP can return an endpoint, a client config snippet and the caveats attached to a listing. It cannot reach through to the server it just described and pull data from it. An agent cannot connect a new server on its own mid-conversation either. The handoff is always to you: here is what to add, here is the config, add it in your client and then we can use it.

Which makes Directory the one role that is honest about being a first step. Everything else in this taxonomy does work. A Directory reduces the time between having a question and knowing which tool answers it, and it does that best when the listings carry the things a vendor page will not tell you: what the auth model actually is, whether the server can write, whether the data has known gaps.

That editorial layer is the product. The list is the easy part.

Directory servers in the directory

6 servers in this directory play this role

The other roles

Read the full role taxonomy →