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

Most of the big CRMs now have an official MCP server, and nearly all of them let your AI assistant read and change your records. Almost none let it send anything. Of the other servers I checked, not one has a tool that sends a text message, and only one, Microsoft's Customer Service server, documents a tool that sends an email to a customer. The rest stop at a draft, or have no email tool at all.

Groundbase's server can send texts and email, book meetings, create and send invoices and quotes, send documents for signature, and run workflows. It's in the one plan, and you use the AI subscription you already pay for.

I build Groundbase, so I have an obvious bias. This is the survey as accurately as I can check it, including where the others are the better choice. Everything was checked on each vendor's own documentation on 10 October 2026. This space moves monthly, so treat the date as part of the answer.

The short answer

Sources: Salesforce's hosted MCP servers announcement; HubSpot's remote MCP server changelog; Microsoft's Dataverse MCP documentation; Zoho's CRM MCP overview and Bigin's Zoho MCP page; Attio's MCP overview and pricing; monday.com's MCP help article; Pipedrive's MCP tools; Close's MCP tools and MCP help page.

Two more. Folk has an official server that creates and updates contacts and notes. Less Annoying CRM has no official server; there's a third-party one.

Records versus actions

Nearly every server above can do the first of these two things. Very few can do the second.

• Records. Read, create and update rows. The assistant can look things up and file them: add a contact, move a deal, write a note.
• Actions. Send the text. Send the email. Send the invoice. Something leaves your CRM and reaches a person.

When a CRM's server touches messaging at all, it usually stops at a draft. Close's draft tool says outright that the email is never sent automatically. HubSpot's server creates, updates and clones email drafts. You open the CRM and press send yourself.

That's a defensible choice, and I want to be fair about why. Sending can't be undone. A bad draft costs you a minute. A bad text to two hundred people is a problem you can't take back. For a vendor with millions of users, keeping a person between the assistant and the send button is the responsible default.

It does mean the useful version of the request doesn't finish. "Text the twelve people who went quiet after a demo" ends with twelve drafts you still have to click through, which is most of the work you were trying to hand over.

What Groundbase's server can do

Nearly everything you can do in the app, by asking. Some of what that looks like, said to Claude or ChatGPT:

• "Text everyone tagged demo-requested who hasn't heard from me this week." The texts go out from your number, through your own Twilio account.
• "Send Maria the intake form to sign, and book her in for Thursday at 2." The form goes from your saved template, and the meeting lands on your calendar.
• "Turn the quote Dan accepted into an invoice and send it." The invoice goes out with a pay link, and card payments land in your own Stripe account.
• "Which deals have been in Proposal for more than a week? Move them back to Discovery and tag them stalled."
• "Run the new-client workflow for Maria."

In full: search and filter contacts, update records, find and merge duplicates, send and schedule texts, send email from your own mailbox, run email and text campaigns, book meetings and manage booking links, create and send invoices and quotes, record payments, send documents for signature and remind signers, run and pause workflows, leave voicemail drops, and track time onto an invoice. All of it is in the $19. There's no AI tier, no credits, and no Groundbase charge for using it; the cost of the AI is whatever your own Claude or ChatGPT subscription already is.

A few things stay in the app on purpose: connecting Twilio, Google, a mailbox or Stripe, your subscription, card refunds, importing a spreadsheet, and making a document template.

Setup is a URL. Copy it from Settings → AI integrations, add it as a connector in your assistant, and sign in with your Groundbase account. Connect Claude to your CRM via MCP walks through it, and what you can do with a CRM connected to Claude shows it day to day.

How it's fenced

An assistant that can send needs limits, so here they are, stated exactly.

• Every tool that sends or deletes is labelled that way and tells the assistant to check with you first. Most assistant apps also ask your permission before they use a tool. Groundbase can't force an assistant to ask, though, so I don't promise it will.
• There's a cap. Through an AI connection, your account can send at most 100 texts and emails an hour and start at most 10 campaigns or bulk sends an hour. One email can go to at most 50 people.
• Deletes can be undone, sends can't. Deleted contacts, companies and deals can be restored from Settings → Recently deleted for 30 days. A sent text or email can't be called back.
• Each assistant gets its own key, which you can revoke from Settings without touching the others.

Why I allowed sending at all comes down to how Groundbase is built. Texts go out on your own Twilio account and email from your own mailbox, at your providers' rates. I'm not reselling messages, so I have no margin to protect by keeping the assistant at the draft stage. The decision, and the bill, sit with you. That's not braver than HubSpot. It's a different architecture.

Which plan each server needs

This is where "nothing gated" matters.

• Salesforce offers its hosted servers to every Enterprise Edition org and above, and an admin has to turn them on.
• Microsoft Dynamics 365 charges tool use in Copilot Credits when an agent outside Copilot Studio uses it, unless you're licensed for it.
• Zoho CRM counts each call against your API credits.
• Pipedrive has the server on every plan, with token limits, and still in beta.
• HubSpot has the server on all accounts, but its quotes tool needs Revenue Hub Professional or Enterprise.
• Attio, monday.com and Zoho Bigin put theirs on every plan, Bigin's free edition included. Credit where it's due.

Groundbase has one plan, so the server, and everything it can reach, is in it.

Where the others are the better choice

• Breadth. Salesforce and HubSpot have a decade of objects behind their servers: tickets, products, line items, custom objects. If your business lives in those, no small CRM's server replaces them.
• Admin control. Salesforce's servers are off until an admin enables them. Close splits its server into permission levels, with updates and deletes at the top. Pipedrive's server can't delete at all. Groundbase has none of that granularity; a connected assistant can reach nearly everything.
• A draft-first default. If you want a person approving every message, the drafting servers give you that by design. In Groundbase it depends on your assistant asking, which most do and none are forced to.
• Flexible data. Attio lets the CRM take your business's shape, and its server can address all of it.
• A whole suite. Zoho's and Microsoft's servers reach across their other apps. If you already live there, that's worth more than a better CRM server.
• Calling by AI. Close's server can schedule a call by its AI voice agent. Groundbase's assistant can leave a voicemail drop, but nothing in Groundbase talks to your customers by voice.
• They have teams. Groundbase is one person. If a protocol change breaks something, I fix it myself, which is fast some days and fragile on others.

What Groundbase doesn't have

• No teams or extra users. One person per account, so no admin roles either.
• No permission levels for an assistant. It's connected or it isn't, within the caps above.
• AI changes aren't marked as AI. Most record changes show in your activity feed like your own, without saying the assistant made them, and emails the assistant sends don't appear there at all.
• No assistant inside the app. You bring your own Claude, ChatGPT, Cursor or other MCP client.
• No iPhone app. Web, Windows desktop, and Android installed from the website.
• Texting needs setup. Your own Twilio account, and for US numbers a carrier registration that takes days. Here's that process.

How to check a server before you commit

1. Read the tool list, not the marketing page. Any MCP client shows you a server's tools once it's connected. The verbs tell you more than any post, this one included.
2. Search for "draft". If the messaging tools all draft, compose or prepare, the assistant can't send. That may be exactly what you want; know it before you build your week on it.
3. Check what it costs to use. Look for credits, API limits or token limits, and the edition it needs.
4. Check how you take access away. A server that can act should make revoking it obvious.

The decision

If you're already on Salesforce, HubSpot, Zoho, Dynamics or Attio, use their server. It covers more of your data than anything I offer, and changing CRM for a better MCP server is a bad trade.

Pick Groundbase if you're one person, your work runs on texts, calls and email, and you want your assistant to finish the job, sending the texts, the invoice and the form to sign, rather than leave drafts for you. All of that is in one plan: $19 a month or $199 a year, with a 14-day trial; a card is taken up front and nothing is charged until day 15. Who Groundbase is and isn't for is the straight version.

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

---

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