Salesforce and Claude Integration: Salesforce in Claude vs. a CRM Built for MCP

This guide covers what getting Salesforce in Claude actually takes as of November 2026, what the connection can and can't do to your data, how the Zoho and Claude integration compares, and a straight answer on when each route is worth it. If you just want the general idea of connecting an assistant to a CRM, start with our pillar guide on how to connect Claude, ChatGPT or Grok to your CRM.

Three ways people get Salesforce in Claude

Search for this and you'll find a mix of official docs, consultant tutorials and vendors selling middleware. They describe three different things, and it helps to know which one you're reading about.

1. Salesforce Hosted MCP Servers (official)

Salesforce runs the MCP servers for you. According to Salesforce's own general availability announcement (April 29, 2026), they're available "for every Enterprise Edition org and above." Nothing to host, no code. This is the route most small and mid-size Salesforce customers should look at first.

2. A connector listed in Claude's directory

Several setup guides published in the last few months report that Claude's connector directory also lists a Salesforce-built connector marked beta. Directory listings change often, so check Claude's Connectors page yourself before planning around it. When it's available to you, the click-to-add flow is simpler on the user side, but your Salesforce admin still controls whether the org allows it.

3. Third-party and self-built connectors

Integration platforms and open-source projects also offer MCP servers that sit between Claude and Salesforce. They can fill gaps, such as reaching editions or objects the hosted servers don't cover, but they add another vendor holding your CRM credentials. For a small business, that's usually one moving part too many.

What the Salesforce and Claude integration setup actually involves

Salesforce says setup "takes less than 30 minutes." That's fair for someone who knows Setup well. Here's the shape of it, based on Salesforce's announcement and its Hosted MCP Servers documentation, as of November 2026:

1. Confirm your edition. Enterprise Edition or above. If you're on a lower tier, the hosted servers aren't an option without upgrading.
2. Turn on the servers you want. In Setup, go to API Catalog → MCP Servers. Setup guides note the servers are off by default, and a client can't connect to a disabled one even with valid credentials.
3. Create an External Client App. This is the OAuth app Claude signs in through. It needs the mcp_api and refresh_token scopes and Claude's callback URL. Get these settings from Salesforce's docs rather than a blog post, because a wrong checkbox here is the most common reason the connection fails.
4. Decide who may use it. OAuth policies on the app control which users can authorize. Narrow it to the people who need it.
5. Each user adds the connector in Claude. Settings → Connectors → Add custom connector, paste the server URL, then sign in with their Salesforce login.
6. Wait, then test. One widely shared setup guide warns that a new app can take up to 30 minutes before it starts working. Don't assume a failure until that window has passed.

None of this is hard for a Salesforce admin. The catch for small teams is the word "admin." If your Salesforce org was set up by a consultant two years ago and nobody has opened Setup since, budget an afternoon and a support ticket, not 30 minutes.

MCP for Salesforce: what Claude can and can't touch

The good news first. Salesforce states that hosted MCP "respects your org's security model: object and field-level security, sharing rules, and profiles all apply." Claude acts as the signed-in user and sees only what that user could see in Salesforce. That's the right design, and it's the first thing to check with any CRM connector.

The part to plan for is write access. Salesforce offers a set of standard servers with fixed tool sets, and setup guides describe both read-only options and broader ones that can create, update and delete records. Which ones you enable is the single most important decision in the whole setup.

• Start read-only. Let the team ask questions for a week or two before anyone gets a server that writes.
• Avoid delete for everyday users. A misread instruction that edits one opportunity is a nuisance. One that removes a batch of contacts is a recovery project.
• Watch API usage. MCP calls go through Salesforce's APIs. If your org already runs close to its API limits because of other integrations, ask your admin before rolling Claude out to everyone.

For a deeper look at what any CRM's MCP server exposes and how a request travels from chat to record, see what an MCP server for a CRM is.

Zoho and Claude integration: same idea, different plumbing

Zoho took a similar path. Its Zoho CRM MCP documentation describes pre-built MCP servers that Zoho hosts, so "you don't need to build, host, or maintain any infrastructure." As of November 2026 there are four:

• Data Insights, which is read-only.
• Data Operations, which can create, read, update and delete, run bulk operations and search with COQL.
• Module Customization, for changing modules and fields.
• Workflow & Process Automation.

Sign-in is OAuth on first use, and actions are scoped to the user's own Zoho CRM permissions. One detail worth knowing: Zoho says MCP calls "consume API credits in the same way as standard API calls," so heavy daily use counts against the same allowance as your other integrations.

The same advice applies as with Salesforce. Give most people Data Insights, and keep Data Operations and Module Customization for whoever owns the CRM. Weighing a move off Zoho for other reasons? Our Zoho CRM alternative guide covers when that makes sense.

Side by side: Salesforce, Zoho and a CRM built for MCP

Here's how the three routes compare for a small team, as of November 2026. Salesforce and Zoho details come from their documentation linked above; check them against your own edition before deciding.

The honest read: Salesforce and Zoho give you more power through MCP, including customization and bulk work that Argento doesn't offer at all. Argento gives you fewer ways to hurt yourself and no setup gate. Which matters more depends on who's in your CRM.

A worked example: one Tuesday morning, two setups

Say you run a five-person IT services company. Two people sell, two handle support and you do a bit of everything. Everyone already pays for Claude. You want each person to open Claude in the morning and ask, "What's waiting on me today?"

On Salesforce Enterprise, you (or your consultant) enable a read-only server, build the External Client App, restrict it to the five of you and wait for it to propagate. Then each person adds the connector. Once it works, the answers are good, because your Salesforce data is rich: opportunities with amounts, forecast categories, years of activity history. If your sales lead wants Claude to update opportunities too, you go back into Setup and enable a write server for her account only.

On Argento, each person opens Settings → MCP Server, copies https://app.argentocrm.com/mcp, adds it in Claude under Settings → Connectors → Add custom connector and signs in with their Argento email and password. The morning question returns their open tickets, tasks due or overdue, active projects and open deals. A support tech can say "Move the Henderson ticket to Waiting on client and add a subtask to chase the survey," and Claude uses the workspace's own status list, so it can't invent a status that doesn't exist. Nobody can delete anything through Claude, and you can scan Recent Claude activity on Friday to see what was done.

What you give up in the second setup is real: Argento deals have no dollar values, win rates or forecasts, and there's no custom object or automation builder for Claude to work with. If your sales lead lives in forecast reviews, that's a dealbreaker. If the team mostly needs "who do I call, what's overdue, log this," it isn't.

When Salesforce in Claude is the right call

• You're already on Enterprise Edition or above, so the hosted servers are already available to your org.
• You have an admin, in-house or on retainer, who's comfortable in Setup and OAuth policies.
• Your team depends on opportunity amounts, forecasts, custom objects or Flows that a smaller CRM doesn't have.
• You've got years of history in Salesforce that would be painful to move.

If most of those are true, don't switch CRMs to get an AI connection. Turn on the hosted servers, start read-only, and expand from there.

When a CRM built for MCP makes more sense

• You're on a Salesforce edition below Enterprise and would need to upgrade just to connect Claude.
• Nobody on the team wants to be the Salesforce admin.
• You're paying per seat for features the team doesn't open, and the AI connection is the main thing you want.
• You'd rather the connector simply not be able to delete, so you never have to audit who has which server.

That's the case for a flat-rate CRM that includes its MCP server. Our Salesforce alternatives guide covers the full feature trade-off and a migration plan, and the same applies whether you start from Salesforce or Zoho.

Connecting Argento CRM to Claude

For comparison with the admin checklist above, this is the entire process. It's also in the Help Center.

1. In Argento, open Settings and expand MCP Server.
2. Select Copy next to the connector URL.
3. In Claude, go to Settings → Connectors → Add custom connector and paste it.
4. Sign in with your Argento email and password and approve.

There's no API key and nothing for an administrator to do first. Claude can then search and list companies, contacts, tickets, tasks, projects, deals and knowledge base articles; summarize a workspace; pull a full company profile; create and update records linked by name; and manage subtasks. ChatGPT, Grok and other MCP-capable assistants connect the same way. For prompts to try in your first week, see our Claude CRM integration guide with 25 prompts.

Plans are flat, with users included: Starter is $25/month for up to 10 users, Growth $50/month for up to 50 and Scale $100/month for up to 100, each with the MCP server. See full pricing.