Skip to main content
The Salesforce plugin and Salesforce’s hosted MCP server let Claude work with your organization’s Salesforce records. The plugin’s marketplace is one of the preconfigured plugin marketplaces Claude Desktop offers.

Set up Salesforce

1

Prepare your Salesforce org

In Salesforce Setup, turn on Enable MCP Service, then create an External Client App for Claude Desktop with these OAuth settings:
  • The callback URL http://127.0.0.1:53280/callback
  • The OAuth scopes mcp_api and refresh_token
  • Proof Key for Code Exchange (PKCE) required
  • Access tokens issued as JSON Web Tokens (JWTs)
  • An OAuth policy that lets users self-authorize
Copy the app’s Consumer Key, which is its client ID. With PKCE, Claude Desktop needs no client secret.
2

Add the Salesforce marketplace

In the Enterprise Admin Console. Go to claude.aiOrganization settings and open the Plugins page under Desktop 3P. Under Plugin marketplaces, click Add and choose Salesforce under From partners. The new entry has Source set to GitHub, Repository set to salesforce/salesforce-skills, and Ref set to claude-prod, the branch Salesforce publishes its releases to. Leave Installation empty and click Save changes.With MDM or a bootstrap server. Add this entry to the allowedPluginMarketplaces key of your managed configuration or bootstrap response:
Either way the marketplace stays available, and each user installs the plugin once, as described in step 4. To install the plugin on every device without user action instead, set the ref to a full 40-character commit SHA and the installation preference to auto_install. Marketplace installation preferences explains why the SHA is required, and Roll out marketplace updates explains how to move to a newer release.
3

Add the Salesforce MCP server

In the Enterprise Admin Console. Go to claude.aiOrganization settings and open the Connectors page under Desktop 3P. Under Managed MCP servers, click Add → Blank, fill in the entry as below, and click Save changes. Set up sign-in for managed MCP servers explains each OAuth field, and users’ apps pick up console changes as described under Configuration updates.With MDM or a bootstrap server. Add this entry to the managedMcpServers key of your managed configuration or bootstrap response:
Keep the name exactly as shown. The Salesforce plugin defines an MCP server with this name, and Claude Desktop matches your entry to it by name and connects it with your client ID. Without the entry, users get the plugin’s skills but not its Salesforce tools.Enter exactly one URL as the authorization server. To send users to your org’s My Domain login page instead of the shared Salesforce login page, enter that URL, for example ["https://yourorg.my.salesforce.com"].For a Salesforce sandbox org, create the External Client App in the sandbox and enter the sandbox’s login URL as the authorization server, for example ["https://test.salesforce.com"]. Set the URL to https://api.salesforce.com/platform/mcp/v1/sandbox/platform/headless-360.Devices need git installed to fetch the marketplace, and outbound HTTPS access to github.com, api.salesforce.com, and your Salesforce login host.
4

Have users install the plugin and connect

Each user opens Customize → Plugins in Claude Desktop and clicks Discover, which opens the Directory. On its Organization tab the user selects your marketplace’s tab and clicks the + button on the Salesforce plugin to install it. The user then opens Customize → Connectors, clicks Connect next to salesforce-h360, and signs in to Salesforce in the browser.