Skip to main content
Salesforce MCP connects a Salesforce hosted MCP (Model Context Protocol) server to Cargo so AI agents can call Salesforce tools directly. It is separate from the regular Salesforce CRM connection: each Salesforce org exposes its own MCP server URL, and authorization uses an External Client App you create in that org (mcp_api scope). Salesforce does not support Dynamic Client Registration for hosted MCP, and an External Client App is not installed into another org on first OAuth (unlike a classic Connected App). Cargo therefore uses the same pattern as Claude, ChatGPT, Cursor, and Postman: you create the app in your org and paste its consumer key and secret into Cargo.

​
How to set up Salesforce MCP

​
1. Activate a hosted MCP server

In Salesforce Setup > MCP Servers, open the Salesforce Servers tab, activate a server, and copy its Server URL. Production and sandbox URLs differ (/platform/mcp/v1/ vs /platform/mcp/v1/sandbox/).

​
2. Create an External Client App

Connected Apps are not supported for MCP. In the same org as the server URL:
  1. Setup > Quick Find > External Client App Manager > New External Client App
  2. Set Distribution State to Local (not Packaged)
  3. Enable OAuth and configure:
    • Callback URL: https://app.getcargo.io/oauth-callback (Cargo also shows this on the connector form)
    • Scopes: Access MCP servers (mcp_api) and Perform requests at any time (refresh_token / offline_access)
    • Issue JWT-based access tokens for named users: on
    • Require PKCE: on
    • Require Secret for Web Server Flow: on
  4. Save, then copy the Consumer Key and Consumer Secret from the app’s OAuth settings
A new External Client App can take up to 30 minutes to become usable. See Salesforce’s Create an External Client App guide.

​
3. Connect in Cargo

  1. Create a Salesforce MCP connector
  2. Turn on Use sandbox? if the org is a sandbox or scratch org
  3. Paste the MCP Server URL, Consumer Key, and Consumer Secret
  4. Click Authorize Salesforce MCP and sign in to that org
  5. Cargo stores the resulting token and refreshes it automatically
Code slugs — integration slug: salesforceMcp. This integration exposes no fixed actions: its tools are discovered from your org’s MCP server at runtime and made available to agents.

​
Salesforce MCP tools

The connector does not define static actions. When attached to an agent as an MCP server, the agent lists the tools your Salesforce MCP server advertises at runtime and can call any of them. See MCP servers for how agents use MCP tools. Related MCP integrations: HubSpot MCP and Notion MCP.

​
Best practices

  • Use Salesforce MCP for agent tool use; keep the regular Salesforce connector for workflow actions and data syncing
  • Create the External Client App in the same org you authorize with — the server URL is org-specific
  • Authorize with a Salesforce user whose permissions match what you want agents to be able to do
  • If Salesforce returns OAUTH_EC_APP_NOT_FOUND, the consumer key does not belong to the org you logged into (wrong org, or the app is Packaged but not installed)