Skip to content

Support MCP version 2025-11-25 #715

Closed

Description

@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:

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.

Activity

  1. alexcheng1982 commented on Dec 18, 2025

    @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
    
  2. chemicL commented on Feb 20, 2026

    @chemicL
    Member

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

  3. added
    enhancementNew feature or request
    P1Significant bug affecting many users, highly requested feature
    on Feb 20, 2026
  4. chemicL commented on Jun 11, 2026

    @chemicL
    Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Significant bug affecting many users, highly requested featureenhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions