[BUG] Doesn't support MCP 2025-11-25 protocol version

[Realrubr2]

Problem (one or two sentences)

Current Roocode does not support the latests MCP protocol version.

Context (who is affected and when)

who is affected: people try to use MCP server implemented protocol version: 2025-11-25

Reproduction steps

Install Roo version 3.28.16 within VScode extension
config with any MCP server which implemented protocol version 2025-11-25
Get error

Expected result

Roo should support MCP server

Actual result

Server's protocol version is not supported: 2025-11-25

Variations tried (optional)

No response

App Version

Version: 3.51.1 (7c9722b)

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause:
The @modelcontextprotocol/sdk package is currently pinned at version 1.12.0 in src/package.json. This version defines LATEST_PROTOCOL_VERSION as 2025-03-26 and only supports protocol versions ["2025-03-26", "2024-11-05", "2024-10-07"]. When the SDK client connects to a server advertising protocol version 2025-11-25, the version negotiation fails with the error "Server's protocol version is not supported: 2025-11-25".

Proposed Fix:

1. Upgrade @modelcontextprotocol/sdk from 1.12.0 to 1.28.0 (latest stable) in src/package.json
2. Run pnpm install to update the lockfile

SDK version 1.28.0 sets LATEST_PROTOCOL_VERSION to 2025-11-25 and supports ["2025-11-25", "2025-06-18", "2025-03-26", "2024-11-05", "2024-10-07"], which covers the version the reporter needs.

I verified that all imports used by Roo Code (Client, StdioClientTransport, getDefaultEnvironment, SSEClientTransport, StreamableHTTPClientTransport, and the type schemas) remain available with the same module paths in v1.28.0, so no code changes to src/services/mcp/McpHub.ts should be needed beyond the version bump.

Risk Assessment:

• The SDK upgrade is a semver-minor bump (1.12.0 -> 1.28.0) within the same major version, so breaking changes are unlikely
• All currently used exports are confirmed to still exist in the new version
• The upgrade adds support for newer protocol versions while maintaining backward compatibility with older ones

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[av-gantimurov]

@roomote approve this plan. I really need this update.

[roomote-v0]

I've seen your comment and the approved plan. I'll proceed with upgrading @modelcontextprotocol/sdk to support the 2025-11-25 protocol version. I'll open a PR to share progress shortly.

[roomote-v0]

Opened a draft PR with my attempt at addressing this: #12243. Feedback welcome!