Claude CRM: Connect Claude to Your CRM and Keep Control

Claude has no CRM of its own, but it can work inside yours. Through a connector based on the Model Context Protocol (MCP), Claude finds, creates and updates records in the CRM and acts with the permissions of the person who connected it. HubSpot, Pipedrive, Zoho CRM, Capsule and Customermates offer such a connection today; Salesforce is piloting its own Claude plugin. What separates them is the plan you need on each side, whether Claude can delete, and where you decide which actions Claude may take without asking.

Below you will find a vendor table with sources, the setup in Claude and Claude Code, the permission settings that matter and the cost for a small team. Customermates publishes this guide and appears in it as one option, in its own labelled section.

Four things people mean by "Claude CRM"

Most search results for "Claude CRM" are about the first row, so the rest of this guide is about connectors.

What Claude does once it is connected

The tools come from the CRM, not from Claude, so the exact list depends on the vendor. Across the connectors below, the everyday work looks like this:

• Answer questions from live records: "Which deals are in the Proposal stage, and who is the contact on each?"
• Create and link records after a call: a contact, its organization, a deal and a task.
• Change fields and add notes from a transcript or from notes you paste in.
• Where the CRM holds conversations, read a thread and prepare a reply.

Claude picks the tools and the order on its own. That works well for a handful of records per request. For hundreds of rows, vendor limits apply (HubSpot's connector creates or updates 10 records at a time in bulk), and an import is the better tool.

Which CRMs connect to Claude

Checked on 8 October 2026 against each vendor's own page, linked in the first column.

Salesforce also runs hosted MCP servers that are separate from the Claude plugin; the Salesforce MCP guide covers them. HubSpot has a remote MCP server next to its Claude connector, explained in the HubSpot MCP guide.

How to connect Claude to a CRM

The steps are the same for any CRM with a remote MCP server. Where Customermates differs, it says so.

1. Check who can add the connector

   On Free, Pro and Max you add it yourself; Free allows one custom connector. On Team and Enterprise, an Owner adds it under Organization settings › Connectors, and then each member connects individually.

2. Add the server address

   In Claude, open Customize › Connectors, click +, choose Add custom connector and paste the vendor's MCP URL. Pipedrive's is https://mcp.pipedrive.ai/mcp. For Customermates, it is the address you open Customermates at, followed by /api/v1/mcp.

3. Sign in and approve

   The CRM opens a sign-in window. In Customermates, the Authorize access screen names the connecting app and the host it sends access to; click Approve. From then on, Claude acts as you, with your role's permissions.

4. Set tool permissions

   Select the connector under Customize › Connectors to see Tool permissions. Set read tools to Always allow, and leave anything that writes, sends or deletes on Needs approval. On Team and Enterprise, Owners can restrict a connector's actions for the whole organization, and members cannot override that.

5. Prove it with one read and one update

   Ask a read-only question first, such as your open deals in one stage. Then change one field on a test record and add a note. Open the record in the CRM and check that the change is there. In Customermates, the record's History panel lists it, provided your role can read the audit log.

Customermates also has a shortcut: under Settings › API keys, click Add, choose Claude under Quick connections, then Claude account. Add to Claude then opens Claude's dialog with the address filled in (Claude web and Team only). The connector guide has the details and a troubleshooting table.

Claude Code, including Pipedrive

Claude Code adds remote MCP servers from the terminal. For Customermates, create a key under Settings › API keys (Add, then Standard API key; the key is shown once) and run:

claude mcp add --transport http customermates https://<your-customermates-address>/api/v1/mcp \
  --header "x-api-key: YOUR_KEY"

A server that signs in with OAuth instead of a key, such as Pipedrive's, is added without the header. You then complete the sign-in with /mcp inside Claude Code, as Anthropic's Claude Code documentation describes:

claude mcp add --transport http pipedrive https://mcp.pipedrive.ai/mcp

Pipedrive's guide covers the Claude app only, so try a read before you rely on Claude Code with it. The default scope is the current project. --scope user makes a server available in all your projects, and --scope project writes it to a .mcp.json file meant to be shared with your team, so keep API keys out of a file you commit. Codex, Cursor and the Gemini CLI are covered in the CLI guide.

Who controls what Claude writes

This is where setups differ most, and a wrong assumption here costs data.

• The client is usually the gate. The Customermates MCP server tells connected clients to confirm with you before they delete or send, but it does not enforce that: once Claude calls an allowed tool, the action runs. What protects you is Tool permissions in Claude. Capsule describes the same choice: you decide whether Claude checks with you before it makes changes.
• Claude gets your permissions, not fewer. A Customermates connector or API key inherits the permissions of the user behind it; there is no per-key scope. If Claude should do less than you can, connect it as a separate user with a narrower role (which takes a seat), or expose fewer tools with the toolsets parameter in the MCP reference.
• Sending is immediate. If your CRM can send email or chat messages, a send call sends. Ask Claude to save a draft and send it yourself from the inbox.
• Vendor guardrails vary. HubSpot's connector cannot delete and applies conditional property and pipeline stage validation rules, but not association label validations. Capsule lists only create and update actions. Zoho's Data Operations server can delete, also in bulk.
• What Claude reads goes to Anthropic. Tool results become part of the conversation. Anthropic publishes separate consumer and commercial terms; check which ones cover your Claude plan, and whether you need a data processing agreement, before you connect customer data.

What Claude plus a CRM costs

Claude prices from claude.com/pricing, checked on 8 October 2026, in USD with monthly payment: Pro is $20 per month, Team Standard seats are $25 per seat per month, for teams of two or more, and Team Premium seats are $125. On a yearly subscription, Anthropic charges $17 for Pro and $20 per Standard seat. Pro includes Claude Code.

Customermates bills monthly per user, with no yearly contract. When Claude works through MCP, the model runs on your Claude plan, so it uses no Customermates hosted AI credits. The self-hosted open-source core includes the MCP endpoint without licence fees, but not the inbox. With another vendor, add its seat price instead; HubSpot and Pipedrive list their connectors for all plans, and Pipedrive applies usage token limits per plan. Plan details are on the pricing page.

Where Customermates fits

Disclosure: Customermates publishes this guide. Customermates is an open-source, AI-native CRM built in Germany for small client-facing teams: consultants, agencies, other service businesses and founders. Its MCP endpoint is part of the AGPL core, so it works on every cloud plan and on self-hosted installations, with 53 tools. Through it, Claude works with contacts, organizations, deals, services, tasks and any lists you add, their notes and fields, and the workspace Knowledge Base. On Pro and higher in Customermates Cloud, the same connection reaches the unified inbox with email, LinkedIn, WhatsApp, Instagram and Telegram conversations.

Four prompts that test the setup on a workspace with the default deal stages:

1. "Show my open deals in the Proposal stage with their organization and weighted value." (read)
2. "On the Northwind deal, set Stage to Negotiation and add to its notes: budget approved on today's call, contract draft next." (update)
3. "Create a contact for Sarah Lee, link her to the Northwind organization and the Northwind deal, and create a task assigned to me to send the contract draft." (create and link)
4. "Find my latest email thread with Sarah Lee, summarize it in two lines and save a reply as a draft. Do not send it." (Pro, inbox)

If you would rather not run your own AI client, Mate is the assistant inside Customermates Cloud. It uses the monthly hosted AI credits per active user that come with the plan, prepares summaries and reply drafts, and runs Routines: saved instructions on a schedule or on record events. In Customermates Cloud, the primary production database is configured in the AWS Frankfurt region. That is a selected setting rather than a residency guarantee, and the subprocessors are listed publicly.

Customermates is not the right pick if you need a phone dialer, email sequences or a native mobile app, or if your team runs HubSpot or Salesforce and is happy with it. In that case, use the vendor's own connector from the table above.

Frequently asked questions

Vendor details checked on 8 October 2026 against Anthropic's custom connector guide, Anthropic's connector permissions guide, Claude pricing, HubSpot, Pipedrive, Zoho CRM, Capsule and Salesforce.