|
| 1 | +# RMCP Roadmap |
| 2 | + |
| 3 | +This roadmap tracks the path to SEP-1730 Tier 1 for the Rust MCP SDK. |
| 4 | + |
| 5 | +Server conformance: 86.7% (26/30) · Client conformance: 85.0% (18/24) · Spec tracking gap: 6 days |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +## Tier 2 → Tier 1 |
| 10 | + |
| 11 | +### Conformance |
| 12 | + |
| 13 | +#### Server (86.7% → 100%) |
| 14 | + |
| 15 | +- [ ] Fix `server-prompts-get-with-args` — prompt argument handling returns incorrect result |
| 16 | +- [ ] Fix `server-prompts-get-embedded-resource` — embedded resource content in prompt responses |
| 17 | +- [ ] Fix `server-elicitation-sep1330-enums` — enum inference handling per SEP-1330 |
| 18 | +- [ ] Fix `server-dns-rebinding-protection` — validate `Host` / `Origin` headers on Streamable HTTP transport |
| 19 | + |
| 20 | +#### Client (85.0% → 100%) |
| 21 | + |
| 22 | +- [ ] Fix `auth/scope-step-up` (2025-11-25) — handle 403 `insufficient_scope` and re-authorize with upgraded scopes |
| 23 | +- [ ] Fix `auth/metadata-var3` (2025-11-25) — AS metadata discovery variant 3 |
| 24 | +- [ ] Fix `auth/2025-03-26-oauth-endpoint-fallback` (2025-03-26) — legacy OAuth endpoint fallback for pre-2025-06-18 servers |
| 25 | + |
| 26 | +### Governance & Policy |
| 27 | + |
| 28 | +- [ ] Create `VERSIONING.md` — document semver scheme, what constitutes a breaking change, and how breaking changes are communicated |
| 29 | + |
| 30 | +### Documentation (26/48 → 48/48 features with prose + examples) |
| 31 | + |
| 32 | +#### Undocumented features (14) |
| 33 | + |
| 34 | +- [ ] Tools — image results |
| 35 | +- [ ] Tools — audio results |
| 36 | +- [ ] Tools — embedded resources |
| 37 | +- [ ] Prompts — embedded resources |
| 38 | +- [ ] Prompts — image content |
| 39 | +- [ ] Elicitation — URL mode |
| 40 | +- [ ] Elicitation — default values |
| 41 | +- [ ] Elicitation — complete notification |
| 42 | +- [ ] Ping |
| 43 | +- [ ] SSE transport — legacy (client) |
| 44 | +- [ ] SSE transport — legacy (server) |
| 45 | +- [ ] Pagination |
| 46 | +- [ ] Protocol version negotiation |
| 47 | +- [ ] JSON Schema 2020-12 support *(upgrade from partial)* |
| 48 | + |
| 49 | +#### Partially documented features (7) |
| 50 | + |
| 51 | +- [ ] Tools — error handling *(add dedicated prose + example)* |
| 52 | +- [ ] Resources — reading binary *(add dedicated example)* |
| 53 | +- [ ] Elicitation — form mode *(add prose docs, not just example README)* |
| 54 | +- [ ] Elicitation — schema validation *(add prose docs)* |
| 55 | +- [ ] Elicitation — enum values *(add prose docs)* |
| 56 | +- [ ] Capability negotiation *(add dedicated prose explaining the builder API)* |
| 57 | +- [ ] Protocol version negotiation *(document version negotiation behavior)* |
| 58 | + |
| 59 | +--- |
| 60 | + |
| 61 | +## Informational (not scored) |
| 62 | + |
| 63 | +These draft/extension scenarios are tracked but do not block tier advancement: |
| 64 | + |
| 65 | +- [ ] `auth/resource-mismatch` (draft) |
| 66 | +- [ ] `auth/cross-app-access-complete-flow` (extension) |
| 67 | +- [ ] `auth/client-credentials-jwt` (extension) |
0 commit comments