An MCP server offers three kinds of thing. Tools are actions the model can invoke and that can change something. Resources are data the client can read into context. Prompts are prewritten instruction templates a user chooses. For go to market work, tools are almost always the part that matters.
Tools are functions with a name, a description and a typed argument schema. The model picks one, fills the arguments and the client executes it. Anything that finds a person, writes a record, sends a message or spends credits is a tool. Tools are model controlled, which is exactly why the approval behaviour in your client matters.
Resources are addressable pieces of context: a file, a record, a document, a query result. They are read, not run. The application decides which resources to pull into context, so they are application controlled rather than model controlled. In a GTM stack a resource is typically the account record or the transcript you want the model to reason over.
Prompts are reusable instruction templates the server publishes, surfaced in the client as something a person picks deliberately. They are user controlled. A vendor might ship a prompt for "prepare me for this call" that pulls the right resources and calls the right tools in the right order.
Three different parties decide. The model chooses tools, the application chooses resources, the human chooses prompts. That is a permission design, not a filing system, and it is the part of MCP most worth understanding before you connect an agent to anything that can send email on your behalf.
When a vendor here says it ships an MCP server, in practice that nearly always means tools: search, enrich, create, send. This directory records what the vendor documents and does not enumerate the tool surface of each server, because that would need each server to be installed and run, and 0 tools in this directory have been run by anybody here.
The closest published proxy is the job tags. 827 tags across 271 entries record what each vendor says its tool does, in the agent's own phrasing, which is the vocabulary you would expect its tools to be named after.
Every number on this page is generated from directory.json at build time and carries the date it was baked: 2026-08-25. Nothing is typed by hand, nothing is rounded, and nothing is estimated. The underlying data is published in full. Where the honest answer is a zero, the zero is printed.