What you can actually do with a CRM connected to Claude: 10 real examples

When your CRM is connected to Claude through MCP, you can ask it to find, summarise, create and change real records — not just talk about them. Below are ten requests that work, phrased the way you'd actually type them, each one run against my own live Groundbase account while writing this post.

Most explainers stop at what MCP is. Mine does too, which is why this post exists: this is the part where someone uses it.

The ten

1. "How many open deals do I have, and what are they worth?"

You get the count and the total, plus what came in over the last 30 days. This is the request that replaces opening the app to look at the dashboard, and it's the one I use most.

2. "What tags am I using, and how many contacts are on each?"

Comes back as a list with a count beside every tag. Ask this once and you'll find the two tags that mean the same thing, and the three you made for a campaign that ended in June.

3. "How many people tagged real-estate can I text, excluding anyone who's opted out?"

This one matters more than it sounds. It resolves the audience and hands back a count plus a few sample names without sending anything or creating a campaign, so you can check the number before you commit. When I ran it, the opt-out exclusion was correctly applied — people who replied STOP were left out.

4. "What's outstanding, and in which currencies?"

Invoice totals come back per currency rather than merged into one converted figure, because a single blended number doesn't correspond to any money that exists.

5. "What automations do I have, and when did each one last run?"

Every workflow with its trigger, step count, whether it's active, and its last run and status. This is how you find the automation you built in July that has been quietly failing since.

6. "Add Priya Shah, priya@example.com, 555-0123 — she asked about a kitchen, wants to start in November."

One sentence, one record. The name, email, phone, job title and the note all land in the right fields, and you never open a form.

7. "Open a deal for her — kitchen reno, $2,500, in Prospect."

Created against the contact, in the stage you named, in the currency you use. Stage names are yours, so "in Prospect" works because that's what your pipeline calls it.

8. "Remind me to follow up on Friday at 9."

A task with a real due date, linked to the contact, so it shows up on the record and in your task list rather than in a note you have to reread.

9. "Note that she wants to start in November."

Notes land on the contact's timeline next to the texts, calls and emails, so the history is one thread rather than a separate app.

10. "Tag these 40 people sms-batch-06."

Bulk tagging is the one that earns the whole setup. It's tedious by hand, it's not worth building a feature for, and it's a perfectly reasonable thing to ask for in a sentence. Tagging is also how you drive everything else: a workflow that triggers on a tag, or a campaign audience built from one.

And the one I didn't run for this post

Claude can also send — texts, emails, and bulk sends through your own Twilio and your own mailbox. I've used it for exactly that: writing a message template and then sending a bulk SMS with it.

I deliberately didn't run a send while writing this, because my account holds thousands of real people and a blog post is not a reason to text them. That's worth saying out loud, because it's the difference between reading and doing: everything in the list above is reversible, and sending isn't.

What it can't do

Being straight, because a features post that oversells is worse than none:

• It acts as you. Connecting the server gives the assistant your permissions inside your CRM. That's the point, and it's the reason to be deliberate about which tools you connect. Each client gets its own token, and revoking one doesn't sign out the others.
• It isn't a background process. It acts when you ask, in a conversation you're having. Nothing runs overnight on its own — that's what workflows are for.
• It can't read what isn't there. If your notes are in your head, no assistant can summarise them.
• It won't fix a messy CRM. Duplicate contacts and stale tags come back as duplicate contacts and stale tags, just faster.
• Confirm the consequential ones. Anything that sends a message or deletes a record deserves a look the first few times. Ask for the count before the send — example 3 exists for that.

How to connect it

Groundbase is a CRM for one-person businesses that sends email and texts through your own accounts and connects to the AI assistant you already use. The connection is one URL and a sign-in:

1. Copy your connection URL from Settings → AI integrations
2. In Claude, open Settings → Connectors → Add custom connector and paste it
3. Sign in when it asks — your password is typed on a Groundbase page, never into the AI client

It's the same URL for ChatGPT, Cursor and Windsurf. The full walkthrough, including the per-client steps, is in connecting Claude to your CRM via MCP and the AI integrations help article.

If you want to know how Groundbase's server compares to other CRMs' — including where it comes off worse — that's which CRMs actually have MCP servers.

Who this isn't for

If you don't already use an AI assistant daily, none of this is a reason to start. The value here is that the assistant you already pay for can reach your actual work; if there's no assistant, there's nothing to connect.

And if you want an AI that works your CRM for you without being asked, this isn't that either. It answers, it acts, and then it waits for you.

---

Tried something with Claude and your CRM that worked better than expected? I'd like to hear it: blog-claude-crm@groundbasecrm.com — I read every one.