From ca608e5a3a17a8fa91f8a3bed035a68a5076f9ee Mon Sep 17 00:00:00 2001 From: oleg Date: Tue, 15 Apr 2025 18:34:12 +0200 Subject: [PATCH] Clarify limitation MCP trigger limitations in queue mode (#3084) --- .../core-nodes/n8n-nodes-langchain.mcptrigger.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger.md index b4a2888e4..f0fddf369 100644 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger.md +++ b/docs/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger.md @@ -94,7 +94,16 @@ Be sure to replace the `` and `` placeholders with th ## Limitations -The MCP Server Trigger node doesn't yet support n8n instances running in [queue mode](/hosting/scaling/queue-mode.md) mode. +**MCP Trigger and Webhook Replicas** +The MCP Trigger node relies on Server-Sent Events (SSE), which require the same server instance to handle persistent connections. + +* If you run n8n in [queue mode](/hosting/scaling/queue-mode.md) with only a **single webhook replica**, MCP Trigger will work as expected. +* If you run **multiple webhook replicas**, make sure that you route all `/mcp*` requests to a single, dedicated webhook replica. +* To achieve this, create a separate replica set with one webhook container for MCP requests, and update your ingress or load balancer configuration to direct all `/mcp*` traffic to that instance. + +/// warning | MCP Trigger with Multiple Webhook Replicas +If you run MCP Trigger with multiple webhook replicas and don't route all `/mcp*` requests to a single, dedicated webhook replica, SSE connections will frequently break or fail to deliver events reliably. +/// ## Related resources