Connect Salesforce to Claude Code

Make Claude log activities and move deals in Salesforce. From the terminal, inside the sessions where you already work.

How do you connect Salesforce to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Salesforce, you add a Salesforce MCP server: a small hosted service that exposes Salesforce's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Salesforce account. No API keys pasted into config files.

claude mcp add --transport http salesforce https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Salesforce once connected?

Full read-write Salesforce access lets Claude update opportunity stages and amounts, log calls and emails as activities, create leads and contacts, and keep records current as work happens. The CRM hygiene and pipeline updates that used to mean manual data entry happen where the record already lives.

Update an opportunity's stage, amount, or close date as a deal progresses
Log a call, email, or meeting as an activity on the right account or contact
Create a new lead or contact and link it to the right account
Update fields on accounts and contacts to keep records current
Create or update a case and route it to the right queue
Find records matching a query and propose batched field updates

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Salesforce access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Salesforce API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Salesforce changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Salesforce connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Salesforce connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Salesforce account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Salesforce's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Salesforce?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Salesforce account it signs in with. Revoking access is one click in Salesforce.

More on the Salesforce connector

Salesforce connector for claude.ai HubSpot + Claude Code Pipedrive + Claude Code Zoho CRM + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us