Skip to content

feat(core): update protocol definitions to use MCPLatest for draft specs#281

Open
anubhav756 wants to merge 1 commit into
anubhav-sep-2243from
anubhav-mcp-latest
Open

feat(core): update protocol definitions to use MCPLatest for draft specs#281
anubhav756 wants to merge 1 commit into
anubhav-sep-2243from
anubhav-mcp-latest

Conversation

@anubhav756

@anubhav756 anubhav756 commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Description

This PR introduces user-facing protocol version aliases to simplify configuration and abstract away explicit date-based versions.

  • Protocol.MCP_LATEST maps to the stable 2025-11-25 release.
  • Protocol.MCP_DRAFT maps to the experimental 2026 Draft release.

@anubhav756
anubhav756 force-pushed the anubhav-mcp-latest branch from 4276bd6 to 13da1cb Compare July 3, 2026 22:40
Comment thread core/client.go
// Initialize the Transport based on the selected Protocol.
var transportErr error

if slices.Contains(GetSupportedMcpVersions(), string(tc.protocol)) && tc.protocol != MCPLatest {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we removing this warning SDK - wide?
If this is only because of the new draft spec being latest, should we keep MCPLatest as the latest released version?

Comment thread core/client.go
switch version {
case MCPDRAFT2026v1:
case MCPLatest:
return mcp20260618.New(tc.baseURL, tc.httpClient, tc.clientName, tc.clientVersion)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This may cause a breakage when we bump the MCPLatest variable in the future. Can we use the explicit name (MCPDRAFT2026v1) instead?

@dishaprakash dishaprakash added the priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. label Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants