Brothers, when will the Kotlin SDK support Streamable HTTP? #346

Activity

1. bczhaoa

   added

   enhancementNew feature or requestNew feature or request

   on Oct 25, 2025
2. Moyuyanli commented on Oct 28, 2025

   

   Moyuyanli

   on Oct 28, 2025

   More actions

   不是支持吗？
3. bczhaoa commented on Oct 28, 2025

   

   bczhaoa

   on Oct 28, 2025

   Author

   More actions

   no. no support
4. Moyuyanli commented on Oct 28, 2025

   

   Moyuyanli

   on Oct 28, 2025

   More actions

   I implemented it after modifying some StreamableHttpClientTransport code.
5. bczhaoa commented on Oct 28, 2025

   

   bczhaoa

   on Oct 28, 2025

   Author

   More actions

   Could you post your code for reference?
6. Moyuyanli commented on Oct 28, 2025

   

   Moyuyanli

   on Oct 28, 2025

   More actions

   My solution isn't particularly elegant; it just gets the job done.

   Replace the following code in the send method:

   // if (response.status == HttpStatusCode.Accepted) {
   // if (message is JSONRPCNotification && message.method == "notifications/initialized") {
   // startSseSession(onResumptionToken = onResumptionToken)
   // }
   // return
   // }

   With:

   when (response.contentType()?.withoutParameters()) {
   ContentType.Application.Json -> {
   val body = response.bodyAsText()
   if (body.isNotBlank()) {
   runCatching { McpJson.decodeFromString<JSONRPCMessage>(body) }
   .onSuccess { _onMessage(it) }
   .onFailure { _onError(it); throw it }
   }
   }
   
   ContentType.Text.EventStream -> {
   // Handle all streaming responses here
   handleInlineSse(
   response,
   replayMessageId = if (message is JSONRPCRequest) message.id else null,
   onResumptionToken = onResumptionToken
   )
   }
   
   else -> {
   if (response.status.isSuccess()) {
   return // Normal no-content response
   }
   val error =
   StreamableHttpError(response.status.value, "Unexpected content type: ${response.contentType()}")
   _onError(error)
   throw error
   }
   }

   Then, simply modify the handleInlineSse() method to make it compatible with handling other types of responses.
7. devcrocod commented on Oct 28, 2025

   

   devcrocod

   on Oct 28, 2025

   Contributor

   More actions

   Streamable http for the client was introduced in version 0.6.0.

   We’re currently working on adding streamable HTTP support for the server. There’s an open pr #235 by @zshea, and I’ve also been implementing a streamable HTTP server in my branch
8. bczhaoa commented on Oct 28, 2025

   

   bczhaoa

   on Oct 28, 2025

   Author

   More actions

   Thank you very much, looking forward to an early release of a version with support.
9. kpavlov

   marked this as blocked by 2 issues on Nov 19, 2025

   • Server example - streamable #170
   • Adding Streaming HTTP Transport #79
10. bczhaoa commented on Dec 26, 2025

    

    bczhaoa

    on Dec 26, 2025

    Author

    More actions

    It's been two months now, and there's been no progress at all. Is this issue being addressed? When is it planned to be resolved? Could you please provide a clear answer? I'm thinking of switching to the Java SDK. @devcrocod @kpavlov
11. karthyks commented on Dec 29, 2025

    

    karthyks

    on Dec 29, 2025

    More actions

    Java SDK - Tightly coupled with Spring framework
    Quarkus SDK - Not many contributions, but at least supports Streamable HTTP for server.
    Kotlin SDK - Far behind in features.

    Maybe JVM is just not right for AI tooling. I hope I am wrong in 2026.
12. devcrocod commented on Apr 8, 2026

    

    devcrocod

    on Apr 8, 2026

    Contributor

    More actions

    Streamable HTTP is implemented for both client and server as of 0.8.0
13. devcrocod

    closed this as completedon Apr 8, 2026