Transition from Beta

If you integrated with the Salesforce hosted MCP server during the pilot or beta period, you'll need to complete a few steps to reconnect using the GA release. The changes are straightforward, and your underlying Salesforce configuration — permissions, sharing rules, data — is unchanged.

Three things change between the beta and GA release:

The server URL changes. The beta service used a versioned URL path (v1-beta.2) that is specific to the pre-GA infrastructure. The GA release uses a new URL format. Any MCP client configuration that references the old URL will stop working once beta access is retired, so you'll need to update the server URL in each client that was connected during beta.

MCP servers must be enabled. In the GA release, MCP servers are disabled in your org by default and must be explicitly enabled by an administrator. This is a deliberate security posture: org capabilities that expose data to external systems should require an intentional administrator action to turn on. If your servers aren't enabled, clients will not be able to connect, even with correct authentication.

OAuth scopes change. The beta required a set of individual scopes (api, sfap_api, refresh_token, einstein_gpt_api). At GA, these are replaced by two scopes: mcp_api and refresh_token. You'll need to update the scope configuration in your External Client App and in each connected MCP client.

The fundamental connection model is unchanged. You'll still use an External Client App (ECA) for OAuth authentication, and the same per-user permission model governs what agents can access. Your existing ECA can be reused — you don't need to create a new one, though you will need to update its scope configuration as noted above.

The tools available in each server, and the behavior of those tools, are also unchanged. Integrations and prompts built during beta should work without modification once clients are reconnected to the GA endpoints.

  1. Enable MCP servers in Setup. An administrator must navigate to Setup → API Catalog → MCP Servers and enable the servers your team uses. Servers are disabled by default at GA.
  2. Update OAuth scopes. In your External Client App, remove the beta scopes (api, sfap_api, refresh_token, einstein_gpt_api) and replace them with mcp_api and refresh_token. Update the scope value in each MCP client configuration as well.
  3. Update server URLs in your MCP clients. In each connected client, update the server URL to use the GA endpoint format. Refer to Connecting an MCP Client for client-specific instructions.
  4. Reauthorize. After updating the URL and scopes, each user will be prompted to authorize the connection again. This is expected — tokens issued during beta are not valid for the GA service.
  5. Verify. Confirm the connection is working by running a simple tool call (for example, a simple SOQL query) and checking that it returns expected results.