How to connect Claude to your CRM

What is a CRM MCP server?

A CRM MCP server is a connection that lets an AI app like Claude read and change records in your CRM, within the permissions you set. MCP stands for Model Context Protocol, an open standard for connecting AI apps to tools and data.

A CRM MCP server usually offers two kinds of tools:

• Read tools: search contacts, list deals, read notes and activity.
• Write tools: create a contact, update a deal stage, add a note or a task.

The difference matters. Reading is safe to allow broadly. Writing changes your records, so it deserves rules.

How MCP differs from a normal integration

A normal integration moves data on a fixed schedule: every new form becomes a contact, every won deal sends a message. It does the same thing every time. An MCP connection is different. The AI decides which tool to call based on your question. But that flexibility is exactly why the permissions matter. So treat an MCP connection like giving a new assistant a login: useful from day one, trusted step by step.

Which CRMs have an MCP server?

Support is changing fast. Check each vendor’s documentation before you decide.

If your CRM has no MCP server but has an API, a small adapter can expose the tools you need. That is how most self-hosted setups work.

How to connect Claude, step by step

There are two common ways, depending on where you work.

In Claude (web or desktop)

1. Open Settings → Connectors.
2. If your CRM is listed, connect it and sign in. If not, choose Add custom connector and paste the MCP server URL from your CRM’s docs.
3. Sign in with OAuth when asked.
4. Start a new chat and ask: “List my open deals with no activity in the last 7 days.”

In Claude Code

1. Add the server with the claude mcp add command and the URL or local command from the vendor’s docs.
2. Sign in if the server uses OAuth.
3. In a session, ask Claude Code to list its available tools, then run a read-only question first.

Always start read-only. Confirm the answers match what you see in the CRM before you allow any writes.

If the connection doesn’t work

• Sign-in loops or fails. Disconnect and reconnect. Check that your CRM user has permission to use the API.
• The agent says it has no tools. Start a new conversation or session after connecting; tools load at the start.
• Answers look incomplete. The server may return only the first page of results. Ask the agent how many records it read.
• “Unauthorized” errors. An API key may have expired, or the account may lack API access on its current plan. Check your vendor’s plan details.
• Slow answers. Narrow the question: one pipeline, one date range, one owner.

Ten questions worth asking your CRM

Founders get the most value from questions they would never take the time to answer by hand:

1. Who sent an inquiry in the last 48 hours and has not heard back?
2. Which quotes are older than three days with no reply?
3. Summarize everything we know about this company before my call.
4. Which lead sources produced deals we actually won?
5. What objections came up most in lost deals this quarter?
6. Draft a follow-up for each stalled deal, with a new angle.
7. Which customers have not been contacted in 90 days?
8. Create a task for every deal stuck in one stage for more than a week.
9. Which industries close fastest?
10. What did we promise this customer, and is it done?

Three routines worth running every week

Questions are useful. Routines are what change your results.

The pre-call brief (before every call)

“I have a call with [company] in 15 minutes. Summarize every note, email and deal for them. List what we promised, what they asked, and one question I should ask.”

Two minutes of reading replaces ten minutes of searching. You walk in knowing the history.

The Monday pipeline sweep

“List every open deal with no activity in 7 days. For each, say the stage, the last contact and the next step I set. Draft a short follow-up for the three most valuable.”

This catches the deals that slip quietly. Most founders find at least one deal they had forgotten.

The Friday lost-deal review

“Read every deal marked lost this week. Group the reasons. Quote the customer’s own words where notes have them.”

Over a month, this shows whether you lose on price, timing, fit or silence. Each answer points to a different fix.

What to let the agent change

Give the agent the smallest power that does the job, then widen it as you build trust.

Rolling out write access safely

1. Week 1: read only. Use the routines above. Check answers against the CRM.
2. Week 2: drafts. Let the agent draft notes, tasks and follow-ups. You paste or approve them.
3. Week 3: routine writes. Allow notes and tasks directly. Review a sample each day.
4. Later: stage changes. Only with clear rules, like “move to Meeting when a booking is confirmed.”
5. Never by default: sending, pricing, deleting.

If something goes wrong at any step, go back one step. That is the whole point of rolling out in stages.

When one CRM connection is not enough

A CRM connection answers CRM questions. But the questions founders care most about cross tools: which ad brought the customer who paid? needs ads, CRM and payments together. So once the CRM connection works, the next step is one business context that joins them.

That is what Growth Control does: it connects ads, CRM, calls, email and payments, and gives Claude or Codex access through MCP, with approval rules for every action that matters.

Common mistakes

• Messy data in, confident answers out. If your CRM has duplicates and empty fields, the agent will summarize the mess with confidence. Clean the active pipeline first.
• One shared admin login. Connect with a user whose permissions match what the agent should do, not an admin account.
• No log. If the agent can write, you need a record of what it changed and why.
• Asking vague questions. “How are sales?” gets a vague answer. “Which quotes over $1,000 are waiting more than three days?” gets a list you can act on.

A short security checklist

• The connected user has the smallest permissions that do the job.
• OAuth or keys are stored by the client, not pasted into chats or files.
• Write tools are off until you have tested reads.
• Sending, pricing and deleting require your approval.
• You know how to disconnect the server in one step.
• You have checked your AI provider’s data terms for your plan.

Walkthrough: a pre-call brief, start to finish

This example is illustrative. It shows what one connected question looks like in practice.

A founder has a call in ten minutes with a lead from last week. Before CRM access, she would open the CRM, search the inbox, scroll through notes and still miss something.

With Claude connected to the CRM, she asks: “Brief me on Jordan at Northline before my 2 pm call.”

The agent searches contacts, finds the company record and reads the deal, the notes and the last three emails. It answers in five lines:

• Who: Jordan, operations lead, came in through the website form two weeks ago.
• What they want: a setup for 60 people in March; asked about weather options.
• Where it stands: quote sent eight days ago; no reply since.
• Open question: they asked about payment terms; nobody answered.
• Suggested next step: answer the payment question and confirm the date on the call.

The founder walks into the call knowing the one thing that was blocking the deal. But the agent changed nothing in the CRM. So the risk was zero, and the value showed up in the first week.

After the call, she gives one instruction: “Add a note with today’s decisions and set a follow-up for Thursday.” That is a routine write, allowed by her rules.

Glossary: words you will see during setup

What to do this week

1. Check whether your CRM has an official MCP server or connector.
2. Connect it read-only in Claude or Claude Code.
3. Ask three questions you can verify by hand, and compare the answers.
4. Use the pre-call brief before every sales call for five days.
5. Write down which write actions you would trust, and allow only notes and tasks first.
6. Note which questions the CRM alone cannot answer. That list tells you what to connect next.

Questions and answers