A GTM tech stack is every system a revenue team sells through, from the data that starts a conversation to the document that closes it. In this directory it is 15 layers and 293 tools, and the interesting question about a stack is no longer what is in it but how much of it anything can call.
Most stack diagrams are drawn by category because that is how software is sold. An agent does not experience it that way. It experiences a chain of doors, and the chain is only as good as its locked link.
| Layer | Tools | Official MCP | Community | Reachable |
|---|---|---|---|---|
| RevOps Infra | 23 | 22 | 0 | 96% |
| Data & Enrichment | 38 | 31 | 2 | 87% |
| Conversation Intel | 24 | 17 | 3 | 83% |
| Signals & Intent | 28 | 17 | 1 | 64% |
| Video Prospecting | 14 | 3 | 6 | 64% |
| Engagement & Outbound | 27 | 15 | 2 | 63% |
| Scheduling & Routing | 14 | 6 | 2 | 57% |
| MCP Layer | 13 | 7 | 0 | 54% |
| Proposals & Deals | 14 | 7 | 0 | 50% |
| Inbound & PLG Chat | 15 | 5 | 0 | 33% |
| Email Deliverability | 13 | 4 | 0 | 31% |
| AI SDRs | 23 | 4 | 2 | 26% |
| Community & Dark Social | 16 | 2 | 2 | 25% |
| Forecasting & Revenue | 17 | 3 | 0 | 18% |
| Enablement & Coaching | 14 | 1 | 1 | 14% |
Counted 2026-08-25. Totals sum to 293 entries, which includes 16 products deliberately listed in two categories.
The top of that table is the infrastructure and data layers, where the API was always the product. The bottom is where the interface is the product: enablement, forecasting, community. The category sold hardest on autonomy, AI SDRs, sits well down it with 4 official servers out of 23.
If you are assembling a stack an agent can drive, build it from the top of that table down. The bottom is where you will still be writing glue, or clicking.
Reachable is not the same as available. 45 entries need a contract before anybody gets an API key. Cross those two columns before you plan anything: the list you actually get to build with is the 117 entries that have a server and are free to start or paid self serve.
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.