[FEATURE] Inquiry Regarding MCP's SSE Communication Release

[GG3T]

Inquiry Regarding MCP's SSE Communication Release

I would like to know when MCP's SSE communication will be enabled. Could you please provide an update on the expected timeline?

[faanskit]

I think it is already supported. In version 2.2.7-patch.1 I can connect to a locally hosted MCP using SSE. It can connect both to n8n MCP servers and locally hosted server based on FastMCP.

Here's my sample config: Local n8n

{
  "command": "npx",
  "args": [
        "-y",
        "supergateway",
        "--sse",
        "http://192.168.1.170:5678/mcp/mcp_test/sse"
  ]
}

Local FastMCP

{
  "command": "npx",
  "args": [
    "-y",
    "supergateway",
    "--sse",
    "http://192.168.1.246:8080/sse"
  ]
}

[sei-dupdyke]

The solution above does not work for me, and this video makes the claim that npx commands do not work.

Any idea when this is coming?

[internationalvillager]

Hi everyone,

I was able to get things working locally by invoking the gateway directly via an npx/node command. Here’s a redacted example (paths and IPs replaced with placeholders):

{ "command": "node", // Specifies that the 'node' runtime should be used "args": [ "/node_modules/@latitude-data/supergateway/dist/index.js", // Path to the SuperGateway script "--sse", // Flag to enable SSE (Server-Sent Events) support "<YOUR_SSE_ENDPOINT>", // Replace with your actual SSE endpoint URL "--timeout", // Flag to set a custom timeout for the connection "600000" // Timeout duration in milliseconds (600,000ms = 10 minutes) ] }

[cnguyen86]

Hi @GG3T, @sei-dupdyke there is new version 2.2.8 which support SSE now, you can see the PR here https://github.com/FlowiseAI/Flowise/pull/4329