Here's the updated bug report with all the new information added:
What happened?
When connecting the Salesforce Hosted MCP sandbox endpoint as a custom connector in claude.ai, the OAuth flow completes successfully (confirmed via Salesforce Setup → OAuth Usage by User), but claude.ai returns "Authorization with the MCP server failed". This has been reproduced across multiple configuration attempts including both the beta and GA endpoints.
Update 17 Apr 2026: Retested with the fully GA setup per official Salesforce documentation ([developer.salesforce.com/docs/platform/hosted-mcp-servers](https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/client-connection-overview.html)) — new v1 endpoint, updated mcp_api scope replacing sfap_api, and OAuth Client ID (consumer key) now populated in claude.ai Advanced settings as required. Issue persists identically. OAuth Usage confirms token issued at 17 Apr 2026 09:14:53 EEST with use count 1, used at 09:14:54 EEST — token is being issued and touched but claude.ai never completes the authenticated MCP handshake.
What did you expect to happen?
After completing OAuth, the Salesforce MCP connector should show as Connected and MCP tools should be available in conversations.
Steps to reproduce
- Create an External Client App in Salesforce sandbox per GA docs:
- Callback URL:
https://claude.ai/api/mcp/auth_callback
- OAuth Scopes:
mcp_api, refresh_token
- Security: JWT-based access tokens enabled, PKCE required, all other options off
- Permitted Users: All users may self-authorize
- In claude.ai Settings → Connectors → Add custom connector:
- URL:
https://api.salesforce.com/platform/mcp/v1/sandbox/platform/sobject-all
- Advanced settings → OAuth Client ID: paste consumer key from External Client App
- Click Connect — Salesforce OAuth completes successfully
- claude.ai returns authorization failed error
Area
OAuth / Authentication
MCP Server
https://api.salesforce.com/platform/mcp/v1/sandbox/platform/sobject-all (Salesforce Hosted MCP GA, sandbox)
Error messages or logs
"Authorization with the MCP server failed."
ofid_5bfa04366863ce53, ofid_a4d0d03b203388be (original beta attempt, 13 Apr 2026)
ofid_a4d0d03b203388be, ofid_6d04c675eb49a972, ofid_ecc5d480c066d07d, ofid_70763555ebfdc06b (beta retries)
ofid_f4da8406d8ff1e36 (GA endpoint attempt, 17 Apr 2026)
Additional context
Here's the updated bug report with all the new information added:
What happened?
When connecting the Salesforce Hosted MCP sandbox endpoint as a custom connector in claude.ai, the OAuth flow completes successfully (confirmed via Salesforce Setup → OAuth Usage by User), but claude.ai returns "Authorization with the MCP server failed". This has been reproduced across multiple configuration attempts including both the beta and GA endpoints.
Update 17 Apr 2026: Retested with the fully GA setup per official Salesforce documentation ([developer.salesforce.com/docs/platform/hosted-mcp-servers](https://developer.salesforce.com/docs/platform/hosted-mcp-servers/guide/client-connection-overview.html)) — new
v1endpoint, updatedmcp_apiscope replacingsfap_api, and OAuth Client ID (consumer key) now populated in claude.ai Advanced settings as required. Issue persists identically. OAuth Usage confirms token issued at 17 Apr 2026 09:14:53 EEST with use count 1, used at 09:14:54 EEST — token is being issued and touched but claude.ai never completes the authenticated MCP handshake.What did you expect to happen?
After completing OAuth, the Salesforce MCP connector should show as Connected and MCP tools should be available in conversations.
Steps to reproduce
https://claude.ai/api/mcp/auth_callbackmcp_api,refresh_tokenhttps://api.salesforce.com/platform/mcp/v1/sandbox/platform/sobject-allArea
OAuth / Authentication
MCP Server
https://api.salesforce.com/platform/mcp/v1/sandbox/platform/sobject-all(Salesforce Hosted MCP GA, sandbox)Error messages or logs
Additional context
{"errors":[{"message":"JWT Token is required"}]}, confirming server is upv1-beta.2) and GA endpoint (v1) — identical failureapi,sfap_api,refresh_token,einstein_gpt_api) and new GA scopes (mcp_api,refresh_token) — identical failure