Which CRMs actually have MCP servers (and what they can really do)

If you've asked your AI assistant to "look at my CRM" recently, you've probably discovered that the answer depends entirely on whether your CRM speaks Model Context Protocol — and if it does, on what its server is actually allowed to do.

That second part gets skipped in most write-ups. The usual article is a list of CRMs with a checkmark next to each one. The checkmark hides the thing you care about, which is whether the AI can only look at your data or can also do something with it.

I maintain a CRM with an MCP server, so I have an obvious bias here. I'm going to try to be useful anyway: the survey below is accurate as far as I can verify it, includes the places where Groundbase is the weaker option, and names the one axis where I think it genuinely wins.

The state of play

As of writing, the major CRMs with official (vendor-maintained) MCP servers:

Two things jump out of that table.

The SMS column is unanimous. Every CRM MCP server I checked — including the ones from companies with thousands of engineers — reads and writes your records, and not one of them can send a text message.

The email column is nearly unanimous too. Most can compose a draft and stop there. Zoho Bigin is the only one besides Groundbase that actually sends — and Zoho CRM, same vendor, only drafts. Worth knowing which of the two you're actually on before you assume.

Two caveats before you use this table for anything. First, this space moves monthly — a vendor that shipped read-only six months ago may have write access now, and anything I write here has a shelf life. Second, "official server" and "useful server" are different claims. Check the vendor's own docs before you make a decision on it.

The distinction that actually matters

Almost every server above can read your CRM. Most can now write to it too — create a contact, update a deal, add a note, log that a call happened. HubSpot's, for instance, covers contacts, companies, deals, tickets, and activities, and it can create and update email drafts.

Read that last part again, because it's the whole point of this post.

There's a category difference between two things an AI can do with your CRM:

• Records — read, create, and update rows. The AI can look and file.
• Actions — send the text message. Send the email. Enroll someone in a sequence. Fire the automation.

Nearly all the coverage is in the first category. When a CRM's MCP server touches messaging at all, it usually stops at a draft — something that appears in your outbox for you to review and send yourself.

Zoho Bigin is the one exception I found on email, and even it stops at SMS. If you know of another CRM whose own server sends a text message directly, I'd like to hear about it — the email address at the bottom of this post goes to me.

That's a defensible product decision, and I want to be fair about why: sending is irreversible. A hallucinated draft is a wasted minute. A hallucinated SMS to 200 people is a problem you cannot take back. If you're HubSpot, with a huge install base and a brand to protect, gating that behind human review is the responsible call.

But it means the useful version of the request doesn't complete. "Text the twelve people who went quiet after a demo" ends with twelve drafts you now have to click through, which is most of the work you were trying to avoid.

Where Groundbase sits

Groundbase's server exposes 86 tools, and the difference is that some of them are actions:

• sms_send_now and sms_send_scheduled dispatch real text messages
• email_send sends — not drafts
• cadences_enroll puts a contact into a multi-step sequence
• workflows_run_now fires an automation
• voicemail_drops_drop leaves a voicemail
• campaigns_manage runs email and SMS campaigns

So the same request ends with twelve messages sent.

The reason this is possible isn't clever engineering — it's the billing model. Groundbase is BYO Twilio and BYO Resend: you connect your own accounts, and messages go out under your credentials at the rates your provider charges you. I'm not standing between you and the carrier, which means I'm not the one absorbing the risk of a bad send, and I don't need to gate it to protect a margin I'm not taking.

That's the honest version. It's not that I'm braver than HubSpot. It's that the architecture puts the decision — and the bill — with you.

It's also worth saying plainly that you can get most of the way there without changing CRM. Run a second MCP server for Twilio alongside whichever CRM server you already use, and let the model read a phone number out of one and send the message from the other. That genuinely works. It's two servers, two sets of credentials, and a model stitching them together across a seam where things quietly break — but it works, and if you're happy with your current CRM it's a far smaller change than switching.

What Groundbase does is collapse that into one place: the thing holding the contact is the thing sending the message, under one key, with the send logged back against the contact automatically.

(The longer piece on how the integration works day to day — setup, auth, what to ask it first — is Connect Claude to your CRM via MCP.)

Where the others are genuinely better

I'd rather name these than have you discover them after switching.

Salesforce and HubSpot cover vastly more surface area. 60+ tools against a data model with a decade of objects in it, plus tickets, products, line items, quotes. If your business lives in those objects, no small CRM's MCP server is going to replace that.

Attio's data model is more flexible. If you want your CRM's shape to match your business rather than the other way round, that's a real advantage, and it carries through to what the MCP server can address.

Zoho spans the whole suite. If you're already in Zoho's world, an MCP server that reaches across their apps is worth more than a better server that only sees one.

They're all better resourced than I am. These are teams. Groundbase is one person. If a protocol change breaks something, Salesforce will have it patched by a team; I'll have it patched by me, which is faster in some ways and much more fragile in others.

If you need CRM breadth, pick on breadth. This post isn't an argument that 86 tools beats 60 — it's an argument that the tools do different kinds of work.

How to actually check a server before you commit

The listicles won't tell you this, so:

1. Read the tool list, not the marketing page. Any MCP server can be asked for tools/list. The tool names tell you more than any blog post — including this one. Look for verbs.
2. Search for "draft". If the messaging tools all say draft, compose, or prepare, the AI cannot send. That may be exactly what you want; just know it before you build a workflow on it.
3. Check what auth it uses. OAuth means you can revoke access without rotating a key you've pasted into four clients.
4. Check whether the actions are scoped to you. A server that can act should also make it obvious how to take that ability away.

So which should you pick

If your CRM is already Salesforce, HubSpot, Zoho, or Attio, use their server. It'll cover more of your data than anything I could offer, and switching CRMs to get a better MCP server is a bad trade.

Groundbase is worth a look if you're a solo operator whose outreach is phone and email, you want your AI to complete the whole task rather than stage it for you, and you'd rather pay Twilio and Resend directly than pay a platform to sit in between. That's a narrow shape, deliberately — here's who it's for and who it isn't.

For the head-to-head versions: HubSpot, Close, Pipedrive, Zoho Bigin.

Try it

Groundbase is $9/month flat with a 14-day trial. The MCP endpoint is https://mcp.groundbasecrm.com/mcp — point Claude Desktop, Cursor, or any MCP client at it and authenticate with OAuth. You can call tools/list against it before you sign up for anything, which is what I'd suggest doing to every server in the table above.

---

Questions about this one? Email me directly: blog-crm-mcp@groundbasecrm.com — I read every one.