Child Agents cannot use MCP Server Tool added to parent
1. Create a parent agent and add MCP Server tool to the parent
2. Create a child agent and write instruction for the child to use the MCP Server tool
3. Test the agent and the child will not be able to use the tool. No errors. It just stops activity.
Child Agents cannot use MCP Server Tool added to the child
1. Create a parent agent
2. Create a child agent add MCP Server tool to the child
3. In child instructions write instruction for it to use the MCP Server tool
4. Test the agent and the child will not be able to use the tool (in fact if you attempt to use the / command to select a tool, no tool shows in the list). No errors. It just stops activity.
Adding the MCP tool to both parent and child does not work either.
The parent CAN use the MCP Server tool just fine. The child cannot in any configuration. My expectation is that child agents should be able to use different tools independently of the parent or another other children.
My testing was done using the official Dataverse MCP Server, but I don't think the server choice matters because it never even gets invoked.
Appears to be a current limitation: child agents can’t invoke MCP tools (they just stall).
Workaround is host the MCP tools on a separate agent and connect it to the parent; ensure it’s in the same environment, published, and “Let other agents connect” is on.
Also turn on generative orchestration (required for MCP); with these prereqs, it works consistently.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
59
Share
Report
All responses (
Answers (
