c934b04f48
## Motivation and Context The Deprecated Features paragraph still described the pre-#516 design, claiming the SDK "emits deprecation warnings when they are used with protocol version 2026-07-28 or newer". Since #516 the only deprecation warning is the client-side one, emitted on a modern connect that declares the Roots or Sampling capabilities, exactly as the 1.2.0 CHANGELOG entry states. Logging never warns (`notify_log_message` is the sanctioned SEP-2575 delivery path on that wire), and the server never warns either: `initialize` counter-offers a legacy version, a modern `Configuration` pin is rejected at construction, and the modern lifecycle refuses the deprecated server-to-client request APIs outright rather than serving them with a warning. The paragraph now describes the shipped behavior and says where each feature lives per lifecycle: unchanged on legacy, carried on 2026-07-28 by input requests embedded in `InputRequiredResult` responses (the SEP-2322 multi round-trip requests pattern) and the envelope's `logLevel`. Those carriers are not the SEP-2577 replacements: the spec's deprecated-features registry points migrating implementations outside the protocol (tool parameters or configuration, direct LLM provider APIs, stderr or OpenTelemetry), and the paragraph now says so instead of presenting the modern delivery forms as the replacements. ## How Has This Been Tested? Documentation-only change; proofread against the `ProtocolDeprecations` module header and the CHANGELOG entry that shipped this behavior in 1.2.0, which the 1.3.0 release leaves unchanged.
51 lines
2.9 KiB
Markdown
51 lines
2.9 KiB
Markdown
# Roadmap
|
|
|
|
This roadmap outlines the MCP Ruby SDK's path toward SEP-1730 Tier 1.
|
|
It is a living document and will evolve as the SDK matures.
|
|
|
|
## Current Status
|
|
|
|
The SDK implements the 2025-06-18, 2025-11-25, and 2026-07-28 spec revisions, and passes all scored server
|
|
and client conformance scenarios for each revision's requirement set.
|
|
Optional protocol extensions (such as DPoP, workload identity federation, and the tasks extension)
|
|
are not yet implemented; SEP-1730 does not require extensions for any tier.
|
|
|
|
## API Stability
|
|
|
|
The 1.0.0 release marked the public API as stable: breaking changes ship only in major releases,
|
|
apart from the narrow exceptions documented in [VERSIONING.md](VERSIONING.md),
|
|
which also defines the Semantic Versioning scheme and breaking-change policy.
|
|
|
|
## Deprecated Features
|
|
|
|
The 2026-07-28 spec revision deprecates Roots, Sampling, and Logging (SEP-2577).
|
|
These features remain supported throughout 1.x: on the legacy lifecycle they work unchanged
|
|
(the deprecations do not apply there), and the 2026-07-28 lifecycle carries them through its own mechanisms:
|
|
roots-shaped and sampling-shaped input requests embedded in `InputRequiredResult` responses
|
|
(the SEP-2322 multi round-trip requests pattern) and per-request log delivery through the envelope's `logLevel`.
|
|
The replacements SEP-2577 names live outside the protocol: tool parameters or configuration for roots,
|
|
direct LLM provider APIs for sampling, and stderr or OpenTelemetry for logging.
|
|
The client emits a deprecation warning when a modern connect declares the deprecated Roots or Sampling capabilities.
|
|
Under Semantic Versioning their removal requires a major release, but no removal is scheduled yet: whether 2.0.0 removes
|
|
them depends on how future MCP spec revisions treat these features and on adoption of their replacements.
|
|
|
|
## Conformance
|
|
|
|
The SDK maintains a 100% conformance pass rate as new scenarios are added to the conformance suite.
|
|
Legacy SSE transport (2024-11-05) is intentionally out of scope; the SDK provides modern Streamable HTTP only.
|
|
|
|
## Documentation
|
|
|
|
Reference documentation covers all non-experimental features with examples.
|
|
|
|
## Tracking New Spec Revisions
|
|
|
|
The SDK aims to support each new MCP specification revision, with the implementation timeline agreed per
|
|
release based on feature complexity.
|
|
The 2026-07-28 revision shipped during 1.x: the server serves both lifecycle eras side by side,
|
|
so the SEP-2575 stateless lifecycle (including `server/discover` and `subscriptions/listen`),
|
|
SEP-2322 multi round-trip requests, SEP-2549 cache hints, and SEP-2243 custom headers are available alongside
|
|
the legacy handshake. The few incompatible adjustments the revision required shipped in
|
|
a minor release under the spec-conformance and security exceptions described in [VERSIONING.md](VERSIONING.md).
|
|
Removing legacy-era support is reserved for a future major release.
|
|
The tasks extension (SEP-2663) remains planned ([#391](https://github.com/modelcontextprotocol/ruby-sdk/issues/391)).
|