Release 0.11.0

[alexander-atlassian]

Hello, when is 0.11.0 going to be released? The latest release was 0.10.0 back in May. We need 0.11.0 for the Streamable HTTP client and would greatly appreciate if this is released.

[luyiourwong]

You can already try the latest snapshot version with Streamable HTTP from Maven Central.
Here’s an example of how to add it to your build.gradle:

repositories {
	maven {
		name = 'Central Portal Snapshots'
		url = 'https://central.sonatype.com/repository/maven-snapshots/'
	}
}

dependencies {
	implementation 'io.modelcontextprotocol.sdk:mcp:0.11.0-SNAPSHOT'
	implementation 'io.modelcontextprotocol.sdk:mcp-spring-webflux:0.11.0-SNAPSHOT'
}

[alexander-atlassian]

Thank you, yep, that works in the short term.

Do you know when to expect the next release? Is there a release schedule for official releases?

[prakashsaraff]

I do not see the server implementation of "/mcp" endpoint in WebFluxSseServerTransportProvider. The "/sse" endpoint is configured for only "GET". Also, the latest protocol is still "2024-11-05"
Will 0.11 release support the server implementation of "/mcp" as well as move to latest version "2025-03-26"? Or what are the high level changes we can expect in 0.11?

[alexander-atlassian]

Hello @tzolov (and any other active maintainers) any chance you could let us know when 0.11.0 is planned to be released? Is there a release schedule? We prefer not to use the snapshot version.

[fabb]

You can already try the latest snapshot version with Streamable HTTP from Maven Central. Here’s an example of how to add it to your build.gradle:

repositories {
	maven {
		name = 'Central Portal Snapshots'
		url = 'https://central.sonatype.com/repository/maven-snapshots/'
	}
}

dependencies {
	implementation 'io.modelcontextprotocol.sdk:mcp:0.11.0-SNAPSHOT'
	implementation 'io.modelcontextprotocol.sdk:mcp-spring-webflux:0.11.0-SNAPSHOT'
}

@luyiourwong I still only see the HttpServletSseServerTransportProvider in this snapshot version, and no transport for Streamable HTTP, am I overlooking something? Note that I do not use Spring and therefore have to use a Servlet Transport.

[tzolov]

Hey everyone. Our intention is to make the 0.11.0 release around 25.07.2025

[bharat-avn-14416]

Can you give us a list features that will be available in this 0.11.0 release? Importantly we are expecting you to release the Streamable HTTP CLIENT and SERVER support. @tzolov Knowing this can really help us manage our tasks right now. Thanks in advance!

[tzolov]

@bharat-avn-14416 below is the wip. Full streamable http client/server support is pre-requisite for 0.11.0

Feature	Java SDK	Notes
Protocol Version 2024-11-05
Ping	✅⚠️	Client/server pings #203��Add Server ability to send ping request:�#347
Resources	✅	Basic resource management
Resource Subscription	✅	https://github.com/modelcontextprotocol/java-sdk/pull/264
Prompts	✅	Prompt templates
Tools	✅	Function execution
Sampling	✅	LLM interactions #327
Roots	✅	Filesystem boundaries It is already supported
Logging	✅	Structured logging
Progress	✅	Progress tracking https://github.com/modelcontextprotocol/java-sdk/pull/300�https://github.com/modelcontextprotocol/java-sdk/pull/351�https://github.com/modelcontextprotocol/java-sdk/pull/352 #375�#407
Completions	✅⚠️	Prompt and resource template autocompletion Java SDK only supports exact matches on prompts and resource template arguments? Python SDK supports providing a custom implementation.
Cancellation	✅	Request cancellation
stdio Transport	✅	Process communication
HTTP+SSE Transport	✅	Server-sent events
Protocol Version 2025-03-26
OAuth 2.1 Authorization	❌	Authorization servers and dynamic client registration
Streamable HTTP Transport	- webflux-client [✅]�- http-client [✅]�- servlet-server [⚠️]�- webflux-server [⚠️] - webmvc-server [❌]	Replaces HTTP+SSE�~~http-client: #337~~�Servlet-server: #290�Webflux-server: #420
JSON-RPC Batching	❌	Multiple requests - Deprecated
Tool Annotations	✅	Enhanced metadata #313
Audio Content	✅	Audio support in resources�#243
Completions Capability	✅	Explicit autocompletion ??? I believe this is covered.
Progress message	✅	Optional message on notifications https://github.com/modelcontextprotocol/java-sdk/pull/407 �https://github.com/modelcontextprotocol/java-sdk/pull/300�https://github.com/modelcontextprotocol/java-sdk/pull/351�https://github.com/modelcontextprotocol/java-sdk/pull/352�~~#375~~
Resource size	✅	Optional size on Resource #331
Protocol Version 2025-06-18
OAuth 2.1 Resources	❌	Resource servers�#388
OAuth 2.1 Resource Indicators (RFC8707)	❌
Security Best Practices	❌	Enhanced security guidance �#284
JSON-RPC Batching	❌	Removed in draft
Structured Tool Output	✅⚠️[client side validation]	#302�https://github.com/modelcontextprotocol/java-sdk/pull/408 #357
Resource Links	✅	Surbhi picking this up as she waits for OAuth to get unblocked�#341 - created a PR
Version Negotiation	❌	Anurag and Surbhi working on this
Protocol Version Header	⚠️WIP	Delayed until Version Negotiation is implemented Suggestion for a hack until the negotiation is in place: #404
Metadata	✅	Anurag to pick this up https://github.com/modelcontextprotocol/java-sdk/pull/368
Titles	✅	Surbhi to pick this up�https://github.com/modelcontextprotocol/java-sdk/pull/372
Completion Context	✅	Surbhi to pick this up https://github.com/modelcontextprotocol/java-sdk/pull/369

Legend:
- ✅ Full support
- ⚠️ Partial support or unclear from documentation
- ❌ Not supported

[topikachu]

Just to confirm — since #290 hasn't been merged yet, this release doesn't include server-side stream transport, right?