My agent currently calls a self-hosted mcp via the mcp tool. I'm looking into VAPI workflows, and while the progress since a few months ago has been tremendous, I don't seem to be able to select my mcp tool in the Tool Node. Is this intended?

I don't have access to my mcp in the workflow, and it's a problem because the built in vapi api request tools doesn't manage query params in the request

Create and configure your MCP tool in the VAPI dashboard, add it to your assistant under the Tools tab, then select it in the workflow’s Tool Node..

I only have querires and transfer calls available in the workflow tool node. In the assistant version we have it configured, my understanding is that assistant/workflows are standalon? Are you saying you can create an assistant, then select it as a node in workflows? https://cdn.discordapp.com/attachments/1405080374044004424/1406135708271247360/image.png?ex=68a15d6d&is=68a00bed&hm=c7d005496e3f8ea0ff966d36cc7c1b5832151ecb8ffc66b947186e74e871380d& https://cdn.discordapp.com/attachments/1405080374044004424/1406135708774695032/image.png?ex=68a15d6d&is=68a00bed&hm=f3cb78e22d5e9306ac8c790a5e2c4c33631b09bf834e7d78bf1d8d810db71d0a&

Sorry for the misunderstanding, but we are saying that you can use an MCP tool in the workflow if you create it. If you create a tool that can be linked with an assistant, the tool can also be linked to the workflow. You are correct in the way that assistants and workflows are two different systems and they work separately from each other

Ah I hear you, not sure if I'm doing something wrong then - in the first screen shot there's no option to select my mcp tools (ie the mcp-j57... you see in ss 2 which is linked to an agent)

Interesting. It's possible that it's an API exclusive option because it is in the documentation here -->