Connection Re-establishment Issue with MCP SSE Server

[jona7o]

Hi,

I am currently developing an MCP server that runs in a Docker container, and my LibreChat instance is also hosted in an AKS Docker container. Both services communicate seamlessly via SSE.

However, I've encountered an issue: when the MCP server restarts due to a node or software update, the connection appears to be lost. Although LibreChat attempts to call the tool, the MCP server indicates that the tool was accessed before the connection was initialized.

Is there a way for LibreChat to automatically re-establish connections to the MCP servers during runtime if they are interrupted?

Best regards,
Tobias

[z0mt3c]

got the same issue, tunneling through npx with supergateway seems to work

[jona7o]

supergateway is a good workaround, even though it is really slow compared to the direct SSE setting, isn't it?

[rsam444]

@jona7o how are you connecting to your mcp server from librechat hosted in AKS? for me the mcp initialization happens to be fine, but post that if im trying to ask some query like fetch some doc using Git MCP, it just keeps loading and no response back.
And strangely i dont see any errors in the logs and also in the console log.
did you face this kind of issue?

[jona7o]

I have added ClusterIP Services to the AKS Cluster to connect via "name.namespace" with internal traffic. But yes there are some cases where I still have problems with librechat and mcp. Starting from unpredictable time how long the startup would take if you use multiple npx/uvx mcp servers to the fact that if a mcp fails it gets lost in the list of mcp tools or even librechat crashes.

[rsam444]

okay, even i tried with the clusterIP DNS inside my librechat.yml config file, but still when i try calling the mcp server, it just keeps running with no error and no response.
is it possible for you to share a snippet of your librechat.yml file with the mcp configuration for my reference?

[benverhees]

@rsam444 @jona7o this is an issue with the SSE transport itself. If your MCP server supports the streamable http transport, or if you can make it support that - most server API's do - you should use streamable http in stead of SSE: https://www.librechat.ai/docs/features/mcp#server-transports

[rsam444]

Thanks @benverhees for your response, but i did try the basic git mcp using streamable http and still i dont see any response coming back, very strange! but during the librechat app startup the initialization looks fine and even the app is able to get the tool list.