Support MCP version 2025-11-25

[monrax]

Expected Behavior

Current MCP spec version "2025-11-25" should be supported and added to ProtocolVersions.java

Current Behavior

Currently, only versions "2024-11-05", "2025-03-26", and "2025-06-18" are supported:

java-sdk/mcp-core/src/main/java/io/modelcontextprotocol/spec/ProtocolVersions.java

Lines 1 to 23 in 082444e

	package io.modelcontextprotocol.spec;
	public interface ProtocolVersions {
	/**
	* MCP protocol version for 2024-11-05.
	* https://modelcontextprotocol.io/specification/2024-11-05
	*/
	String MCP_2024_11_05 = "2024-11-05";
	/**
	* MCP protocol version for 2025-03-26.
	* https://modelcontextprotocol.io/specification/2025-03-26
	*/
	String MCP_2025_03_26 = "2025-03-26";
	/**
	* MCP protocol version for 2025-06-18.
	* https://modelcontextprotocol.io/specification/2025-06-18
	*/
	String MCP_2025_06_18 = "2025-06-18";
	}

Tools like modelcontextprotocol/inspector only work with the current spec version (see modelcontextprotocol/inspector#962), and this SDK does not support it.

Context

Trying to debug an MCP server using the MCP inspector tool.

[alexcheng1982]

The supported version should only be updated when that version is actually supported.

From my testing using MCP inspector v0.18.0, the tool works fine with protocol version 2025-03-26 returned by the server.

io.modelcontextprotocol.server.McpAsyncServer : Client initialize request - Protocol: 2025-11-25, Capabilities: ClientCapabilities[experimental=null, roots=RootCapabilities[listChanged=true], sampling=Sampling[], elicitation=Elicitation[]], Info: Implementation[name=inspector-client, title=null, version=0.18.0]
io.modelcontextprotocol.server.McpAsyncServer : Client requested unsupported protocol version: 2025-11-25, so the server will suggest the 2025-03-26 version instead

[chemicL]

It is planned, absolutely. Please track individual items of interest on the project board as described in our roadmap.

[chemicL]

Resolved through #1025. The 2025-11-25 is now implemented.