default protocol version for streamable should not be 2024-11-05 use 2025-03-26

[olamy]

Signed-off-by: Olivier Lamy [email protected]

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[tzolov]

Thanks @olamy
Unfortunately the ecosystem reality out there is not that puristic. Check this: #444
Basically the streamable http client/server must pretend they support 2024-11-05 to work with the various complaint mcp client/server implementations. Because of this your code needs to changes to something like:

	@Override
	public List<String> protocolVersions() {
		return List.of(ProtocolVersions.MCP_2024_11_05, ProtocolVersions.MCP_2025_03_26);
	}

[olamy]

@tzolov thanks I have been doing this here https://github.com/jenkinsci/mcp-server-plugin/pull/26/files#diff-7bcf4a0ac9d490967a71ec30f02f69b4f578df2c645f7e13a3b39b0760360fe7R198 (and will change with next release as returned type will be List<String> rather than String)