Which CRMs have an MCP server?

At least seven do, as of September 2026. What each server covers, and whether anything reviews a write, matters more than how many tools it lists.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

app.salescrew.io/inbox
The unified reply inbox with classified threads

The short answer

  • As of September 2026, at least seven CRMs ship an MCP server: HubSpot, Zoho, Close, Pipedrive, Affinity, NetHunt and SalesCrew.
  • Most of these vendors do not publish a tool count on their MCP documentation; they describe coverage instead, which makes the covered areas the more useful thing to compare.
  • All six competing servers here read and write records; none of their documentation describes an approval queue that holds a write for a person, so the access scope you grant is the control you get.
  • An MCP server without an approval step for external actions is a different product decision than one that queues sends for a person, and that difference does not show up in the tool count.

Why the tool count is not the whole story

Every CRM in this space says it has an MCP server once it has published even a handful of tools. That claim is true and also not very useful on its own. A server that can search contacts, read deals and add a note is a real MCP server. So is one that can also move a deal through the pipeline, draft a reply in the shared inbox, enroll a contact in a cadence and check the suppression list. The first agent can look things up. The second can run parts of the job.

The honest way to compare them is to ask for the tool list, not the tool count. Look for names, not totals: does it have a tool for changing a deal's stage, or only for reading one? Does it have a tool for sending a reply, or only for drafting one that a person still has to copy and paste? The gap between "can see" and "can do" is where most of these servers differ.

CRMs with MCP servers

Read on each vendor's own MCP documentation. Most vendors describe what their server covers rather than publishing a tool count.

CRMPublished tool countRead/writeApproval queuePlan gate
HubSpotNot published as a countRead and write on contacts, companies, deals, tickets and other objectsNone documentedNot stated on the MCP docs page
Zoho CRMFour pre-built servers rather than one tool countRead and write, including create, update, delete and bulk operationsNone documented; actions are scoped to your Zoho CRM user permissionsNot stated; MCP calls consume the same API credits as normal API calls
CloseNot published as a countRead and write, split across three scopes: mcp.read, mcp.write_safe, mcp.write_destructiveNone documented; the scope you grant is the controlNot stated on the MCP docs page
PipedriveNot published as a countRead and write, including creating and updating records and activitiesNone documented; actions are limited to what your own user may do, and land in the change logNot stated on the MCP knowledge-base page
AffinityNot published as a countRead and write across relationship data, pipeline, meetings, notes and remindersNone documented, though a connection can be restricted to read-onlyScale, Advanced or Enterprise plan
NetHuntNot published as a countRead and write across folders, records and activity timelinesNone documentedLive for all NetHunt CRM users
SalesCrew (our product)140+ (145 registered as of 2026-09-03)Read and write; every tool has an identical effect to its UI counterpartExternal sends default to a review queue; scoped tokens; audit log on every callIncluded on every tier, unmetered

Figures checked on vendor documentation pages, September 2026. Disclosure: SalesCrew is our product, included in this table because it fits the same category.

What to ask a vendor before you count on their MCP server

Ask for the tool list by name, not a total. Ask which actions are read-only and which can write, and whether writing to the pipeline, the inbox or an outreach sequence is on the list at all. A server that only covers contacts and companies will not run a cadence or triage a shared inbox, no matter how well it reads records.

Then ask what stands between an agent deciding to act and the action actually happening. Some servers execute every write immediately once the token has the scope. Others hold anything external, like a send or a stage change, for a person to approve first. That detail decides how comfortable you will be turning an agent loose on a real account, and it does not show up in a tool count.

Disclosure: SalesCrew is our product, and it takes a specific position here — every one of its 140-plus tools mirrors a UI action exactly, external sends are held in one queue by default, and every call is written to an audit log with the actor named. That is the trade-off we made; other vendors on this list may make a different one, and it is worth checking each one's own approach before choosing.

Scope is the control, because nothing else reviews the write

None of the competing servers above document a step that holds a write for a person to approve. Close splits access into read, safe-write and destructive-write scopes, and Affinity lets you restrict a connection to read-only. Grant the narrowest scope the job needs, because once a token can write, the write happens.

Questions

What is an MCP server, in one sentence?
An MCP server is a CRM's list of callable tools published in a standard format, so an AI client like Claude or ChatGPT can discover them and call them directly instead of a developer wiring up each integration by hand.
Does a bigger tool count always mean a better MCP server?
No, and most vendors do not publish a count anyway. A long list that only covers reading records is less useful than a short one that covers the whole workflow: pipeline, inbox, outreach and approvals. Ask what the tools actually do.
Will more CRMs ship MCP servers soon?
Likely, since MCP became a common way for software to expose itself to AI clients during 2025 and 2026. This list will be out of date quickly; check each vendor's own docs before relying on anything here.