If your CRM ships an MCP server, you add it to your client's server configuration, authenticate, and the assistant can then read and write records as tools. If it does not, you either use a community server, an automation platform that proxies tool calls, or you write a thin wrapper over the CRM's REST API yourself.
RevOps Infra is the best covered layer in this directory: 22 official servers and 0 community across 23 entries, with only 1 where none was found. Check your specific system on the RevOps tools with MCP servers list, and read the auth field on its page before anything else.
This is the step people skip and regret. The server can do whatever your credential can do, and an instruction not to write is a suggestion rather than a boundary. Create a dedicated integration user or a scoped token at the CRM, not a copy of your admin credentials. Where the vendor offers OAuth, take it: the token is scoped and you can revoke it from their side without touching your config.
A local server is a command the client launches. A remote one is a URL the client connects to, usually followed by a browser sign in. The local shape looks like this, and the exact block comes from your vendor's own documentation rather than from here.
{
"mcpServers": {
"some-gtm-tool": {
"command": "npx",
"args": ["-y", "@vendor/mcp-server"],
"env": { "VENDOR_API_KEY": "the key you generated in the vendor dashboard" }
}
}
}Ask for a record you already know the answer to. Check the field names come back the way you expect, that record ownership and permissions behave, and that the record limit on a query is what you assumed. Only then let anything write.
A CRM connection on its own is a search box. The value shows up when the assistant can also research and enrich, then write the result back.
| Step | The job | Tools tagged | Official MCP | Free tier |
|---|---|---|---|---|
| Read CRM records | read crm records | 13 | 10 | 5 |
| Write CRM records | write crm records | 28 | 17 | 7 |
| Sync records between systems | sync records between systems | 9 | 8 | 6 |
| Enrich a company from a domain | enrich a company from a domain | 34 | 26 | 12 |
| Research an account before a call | research an account before a call | 17 | 10 | 3 |
9 entries in this directory are tagged proxy tool calls to saas apps: platforms that stand between an agent and somebody's SaaS and expose the calls as tools. That is the fastest route and it puts a third party in the middle of your credential, which is a tradeoff to make deliberately rather than by accident.
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.