How to Integrate Claude Code with Salesforce MCP: A Complete Guide

Developers want Claude Code to understand their Salesforce org instead of guessing at it. A well-planned Claudeforce MCP integration gives the assistant real context: metadata, records, and tools it can call under controlled access. Model Context Protocol (MCP) is the open standard that makes this connection possible.

This guide covers the two supported paths, what each one needs, and how to configure, test, and secure them. It also walks through a development example. Plan for time on authentication, permissions, and sandbox testing, because those steps decide whether the setup is safe to use.

 

How Claude Code, MCP, and Salesforce Fit Together

• Claude Code: Anthropic’s programming application that runs in your terminal.
• MCP: It is an abbreviation that stands for the protocol that allows AI to use any other external tools and datasets. It describes the connection and does not grant you any new permissions.
• Salesforce Hosted MCP Servers: It is the servers that Salesforce uses in their work, like records queries and updates.
• Salesforce Development plugin: a Claude Code plugin with skills, MCP servers, and commands for development on the platform.

Use the plugin when the job is building, testing, or deploying. Use hosted servers when Claude Code needs live org data or business logic. Many teams need both, but the setup differs. Teams weighing wider scoping for a Claudeforce implementation should treat these as separate workstreams.

 

What You Need Before Starting a Claudeforce MCP Integration

For the Salesforce Development plugin

• Claude Code 2.1.222 or later
• A Node.js long-term support release
• Salesforce CLI
• Python 3.8 or later
• A Salesforce DX project and a development org

Salesforce states that direct plugin access requires Salesforce Foundations or an Agentforce license. Some guided workflows need extra licenses or org configuration. Review Salesforce’s plugin installation guide and its telemetry notes first.

For Hosted MCP Servers

• Availability of Setup in order to configure servers and develop an external client application
• An org of production type, sandbox, or scratch org (server URLs are different for each)
• Installation of Claude Code
• Users possessing the necessary Salesforce permissions

Standard servers are inactive by default. The Headless 360 MCP Server is in beta, so check its documentation before relying on it. The Hosted MCP Servers overview lists current capabilities.

 

Connecting Claude Code to a Hosted Server

Salesforce describes a three-step process: turn on the server, create an external application, and link to Claude. Try these out in a sandbox environment, to begin your Claudeforce MCP integration with minimal risk.

1. In Setup, search for MCP Servers, open the Salesforce Servers tab, select a server, and click Activate.
2. Copy the server’s API Name (without the platform. prefix) and its Server URL.
3. In External Client App Manager, create a new app and enable OAuth.
4. Set the callback URL to http://localhost:38000/callback for Claude Code. Select the refresh_token, offline_access and mcp_api scopes.
5. Under Security, require PKCE and issue JWT-based access tokens for named users. Uncheck the secret requirements for the web server and refresh token flows.
6. Save the app, then copy the Consumer Key and Consumer Secret from its settings.
7. Run the command below and paste the secret when prompted.

claude mcp add –transport http MY_MCP_SERVER_NAME MY_MCP_SERVER_URL –callback-port 38000 –client-id “MY_ECA_CONSUMER_KEY” –client-secret

Replace MY_MCP_SERVER_NAME with a label such as salesforce-sobject-all, MY_MCP_SERVER_URL with the URL you copied, and MY_ECA_CONSUMER_KEY with your consumer key.

Next, start claude, run /mcp, select the new server, and choose Authenticate. The status should change to connected.

There are two caveats here. First, the localhost callback is appropriate for the team that has an enterprise API key only. Secondly, Salesforce advises creating connectors within a Claude.ai account and using them in Claude Code. Another thing is that Claude Desktop uses another callback URL, therefore do not transfer the configuration across clients.

Run a Low-Risk Test

Start with a read-only request. Salesforce suggests this prompt for the SObject servers: “tell me some basic information about the {ACCOUNT NAME HERE} account.” Replace the placeholder with a real account and compare the answer with the record in Salesforce.

 

Installing the Salesforce Development Plugin

The plugin path is shorter. Run claude plugin install salesforce-development@claude-plugins-official, start Claude Code, and run /plugin to confirm the installation. Installing it configures the salesforce-api-context, salesforce-metadata-experts, and salesforce-lsp MCP servers automatically.

Then open Claude Code from your project directory and run /salesforce-development:welcome. Ask “Am I ready for development?” and “Validate that I can deploy to this org.” These checks confirm the project and org before any real work begins.

 

A Practical Development Example

This scenario is illustrative, not a recorded test. A developer inherits an Apex class named AccountTerritoryService with no test coverage.

• Requirement: Make Claude Code explain how the class works and what objects are used by the class. Make it write a test for the class and run the test; Salesforce recommends that you use a prompt like this.
• Process: Claude Code reviews your code base and your organization, writes a test, and makes suggestions.
• Review: You need to review all the lines generated by Claude Code. Be sure to review assertions, bulkification, and hardcoded values. Do not accept coverage tests.
• Deploy: Deploy the code to the sandbox first and then approve the deployment.

Salesforce states that you should review all the projects, organizations, and deployment actions suggested by Claude Code.

 

Security Checks for Your Claudeforce MCP Integration

The connection inherits Salesforce’s access model. It does not bypass it. Hosted servers use per-user OAuth 2.0 with PKCE, and SObject tools respect field-level security and sharing rules.

• Least Privilege: Grant permissions only as necessary to perform the action and use only the servers necessary.
• Separation of Duties: Separation between the tooling used to modify code/metadata and the servers reading/writing live data.
• Credentials: Ensure consumer secrets are not stored in your repositories/scripts.
• Test first: Test all new servers and prompts outside production.
• Human Approval: You personally approve writes, deployments, and changes to flows/Apex.

Custom tools need extra care. Salesforce lets teams expose Apex invocable actions, Flows, and other logic as MCP tools, and weak design there creates risk. Standard servers often suffice, but custom logic, complex metadata, or regulated data usually calls for experienced Salesforce implementation planning.

 

Troubleshooting Common Connection Issues

Hosted server issues by Salesforce include connection, authentication, and prompt execution issues. The above table uses these categories along with some common checks.

Symptom	Likely cause	What to check
Server will not connect	Server inactive or wrong URL	Confirm activation in Setup and the sandbox or production URL
Authentication fails	External client app or callback mismatch	Verify the callback URL, scopes, and PKCE settings
Server shows “needs authentication”	Authorization not completed	Run /mcp and choose Authenticate
Prompt returns no data	Missing user permissions	Test the same query in Salesforce as that user
Plugin workflow stalls	Missing tool, license, or plugin	Rerun the readiness check and read the plugin troubleshooting page

Conclusion

For a Claudeforce MCP integration, success lies in the thoughtfulness of each step – the right route, proper OAuth setup, limited privileges, sandbox tests, and review of each change by people. Begin with one low-risk process, then expand it only when it starts working the way it should.

Should you require assistance in your Claudeforce MCP integration process, check out Salesforce integration services.

 

FAQs

Is it possible to connect Claude Code to Salesforce using MCP?

Yes. Salesforce provides the means to connect Claude Code to Hosted MCP Servers via an external client application and OAuth. Also, its Salesforce Development plugin includes MCP servers for developing in Salesforce DX projects.

What permissions are necessary for configuring the connection?

Access to Setup is necessary to activate servers and create the external client application. Then each user connects separately. Existing permissions in Salesforce, including field-level security and sharing settings, control access to data for Claude Code.

Is it always necessary to develop something custom?

No. Regular hosted servers support records operations without any additional connector code. Custom development comes into play in case some specific functionality such as Apex actions, Flows, or other business logic needs to be exposed as tools.

How can I test the connection?

It is possible to use a sandbox environment, limited user permissions, and a read-only request for data of the known account. Compare the result with the Salesforce record. Only then try to do any writes or deployments.

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