build(deps): bump github.com/modelcontextprotocol/go-sdk from 1.6.1 to 1.7.0

[dependabot]

Bumps github.com/modelcontextprotocol/go-sdk from 1.6.1 to 1.7.0.

Release notes

Sourced from github.com/modelcontextprotocol/go-sdk's releases.

v1.7.0

This release brings full support for protocol version 2026-07-28. The wire protocol is largely rewritten: a stateless model with per-request _meta, a new server/discover RPC replacing the initialize handshake, multi-round-trip requests (MRTR) replacing server-initiated calls, a unified subscriptions/listen stream replacing free-floating change notifications, standardised HTTP headers, and the formal deprecation of the roots, sampling, and logging features.

The streamable HTTP transport accepts requests at protocol version 2026-07-28 only when StreamableHTTPOptions.Stateless = true. If you want to expose the new protocol over HTTP, set Stateless = true; if you want to keep stateful sessions, your clients will negotiate down to 2025-11-25.

Backward compatibility with 2025-11-25 and earlier is preserved on every endpoint. The SDK negotiates the highest mutually-supported version at connect time. The new protocol is enabled by default for new clients; existing legacy clients and servers continue to work unchanged.

This release consolidates everything shipped in v1.7.0-pre.1, v1.7.0-pre.2, and v1.7.0-pre.3. Thank you to everyone who exercised the pre-releases and filed feedback.

v1.7.0-pre.3 is already successfully used by GitHub, serving more than half a million users.

Make MCP Stateless (SEP-2575) & Sessionless (SEP-2567)

The initialize/notifications/initialized handshake is removed in 2026-07-28. Each request now carries _meta.io.modelcontextprotocol/{protocolVersion,clientInfo,clientCapabilities} so the server can validate the peer without state. A new server/discover RPC lets clients learn the server's supported versions and capabilities up front; the SDK falls back to legacy initialize if discover fails. Resumability (Last-Event-ID, standalone GET) is removed; ping, logging/setLevel, resources/subscribe, and resources/unsubscribe are also removed on this revision and rejected with MethodNotFound.

• mcp: Implement support for SEP-2575 on client side by @​guglielmo-san (#975)
• mcp: Implement server-side support for discover method (SEP-2575) by @​guglielmo-san (#987)
• mcp: Implement stateless server (SEP-2575) by @​guglielmo-san (#965)
• mcp: add support for logging level (SEP-2575) by @​guglielmo-san (#997)
• mcp: Remove resumability and introduce MissingRequiredClientCapability error data by @​guglielmo-san (#1005)
• mcp: remove session header handling in stateless mode by @​maciej-kisiel (#952)
• mcp: do not call DELETE for sessionless & doc adjustments by @​maciej-kisiel (#960)
• mcp: Implement retry on advised supportedVersions in UnsupportedProtocolVersion error by @​guglielmo-san (#989)
• mcp: Enable legacy initialize fallback on any error by @​guglielmo-san (#1014)

Subscriptions listen (SEP-2575)

The legacy tools/list_changed, prompts/list_changed, resources/list_changed, and resources/updated notifications are replaced by a single long-lived subscriptions/listen request whose response stream multiplexes every change notification the client opted into, each tagged with io.modelcontextprotocol/subscriptionId. The SDK opens this stream automatically on Client.Connect when the corresponding list-changed handler is set; servers route notifications only to subscribed sessions.

• mcp: Implement subscriptions/listen rpc (SEP-2575) by @​guglielmo-san (#1007)
• mcp: refactor notification of subscribed sessions by @​guglielmo-san (#1018)

Multi Round-Trip Requests (SEP-2322)

Server-to-client requests for elicitation, sampling, and roots are no longer issued as fresh JSON-RPC requests. Instead a tool/prompt/resource handler returns an InputRequiredResult whose inputRequests field carries the requests; the client fulfils each and retries the original call with inputResponses populated. The SDK ships client- and server-side middleware that handles this transparently in both directions, including a server-side compatibility shim that lets MRTR handlers also work against legacy clients.

• feat: multi-round-trip request implementation (SEP-2322) by @​yarolegovich (#950)

Cacheable list results (SEP-2549)

tools/list, prompts/list, resources/list, resources/templates/list, resources/read, and server/discover results now carry ttlMs and cacheScope fields. Clients honour them as freshness hints to reduce polling; shared intermediaries use cacheScope to decide whether responses may be cached.

• mcp: add ttl for list results (SEP-2549) by @​guglielmo-san (#1008)
• mcp: add Cacheable fields to DiscoverResult by @​guglielmo-san (#1022)

HTTP standardization (SEP-2243)

The streamable HTTP transport now mirrors selected fields from the JSON-RPC body into HTTP headers (Mcp-Method, Mcp-Name, Mcp-Protocol-Version, Mcp-Param-*) so network intermediaries can route and observe MCP traffic without deep packet inspection. Tools can declare per-parameter passthrough via x-mcp-header annotations on their input schema. Body↔header mismatches return -32020 HeaderMismatch.

... (truncated)

Commits

• bc72835 mcp: fix potential nil-pointer dereference on message send (#1115)
• cc4db25 chore: update conformance (#1114)
• e761950 mcp: avoid double-copy of payload in writeEvent (#1106)
• 2781b8f mcp: derive Mcp-Protocol-Version header from the outgoing message (#1107)
• 827f90b mcp: allow opt-in to cancel handler ctx on aborted POST (#1099)
• 5cb8339 mcp: update return meta in DiscoverResult (SEP-2575) (#1097)
• fa548d7 docs: update docs (#1089)
• 8baa4cc mcp: add return type to subscriptions/listen (#1088)
• 9576afc mcp: wrap unmarshalParams with jsonrpc error (#1087)
• 0a8953d ci: fix nightly runs (#1086)
• Additional commits viewable in compare view

[dependabot]

Labels

The following labels could not be found: dependencies, go. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[JakobAIOdev]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Resolved. The branch now merges cleanly, and the conflict resolution is in commit 77038c6.