Background
The community member had tried accessing the Agentforce Registry in their new sandbox, but was unable to access the MCP Beta.
Robbie Duncan suggested that as a beta, the MCP client may never be available in sandboxes, and that it may only be possible once it goes GA.
Current Status
Even in orgs where the MCP client is available, it does not currently work with the new Agent Builder, which is also in beta.
There is hope that the MCP client will go GA sometime around TDX, and that it will work together with the new Agent Builder.
The root cause of this issue is that the MCP client is not currently available in Agentforce/Data 360 sandboxes, and that it may only be possible once it goes GA.
Next Steps
Teams running Agentforce should keep an eye on the Salesforce blog and release notes for updates on the MCP client and new Agent Builder.
Checklist
- Check the Salesforce blog for updates on the MCP client and new Agent Builder
- Keep an eye on the release notes for Agentforce and Data 360
- Test the MCP client and new Agent Builder in a production org once they are GA
- Provide feedback to Salesforce on the MCP client and new Agent Builder
- Attend TDX for the latest updates on Agentforce and Data 360
What is the MCP client?
The MCP client is a beta feature that allows users to access the Agentforce Registry in their org.
What is the new Agent Builder?
The new Agent Builder is a beta feature that allows users to build and manage agents in their org.
When will the MCP client go GA?
The MCP client is expected to go GA sometime around TDX.
Will the MCP client work with the new Agent Builder?
It is hoped that the MCP client will work with the new Agent Builder, but this has not been confirmed.
Need help shipping this in production?
Genetrix builds and untangles Salesforce Marketing Cloud and Agentforce setups for teams that want it done right the first time. If anything in this post sounds familiar, talk to us before it ships.
