Connect to Salesforce changedthird-party/claude-desktop/connectors-salesforce
Nearest release: v2.1.276, published 2 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 17 Sep 2026 23:06 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+51added
Lines−53removed
From line
6
where the diff opens
First seen
17 Sep 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 6, old and new numbered
/
from line 6
66
77## Set up Salesforce
88
9<Steps>
10 <Step title="Prepare your Salesforce org">
11 In Salesforce Setup, turn on **Enable MCP Service**, then create an External Client App for Claude Desktop with these OAuth settings:
9**1. Prepare your Salesforce org**
1210
13 * The callback URL `http://127.0.0.1:53280/callback`
14 * The OAuth scopes `mcp_api` and `refresh_token`
15 * Proof Key for Code Exchange (PKCE) required
16 * Access tokens issued as JSON Web Tokens (JWTs)
17 * An OAuth policy that lets users self-authorize
11In Salesforce Setup, turn on **Enable MCP Service**, then create an External Client App for Claude Desktop with these OAuth settings:
1812
19 Copy the app's **Consumer Key**, which is its client ID. With PKCE, Claude Desktop needs no client secret.
20 </Step>
13* The callback URL `http://127.0.0.1:53280/callback`
14* The OAuth scopes `mcp_api` and `refresh_token`
15* Proof Key for Code Exchange (PKCE) required
16* Access tokens issued as JSON Web Tokens (JWTs)
17* An OAuth policy that lets users self-authorize
2118
22 <Step title="Add the Salesforce marketplace">
23 **In the Enterprise Admin Console.** Go to [claude.ai](https://claude.ai) → **Organization 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**.
19Copy the app's **Consumer Key**, which is its client ID. With PKCE, Claude Desktop needs no client secret.
2420
25 **With MDM or a bootstrap server.** Add this entry to the [`allowedPluginMarketplaces`](/docs/third-party/claude-desktop/configuration#allowedpluginmarketplaces) key of your managed configuration or bootstrap response:
21**2. Add the Salesforce marketplace**
2622
27 ```json theme={null}
28 {
29 "source": "github",
30 "repo": "salesforce/salesforce-skills",
31 "ref": "claude-prod"
32 }
33 ```
23**In the Enterprise Admin Console.** Go to [claude.ai](https://claude.ai) → **Organization 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**.
3424
35 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](/docs/third-party/claude-desktop/extensions#marketplace-installation-preferences) explains why the SHA is required, and [Roll out marketplace updates](/docs/third-party/claude-desktop/extensions#roll-out-marketplace-updates) explains how to move to a newer release.
36 </Step>
25**With MDM or a bootstrap server.** Add this entry to the [`allowedPluginMarketplaces`](/docs/third-party/claude-desktop/configuration#allowedpluginmarketplaces) key of your managed configuration or bootstrap response:
3726
38 <Step title="Add the Salesforce MCP server">
39 **In the Enterprise Admin Console.** Go to [claude.ai](https://claude.ai) → **Organization 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](/docs/third-party/claude-desktop/mcp-sign-in) explains each **OAuth** field, and users' apps pick up console changes as described under [Configuration updates](/docs/third-party/claude-desktop/admin-console#configuration-updates).
27```json theme={null}
28{
29 "source": "github",
30 "repo": "salesforce/salesforce-skills",
31 "ref": "claude-prod"
32}
33```
4034
41 | Field | Value |
42 | - | - |
43 | **Name** | `salesforce-h360` |
44 | **Transport** | **Streamable HTTP** |
45 | **URL** | `https://api.salesforce.com/platform/mcp/v1/platform/headless-360` |
46 | **OAuth** | **Bring your own client** |
47 | **Client ID** | The Consumer Key from step 1 |
48 | **Authorization server** | `["https://login.salesforce.com"]` |
35Either 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](/docs/third-party/claude-desktop/extensions#marketplace-installation-preferences) explains why the SHA is required, and [Roll out marketplace updates](/docs/third-party/claude-desktop/extensions#roll-out-marketplace-updates) explains how to move to a newer release.
4936
50 **With MDM or a bootstrap server.** Add this entry to the [`managedMcpServers`](/docs/third-party/claude-desktop/configuration#managedmcpservers) key of your managed configuration or bootstrap response:
37**3. Add the Salesforce MCP server**
5138
52 ```json theme={null}
53 {
54 "name": "salesforce-h360",
55 "transport": "http",
56 "url": "https://api.salesforce.com/platform/mcp/v1/platform/headless-360",
57 "oauth": {
58 "clientId": "YOUR_CONSUMER_KEY",
59 "authorizationServer": ["https://login.salesforce.com"]
60 }
61 }
62 ```
39**In the Enterprise Admin Console.** Go to [claude.ai](https://claude.ai) → **Organization 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](/docs/third-party/claude-desktop/mcp-sign-in) explains each **OAuth** field, and users' apps pick up console changes as described under [Configuration updates](/docs/third-party/claude-desktop/admin-console#configuration-updates).
6340
64 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.
41| Field | Value |
42| - | - |
43| **Name** | `salesforce-h360` |
44| **Transport** | **Streamable HTTP** |
45| **URL** | `https://api.salesforce.com/platform/mcp/v1/platform/headless-360` |
46| **OAuth** | **Bring your own client** |
47| **Client ID** | The Consumer Key from step 1 |
48| **Authorization server** | `["https://login.salesforce.com"]` |
6549
66 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"]`.
50**With MDM or a bootstrap server.** Add this entry to the [`managedMcpServers`](/docs/third-party/claude-desktop/configuration#managedmcpservers) key of your managed configuration or bootstrap response:
6751
68 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`.
52```json theme={null}
53{
54 "name": "salesforce-h360",
55 "transport": "http",
56 "url": "https://api.salesforce.com/platform/mcp/v1/platform/headless-360",
57 "oauth": {
58 "clientId": "YOUR_CONSUMER_KEY",
59 "authorizationServer": ["https://login.salesforce.com"]
60 }
61}
62```
6963
70 Devices need git installed to fetch the marketplace, and outbound HTTPS access to `github.com`, `api.salesforce.com`, and your Salesforce login host.
71 </Step>
64Keep 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.
7265
73 <Step title="Have users install the plugin and connect">
74 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.
75 </Step>
76</Steps>
66Enter 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"]`.
67
68For 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`.
69
70Devices need git installed to fetch the marketplace, and outbound HTTPS access to `github.com`, `api.salesforce.com`, and your Salesforce login host.
71
72**4. Have users install the plugin and connect**
73
74Each 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.
7775
No line in this hunk matches that.