Umbrella for the 2026-07-28 release work. Bar: the conformance suite passes with no expected-failures waivers attributable to this release (the SEP-990 enterprise-auth waiver is unrelated and remains). Each sub-issue lists the scenarios it's responsible for; design is owned by whoever takes the issue.
This sits alongside the broader v2.0 SDK rework tracked in #1253 — that umbrella covers SDK-ergonomics breaking changes; this one covers spec compliance for the 2026-07-28 protocol revision.
What's in it
- Sub-issues:
- Architecture (direction, not law): lowlevel
Server = protocol interface, minimal state, no magic. The 2026 features ship as public helpers/classes usable directly against lowlevel Server. MCPServer is a thin composition of those same public helpers — a pre-built convenience, not a monolith with private machinery.
- Capability checkpoints (shared targets, not tickets):
- M1 — a modern client makes a stateless
tools/call against a modern server over HTTP, no initialize (minimum slice of Backwards compatibility & version negotiation + New HTTP serving path (modern + dual-era) + New Client (all-versions, low-level + high-level))
- M2 — the
server-stateless conformance scenario passes end-to-end (Backwards compatibility & version negotiation + New HTTP serving path (modern + dual-era) + Context object (layered, per-request) + Capabilities API + server/discover handler + subscriptions/listen all in)
- M3 — all release-attributable waivers gone
- Landing model: PRs land to
main. 2026-07-28 stays modeled-but-not-negotiable until the version-negotiation work flips it on, so partial work doesn't change behaviour for existing users.
- Standing maintenance (not a sub-issue): when bumping the conformance pin, reconcile
expected-failures.yml in the same PR; when in-flight spec PRs merge, re-vendor schema/2026-07-28.json + regenerate.
- Stretch (optional): contribute missing scenarios upstream — discover caching-hints check, dedicated
subscriptions/listen server scenario, client-direction sessionless scenario.
Conformance
- (all release-attributable waivers removed across the sub-issues)
Dependencies
References
Umbrella for the 2026-07-28 release work. Bar: the conformance suite passes with no expected-failures waivers attributable to this release (the SEP-990 enterprise-auth waiver is unrelated and remains). Each sub-issue lists the scenarios it's responsible for; design is owned by whoever takes the issue.
This sits alongside the broader v2.0 SDK rework tracked in #1253 — that umbrella covers SDK-ergonomics breaking changes; this one covers spec compliance for the 2026-07-28 protocol revision.
What's in it
Server= protocol interface, minimal state, no magic. The 2026 features ship as public helpers/classes usable directly against lowlevelServer.MCPServeris a thin composition of those same public helpers — a pre-built convenience, not a monolith with private machinery.tools/callagainst a modern server over HTTP, no initialize (minimum slice of Backwards compatibility & version negotiation + New HTTP serving path (modern + dual-era) + New Client (all-versions, low-level + high-level))server-statelessconformance scenario passes end-to-end (Backwards compatibility & version negotiation + New HTTP serving path (modern + dual-era) + Context object (layered, per-request) + Capabilities API + server/discover handler + subscriptions/listen all in)main. 2026-07-28 stays modeled-but-not-negotiable until the version-negotiation work flips it on, so partial work doesn't change behaviour for existing users.expected-failures.ymlin the same PR; when in-flight spec PRs merge, re-vendorschema/2026-07-28.json+ regenerate.subscriptions/listenserver scenario, client-direction sessionless scenario.Conformance
Dependencies
References