n8n’s MCP Client Tool node lets any LLM step in a workflow call Kataven tools. The node connects over SSE, so you need a tunnel exposing the localDocumentation Index
Fetch the complete documentation index at: https://docs.kataven.ai/llms.txt
Use this file to discover all available pages before exploring further.
kataven-mcp server as an HTTPS SSE endpoint.
Important: n8n’s MCP Client Tool node only accepts SSE endpoint URLs, not local stdio commands. The Kataven MCP server runs locally over stdio, so you need a tunnel — follow the tunnel recipe before continuing here.
This page covers n8n consuming Kataven as a client. n8n also has an MCP Server Trigger node for the reverse — exposing your n8n workflows as MCP tools. That’s out of scope here.
1. Run the tunnel
Follow Tunneling end-to-end. You should end up with a public SSE URL likehttps://abc123.ngrok.app/sse.
2. Add the MCP Client Tool node
In an n8n workflow that already has an LLM step (OpenAI, Anthropic, etc.):- Click + next to your LLM node → search MCP Client Tool → add.
- Wire it to the LLM step’s Tools input (drag the connection).
- Configure:
- SSE Endpoint: the public URL from step 1 (e.g.
https://abc123.ngrok.app/sse). - Authentication: None (the API key lives in your tunnel’s env, not in n8n).
- Tools to Include: All — or pick Selected and choose the subset you want exposed (e.g. read-only tools for a customer-facing workflow).
- SSE Endpoint: the public URL from step 1 (e.g.
3. Test the workflow
Run the workflow with a trigger that fires the LLM step. Ask the LLM:List all Kataven agents and tell me which ones aren’t pinned to a phone number.The LLM picks
kataven_list_agents and kataven_list_phone_numbers from the MCP Client Tool node’s catalog.
4. Verify in the dashboard
| What changed | Open in Hub UI |
|---|---|
| Agents | hub.kataven.ai/agents |
| Phone numbers | hub.kataven.ai/phone-numbers |
| Live or recent calls | hub.kataven.ai/conversations |
| Campaigns | hub.kataven.ai/campaigns |
Operational notes
- Production workflows want a stable URL. Free ngrok URLs change between sessions; switch to Cloudflare Tunnel or a paid ngrok subdomain — see Tunneling § Stable URLs.
- Set credentials per-workflow. Use n8n’s credential store to keep the SSE URL out of the workflow JSON if you share it across team members.