Why does MCP sse client do not have heartbeat detection

[Ltyro]

Please do a quick search on GitHub issues first, the feature you are about to request might have already been requested.

Expected Behavior

After the MCP SSE server restarts, the client can automatically connect without restarting

Current Behavior

After the MCP SSE server restarts, the client will not automatically connect

Context

In MCP SSE mode, the client must rely on the MCP server to start, otherwise it cannot start. I don't think it's reasonable. The server has been restarted, so all clients need to be restarted? Why not use heartbeat detection. The MCP native SDK may not have a heartbeat mechanism, but I think Spring AI can have it.

[1435646097]

Yes, I think so too

[andresssantos]

I'm facing the same situation, where I have to restart my client every time something changes in the mcp server. I wonder if there's something to avoid that.

[Ltyro]

I tried to rewrite the client auto configuration the day before tomorrow, but I haven't finished writing it yet. The idea is to connect by heartbeat monitoring. If client.ping() goes through, then execute initialization method. If the server is disconnected, create a loop to ping, and create a client until the ping is connected. However, I haven't continued to write because I've been on vacation recently. If you are interested, you can try it.

[tinomthomas]

I think this is a much needed feature especially in auto adjusting environments like Kubernetes where an auto scale down happens based on the load.