Server Connection Failures
To troubleshoot server connection issues:
Step 1: Verify the server URL
Use the URL format that matches your org type and server type:
- For a Sandbox or scratch org with a standard server:
https://api.salesforce.com/platform/mcp/v1/sandbox/platform/sobject-all - For a Developer, Enterprise, other non-sandbox org with a standard server:
https://api.salesforce.com/platform/mcp/v1/platform/sobject-all - For a Sandbox or scratch org with a custom server:
https://api.salesforce.com/platform/mcp/v1/sandbox/custom/myserver - For a Developer, Enterprise, or other non-sandbox org with a custom server:
https://api.salesforce.com/platform/mcp/v1/custom/myserver
Step 2: Confirm that the server is activated
Be sure to activate your Salesforce Hosted MCP servers in the Salesforce UI before use.
Step 3: Test a known server
Try connecting to sobject-all.
- If
sobject-allworks, your original server name or configuration is likely incorrect. - If
sobject-allalso fails, continue to the next steps.
Step 4: Check Org API eligibility
Confirm that your Org edition supports API access (for example, Developer or Enterprise, or Professional with API access enabled).
Step 5: Check for local or client issues
- Confirm that you can log in to Salesforce UI from the same machine or network.
- Test with Postman or MCP Inspector. If those tests succeed, the issue is likely specific to your MCP client settings.