Agentforce Agent is unable to call the mcp tools added in its subagent actions

[Richa Goyal]

The implementation is regarding, search case real time created in Salesforce org1 in another Salesforce org2 via MCP tool.
To achieve this, high level flow is

Org1 new case -> Record triggered flow -> Agentforce agent( which has mcp tools added in actions from another salesforce org2) -> Agent will
check the similar case, ask for its summary and resoltion tips -> Get the response -> Update the response in custom field of case created in org1

Agentforce agent name 'Agent MCP Connector' is created on org https://orgfarm-c75d4f4013-dev-ed.develop.my.salesforce-setup.com/.
The same org has MCP registered name 'SalesforceMCPServerTools' for another salesforce org https://orgfarm-8c5ab65c84-dev-ed.develop.my.salesforce-setup.com/
Permission set for MCP 'SalesforceMCPServerTools' is assigned to Agentforce user.

Org2 'https://orgfarm-8c5ab65c84-dev-ed.develop.my.salesforce-setup.com/' has External client created 'Connect another Salesforce Org'.

I am successfuly able to call org2 MCP tools in Claude AI and its working fine.

But while calling the same from Salesforce Org1 Agentforce agent it has some error, it says 'I was unable to retrieve information for case number 00001002 due to a system error.'

I have already checked any console errors or Network call, no clue.

Please provide the solution if any,

[Richa Goyal]

Hi @Tomislav Tobijas 

Thank you for the reply, I am trying to use Rovo MCP via 'OAuth 2.0 with 2LO' and seems like it does not support this as of now.

Is the any communication happened by Atlassian if they are going to support 'OAuth 2.0 with 2LO' soon?

Thanks,

Richa

[Tomislav Tobijas]

Hey @Richa Goyal ,

Officially, there's no mention that it supports OAuth 2.0 with 2LO (for standard remote connections.

An alternative way would be to use API tokens (basic auth for personal tokens or bearer for service accounts).

You could check these feature requests: 

• AX-1603: Allow Service Account Impersonation for OAuth2 App Authorization in Cloud Products 
• ROVO-870: Support for Custom OAuth Applications (BYO-OAuth) and Custom Redirect URIs for Rovo MCP Server 

I haven't played with this much myself, but you could also check/ask in Atlassian Rovo MCP Server to see if anyone can share additional insights about this. 👀

Cheers,
Tobi

[Tomislav Tobijas]

Hi @Richa Goyal ,

Well... this does sound like it might take a while to troubleshoot. Like general pointers are to update endpoint and check OAuth scopes, but I guess you already did that. 👀

You could also try narrowing the search criteria in your Agentforce, as if there are too many results, the system might throw an error.

The error could also indicate that the authenticated user lacks the specific object-level permissions, so again, it could be the scopes 🤔

As this might fall a bit out of my domain, you could also reach out here Atlassian Rovo MCP Server, and see if anyone got some additional insights. 
I'm also not sure if Developer community has any dedicated section for MCP-related stuff, but folks there could definitelly help out more.

If nothing works, and this is critical for the implementation, you could start a free trial (e.g., Jira) to be able to raise a ticket here Atlassian Support, as this is the official support channel now for MCP-related stuff.

Cheers,
Tobi