Salesforce connects to Claude through its hosted MCP servers. A Salesforce admin creates an External Client App and turns on the MCP servers the team needs. Then each rep adds Salesforce in Claude as a custom connector and signs in. Salesforce also lists a beta connector in Claude’s directory. Every action runs as the signed-in user, with that user’s Salesforce permissions.
Steps 1 to 3 are a one-time job for a Salesforce admin. Steps 4 and 5 are for each rep. Try it in a sandbox first: sandbox server URLs add /sandbox/ before the server name.
In Setup, search for External Client App Manager and click New External Client App. Turn on OAuth and set the callback URL to https://claude.ai/api/mcp/auth_callback. Salesforce doesn’t support Connected Apps for MCP.
Add the scopes Access MCP servers (mcp_api) and Perform requests at any time (refresh_token). Under Security, select JWT-based access tokens for named users. Create the app and copy its consumer key. It can take up to 30 minutes to start working.
In Setup, search for MCP Servers under API Catalog and toggle on the ones you want. They’re all off by default. SObject Reads (read and query only) is the safe start for reps. SObject All adds create, update, and delete.
In Claude, go to Customize, then Connectors, and add a custom connector. Name it Salesforce and paste the server URL, for example https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads. In the advanced settings, paste the consumer key as the OAuth client ID.
Click Connect. Claude sends you to Salesforce to log in and approve. Back in Claude, click Configure on the connector and set any tool that changes data to Needs approval.
Salesforce’s Headless 360 server (beta, from July 2026) is the one listed in Claude’s directory. It covers records plus admin work such as managing users and permission sets, so most of its early actions are Setup tasks. For reps working deals, the SObject servers are the simpler choice.
From Salesforce’s and Anthropic’s own docs, as of October 20, 2026.
Agentforce is Salesforce’s own agent platform. Your admins build and run it inside Salesforce, on Salesforce data.
Claude connected through MCP works from outside Salesforce, in the same chat where a rep also has email, calendar, and call notes. It reaches into Salesforce as that rep, which suits the quick questions and updates that would otherwise mean building a report or editing a record by hand.
Copy the prompt, swap in your own deal, and run it with Salesforce toggled on. The results are illustrations with a made-up company, Acme.
Ask for exactly the view you need. Claude queries opportunities as you and returns them in a list you can act on.
Using Salesforce, list my open opportunities closing this quarter with stage, amount, and next step. Flag any where the next step is empty or the close date has already passed.
3 opportunities closing this quarter
Give Claude your notes and the changes. With write tools on Needs approval, you confirm each one before it saves.
Log a call on the Acme opportunity in Salesforce with these notes, set the next step to “pricing review with their CFO,” and push the close date out two weeks. Show me each change before you save it.
Changes to save on Acme
Claude pulls the account, its open opportunity, and recent activity, so you walk in knowing what was last promised.
Before my call with Acme, pull the account and its open opportunity from Salesforce: contacts and roles, recent activities, open cases, and what we last promised them.
Acme account brief
Claude inherits your Salesforce permissions. It can’t see or change anything you couldn’t. These are the settings worth checking before a team rolls it out.
Claude can drive one tool when one rep asks. Arrows drives the whole team’s stack on every deal, with no prompt. Arrows reads the context on the opportunity and writes the property changes back, so nobody has to keep two systems in step by hand.
Arrows is its own product, not part of Claude. Your reps can keep using Claude alongside it.
An Agent Architect connects your stack and sets what Arrows can do in each tool. Then Arrows does the follow-through on every deal, and your reps approve what matters.
Book an agent kickoffSalesforceOpportunity updates
HubSpotNot used by this team
GmailFollow-up emails
GongRead call transcripts
GranolaRead meeting notesYes, two routes. Salesforce’s hosted MCP servers connect as a custom connector once an admin sets up an External Client App. Salesforce also lists a beta connector, Headless 360, in Claude’s directory. For reps working deals, the SObject servers are the simpler choice.
Yes. Salesforce hosts standard MCP servers: SObject All, SObject Reads, SObject Mutations, and SObject Deletes for records, plus servers for Data 360, Tableau Next, and Headless 360 (beta). They’re off by default, and an admin turns on the ones the team needs.
An admin creates an External Client App with the callback URL https://claude.ai/api/mcp/auth_callback and the mcp_api and refresh_token scopes, then turns on the MCP servers. Each rep adds a custom connector in Claude with the server URL and the app’s consumer key, then signs in to Salesforce.
Yes, if an admin turns on SObject Mutations or SObject All. Claude can then create and update records as the signed-in user, within that user’s object permissions, field-level security, and sharing rules. Delete is a separate server.
It runs inside Salesforce’s security model: per-user OAuth, the user’s own permissions on every call, and an audit trail. Admins can limit who connects with a permission set, shorten token life, and start reps on the read-only server. In Claude, set write tools to Needs approval.
They do different jobs. Agentforce is Salesforce’s agent platform, built by admins inside Salesforce. Claude works from outside it, next to email and call notes, when a rep asks. Neither works every deal on its own. That’s the part Arrows does.
Cookies at Arrows
We use HubSpot to count site visits in aggregate. With your permission, we also use cookies to recognize visits, measure our marketing, and identify the companies that visit. You can change your mind anytime via “Cookie settings” in the footer. Read our Cookie Policy
We use cookies to understand how people use our site, measure our marketing, and identify the companies and people that visit so our sales team can follow up. Choose “Reject all” to turn this off, or change it anytime via “Cookie settings” in the footer. Read our Cookie Policy
Choose which cookies we can use. Strictly necessary cookies are always on because they make the site work and remember this choice.
Strictly necessary
Required for security, core site functions, and remembering your cookie choices. These are always on.
Analytics
Allow HubSpot and Google Analytics to recognize visits across pages and sessions so we can understand which content is working.
Marketing
Used to measure our campaigns, show you relevant Arrows content on other platforms, and identify the company (and in the US, the person) visiting so our sales team can follow up.
Your browser is sending a Global Privacy Control signal, so Marketing cookies are switched off and cannot be turned on here.
