---
title: "Comment by Jorge Demetrio Sobieski Teixeira on \"Spring AI MCP Client-Server with SSE Transport\" | Hashnode"
description: "Nice walkthrough on the SSE setup. One thing worth flagging for anyone wiring the client side with the new SDK 2.0.0: if the server speaks Streamable HTTP but y"
url: "https://hashnode.com/posts/spring-ai-mcp-client-server-with-sse-transport/688705c0f4aa712a52a935d7/comment/6a3daa188f72479048aeb903"
---

[Discussion](https://hashnode.com/posts/spring-ai-mcp-client-server-with-sse-transport/688705c0f4aa712a52a935d7)

Comment [Spring AI MCP Client-Server with SSE Transport](https://hashnode.com/posts/spring-ai-mcp-client-server-with-sse-transport/688705c0f4aa712a52a935d7)

[Jorge Demetrio Sobieski Teixeira](https://hashnode.com/@jorgedemetrio)

[Jun 25](https://hashnode.com/posts/spring-ai-mcp-client-server-with-sse-transport/688705c0f4aa712a52a935d7/comment/6a3daa188f72479048aeb903)

Nice walkthrough on the SSE setup. One thing worth flagging for anyone wiring the client side with the new SDK 2.0.0: if the server speaks Streamable HTTP but your client uses the legacy SSE transport, listTools() just comes back empty with no error. Same trap if you call it before initialize(), since the handshake is what makes the server advertise its tools. I put together a wrong-vs-right breakdown (pure SDK, Spring AI and Quarkus) over on Meu Universo Nerd if anyone wants the full code.

[Thirumurthi S](https://hashnode.com/@thirumurthi)

[Jun 26](https://hashnode.com/posts/spring-ai-mcp-client-server-with-sse-transport/688705c0f4aa712a52a935d7/comment/6a3daa188f72479048aeb903#reply-6a3de29d6680692f65ce6bd8)

Thanks for the feedback. Sure will check the source code.
