Short answer: MCP tools only show up in a workflow’s Dispatch tool node if the MCP server is attached to the agent (or to a Subagent node at that point in the flow) and the tool isn’t disabled. Also note MCP isn’t available in HIPAA or Zero‑Retention workspaces.
What to check
Confirm the MCP server is added in the MCP integrations dashboard and passes the connection test (lists available tools). (elevenlabs.io)
Attach that MCP server to the exact agent used by the workflow: after adding the integration, you must add it to your agent in the agent’s Tools section; otherwise tools won’t be available to the workflow. (elevenlabs.io)
If you only want the MCP tools available at a specific step, add a Subagent node before the Dispatch node and attach/override the “tools available” there; Subagent nodes can update the tools available at that node. (elevenlabs.io)
Use a Dispatch tool node after that; Dispatch nodes execute a specific tool call and route on success/failure. (elevenlabs.io)
In MCP settings, ensure the tool isn’t set to Disabled under Fine‑grained Tool Approval (set to Auto‑approved or Requires approval). Disabled tools won’t be selectable. (elevenlabs.io)
Verify your workspace isn’t using Zero Retention Mode or HIPAA, as MCP is not supported there. (elevenlabs.io)
If you’ve done the above and the Dispatch node still says you have no integrations, please share screenshots of:
the MCP integration detail (showing discovered tools),
the agent’s Tools panel (showing the MCP server attached),
mystic birch
craggy canopy