How to Integrate Claude with Salesforce via Hosted MCP Servers

Sales reps lose hours moving between records, notes, and emails before a single customer call. Connecting Claude to your CRM puts account context, opportunity history, and case details into one conversation. This Claude Salesforce Integration Guide shows how to do it through hosted MCP servers, which give Claude access to approved CRM data and actions without a custom-built connector.

It is a practical walkthrough, not an AI overview. You will see how setup, authentication, and permissions fit together, which use cases suit a first rollout, and where scope decisions matter most. We also clarify how the Claudeforce vs Agentforce question shapes your plan.

How Claude, MCP, and Salesforce Fit Together

Claude: Anthropic’s AI assistant, acting here as the client your team chats with.
Model Context Protocol (MCP): An open standard that lets AI clients use external tools and data in a consistent way.
Hosted MCP servers: Endpoints that Salesforce runs for you. An admin switches on a server, and a compatible client connects using OAuth, the standard sign-in and consent flow.

The Hosting configuration will remove the middleware. You set up access in Setup without writing and patching your integration server. According to Salesforce, all the calls to standard Salesforce servers from the tools take into account the object permissions, field level security, and sharing rules for the currently signed-in user.

Hosted servers have been generally available since April 2026 and are used in Enterprise, Performance, Unlimited, and Developer editions. Some of the product specific hosted servers, like Headless 360, are still in beta. You can also get charged using Flex Credits.

Claudeforce vs Agentforce: Where Each One Fits

Claudeforce is the name for the expanded Salesforce and Anthropic partnership announced in August 2026. It is not one product. It spans three areas:

Salesforce in Claude: A plugin with 37 prebuilt sales skills, announced for pilot customers first, with open beta expected in September 2026. Confirm current availability for your org.
Claude in Agentforce: Claude serves as a reasoning model in Agentforce and appears in Agent Builder.
Claude in Slack: Claude powers Slackbot for Salesforce customers.

Agentforce is the platform provided by Salesforce that enables developers to build and deploy agents within the Salesforce environment. In the case of hosted MCP servers, things are quite different as they enable Claude, operating independently in an application, to access the CRM from the outside world. The two approaches cannot be interchanged.

A lot of businesses will leverage both platforms. Agentforce can help with the automation of activities facing customers, while Claude on the MCP servers can assist sales and analysis professionals. The latter solution is often referred to as Claudeforce MCP Integration.

Salesforce Claude Integration: How It Works Step by Step

This Claude Salesforce Integration Guide sequence works best in a sandbox first.

Choose any business process: Narrow down the choice; for example, take Pre-Call Account Briefing.
Check requirements: You will need a licensed version, administrator that can create External Client Apps, and a sandbox.
Activate the server: Go to Setup -> MCP Servers (API Catalog) and activate it. Choose sobject-reads first since it involves querying/searching of the data without modification.
Develop External Client App: For MCP, Salesforce requires an External Client App but not Connected App. Configure OAuth, add scopes: mcp_api, refresh_token, choose access token based on JWT for named user. Time to activate can be 30 mins.
Configuring the Callback URL: In case of Claude, https://claude.ai/api/mcp/auth_callback. This is unique for each client.
Configurations for security: Set permission set, limit IP range, refresh token lifetime should not exceed 30 days and enable single logout.
Integration with Claude: Guide for configuration of Claude includes customize, connectors and then add custom connector. Put the server URL and paste consumer key in OAuth Client ID.
Authentication: Tap on Connect, log in to Salesforce, and authorize.
Validation: Execute read prompts in the sandbox environment and compare outcomes with the records, permissions, and logs.

What Changes by Client and Org

Environment	Server URL pattern
Production	https://api.salesforce.com/platform/mcp/v1/<SERVER-NAME>
Sandbox or scratch org	https://api.salesforce.com/platform/mcp/v1/sandbox/<SERVER-NAME>

Salesforce’s published guides cover the Claude connector, ChatGPT, Cursor, Postman, and Agentforce Vibes. Claude Code registers remote servers through its own command line setup, so follow Anthropic’s MCP documentation there and reuse the same server URL and consumer key.

What a Salesforce MCP Server Can Do

The capabilities are determined by which server you choose to enable. Standard servers have limited tools that cannot be changed while custom servers allow for Flows and Apex actions. Every effective Claude Salesforce Integration Guide must begin with these examples.

Account briefings: The rep requests opportunities, activity, and key contacts prior to the call.
Opportunity briefs: Claude writes a note about the history of an opportunity.
Case assistance: The agent requests a case briefing along with an initial response which is edited later.
Reporting queries: The analyst retrieves relevant information from records without creating a report.
Approved actions: With a mutation-capable server, Claude can create or update records when permissions allow.

Keep reading information, preparing a recommendation, and executing an action separate. Each carries different risk, and not every server supports all three.

Pre-and-post: There used to be an agent who would log into the account, review the activity history, view open cases, and take notes by hand. Now there is only one question asked, followed by confirmation using Claude’s summary and the records.

Why Salesforce Permissions Matter

This integration is not unlimited CRM access. What Claude can do depends on the enabled server, its tools, and the signed-in user’s permissions.

OAuth and named users: Individual user authentication means that all actions can be traced back to an actual user.
Object and field permissions: If a user can’t see a particular field, then Claude can’t see it either.
Sharing rules: Adheres to existing access rights.
Least privilege: Read until workflow needs writing.
Separation between read/write test: Needs to be validated on sandboxes.
Manual approval process: Needed for changes that are sensitive or face customers.
Any data issues: Look into vendor agreements/data policies.

These measures reduce risk but do not eliminate it.

Basic Hosted Connection or Custom Build?

Requirement	Hosted MCP approach	Customization to consider
Setup	Admin enables a standard server and an External Client App	Custom servers from Flows, Apex, or API Catalog endpoints
Supported operations	Fixed tool sets	Tools tailored to one process
Business logic	Standard record operations	Approval and validation rules in Flow or Apex
Maintenance	Salesforce manages hosting	Upkeep of custom assets
Access control	User permissions apply	Narrower permission sets
Testing	Sandbox prompt checks	Scripted regression tests

Planning the Rollout

Settle these questions first:

Which single workflow goes first?
Which objects and fields does it need?
Is read-only access enough?
How will you measure success, such as time saved per briefing?
Who is the small group that will trial the approach?
When does the standard set of tools become inadequate?
What place in your strategy would Claudeforce vs Agentforce have?

An experienced provider of Claudeforce implementation services will help you with the mapping of workflows, permission checks, configuration, testing, and tuning. For more information, please visit Claudeforce Implementation Overview, MCP Integration for Claude and Salesforce, and Salesforce Integration Services.

Conclusion

Hosted MCP servers give Claude a governed route into your CRM. This Claude Salesforce Integration Guide comes down to three habits: define one use case, grant the narrowest access that works, and test before widening scope. Salesforce and Claude AI integration pays off when permissions come first. Settling Claudeforce vs Agentforce early also keeps scope clear.

Map your first workflow, list its objects, and decide on read or write access. Then assess your requirements, and bring in an implementation specialist if you want a second opinion.

FAQs

What Is a Salesforce Hosted MCP Server for Claude?

A Salesforce-managed endpoint that presents CRM data and operations available to Claude using the Model Context Protocol. An administrator sets up a server, and Claude acts as an authorized client.

How does Claude authenticate into Salesforce?

Via OAuth and an External Client Application. Each individual logs in and consents, meaning the connection will operate under the identity of that particular person.

Can Claude modify Salesforce records?

Yes, but only if the organization makes available a writable server, like sobject-mutations, and has the necessary privileges to make changes. Read-only servers don’t allow modifications of records. This is why permission check-ups must be part of each Salesforce Integration Guide for Claude.

Is Claudeforce vs Agentforce a matter of either or?

No. The Agentforce operates agents on Salesforce, whereas Claude with hosted MCP does not. Many companies utilize both solutions for various workflows.

For more insights, updates, and expert tips, follow us on LinkedIn.