docs(spec): MCP 2026-07-28 protocol upgrade (spec 058, blocked on mcp-go)#533
docs(spec): MCP 2026-07-28 protocol upgrade (spec 058, blocked on mcp-go)#533Dumbris wants to merge 2 commits into
Conversation
Related #532 Captures the full scope of upgrading mcpproxy to the MCP 2026-07-28 spec revision. Status is BLOCKED on mcp-go shipping 2026-07-28 support (currently v0.54.x targets 2025-11-25 only). ## Changes - specs/057-mcp-2026-upgrade/spec.md: 5 prioritized user stories, 27 FRs, 8 success criteria covering stateless sessions, server/discover + per-request _meta, required routing headers, MRTR, subscriptions/listen, error-code changes, and additive features (CacheableResult, deterministic ordering, JSON Schema 2020-12, trace context) - specs/057-mcp-2026-upgrade/checklists/requirements.md: spec quality checklist
Deploying mcpproxy-docs with
|
| Latest commit: |
8837828
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d3b39f94.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://058-mcp-2026-upgrade.mcpproxy-docs.pages.dev |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 26558739048 --repo smart-mcp-proxy/mcpproxy-go
|
Resolves spec-number collision with PR #531 (in-proxy profiles), which keeps 057.
|
Critic (Codex) review — Dumbris's PR #533
|
|
Critic (Codex) review — Dumbris's PR #533 Strengths: Spec-only scope is clear, the dependency gate is explicit, the spec calls out backward compatibility and proxy-specific header/stateless risks, and current mcp-go release data still supports the blocked-on-library premise ( Findings: none Provenance check: ok |
Summary
Adds spec 057 capturing the scope of upgrading mcpproxy to the MCP 2026-07-28 protocol revision. This is a spec-only PR — no code changes. Implementation is BLOCKED until
mcp-goships2026-07-28support (currently v0.54.x →2025-11-25).Tracking issue: #532
What's in the spec
server/discover+ per-request_meta, requiredMcp-Method/Mcp-Name/MCP-Protocol-Versionheaders, MRTR,subscriptions/listen,-32002→-32602CacheableResult, deterministic ordering, JSON Schema 2020-12, trace context in activity logWhy merge a blocked spec
Locks the analysis while it's fresh and gives a stable reference for the tracking issue and the scheduled mcp-go watcher. Plan/tasks come later, once unblocked and re-validated against the finalized (non-RC) spec.
Test plan
/speckit.plan