Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Richa Goyal
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 4, 2026

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,

1 answer

0 votes
Tomislav Tobijas
Community Champion
June 6, 2026

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events