Skip to content

deps: adopt MCP 2026-07-28 spec by bumping mark3labs/mcp-go #275

Description

@peteski22

Summary

The 2026-07-28 MCP specification is out (announcement). mcpd should adopt it by bumping mark3labs/mcp-go once that library ships 2026-07-28 support, rather than porting protocol handling by hand.

Current state

  • go.mod pins github.com/mark3labs/mcp-go v0.55.1, whose LATEST_PROTOCOL_VERSION is 2025-11-25.
  • mcpd negotiates the protocol version through the library: internal/daemon/daemon.go:375 passes mcp.LATEST_PROTOCOL_VERSION into Initialize. A dependency bump therefore carries the new version through automatically — no call-site changes required for the version itself.
  • mcpd talks to servers over STDIO only and exposes its own REST API upstream, so the spec's HTTP-transport changes (stateless core, header routing, SSE deprecation) do not require code changes here.

Notes

  • No urgency: version negotiation is backward-compatible, so a 2026-07-28 server negotiates down to 2025-11-25 against the current build. Nothing is broken today.
  • mcpd uses the community mark3labs/mcp-go, not the official modelcontextprotocol/go-sdk. The 2026-07-28 SDK announcement refers to the official SDK; this issue tracks mark3labs/mcp-go specifically. If that library does not add 2026-07-28 support, evaluating a move to the official SDK is a separate, larger decision and out of scope here.

Done when

  • mark3labs/mcp-go is bumped to a release that supports the 2026-07-28 protocol version.
  • make test and make lint pass against the bumped dependency.
  • NOTICE regenerated if the dependency set changed.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions