#Hey how does MCP servers integrate with
sour obsidian
Hey, currently, MCP server tools are configured at the agent level, not per sub-agent. When you connect an MCP server to your agent, all sub-agents in the workflow have access to all tools from that server. Unfortunately, this is not currently supported. The "Additional custom tools" option in workflow nodes only works with custom tools (webhook/client tools), not MCP server tools.
We have it on radar but not sure about roadmap yet
low gate
ahhh
AHHH this would make my life soo much easier!!
When building custom agents for clients having to create tools and manage them every time is becoming such a pain!
I still want the granularity for deciding subAgents and have access to which tools are available to it
If i were to expect this feature, what’s the ballpark waiting time!
queen narwhal
Hey, currently, MCP server tools are configured at the agent level, not per sub-...
hiya - apologies for the ping on an old thread, been looking at workflow/mcp related things. What you're saying is that if we have the MCP configured on the main agent, we can tell the workflow subagents to call those tools but can't add the integration manually?
sour obsidian
heya, sure np, yeap thats correct , If you configure an MCP server on your main agent, all workflow sub-agents automatically have access to those MCP tools
You don't need to (and currently can't) add the MCP integration manually at the workflow node level.
The "Additional custom tools" option in workflow nodes is only for webhook/client tools, not MCP server tools. MCP tools configured on the main agent are automatically available to all sub-agents. We have per-node MCP configuration on our radar but not sure when we are able to implement this
queen narwhal
coolio, we'll fiddle around with it
low gate
any timelines on when we can get individual subagent level control ?
I want to expose only a certain tools from the MCP in a subAgent