asklar.dev
Model Context Protocol
MCP 2026 Roadmap — 4 Priorities
From “versioned releases” → working-group-driven priorities (the production reality).
Priority 1
Transport evolution & scalability
Make remote MCP servers boring to run at scale.
Streamable HTTP enabled remote MCP servers
Move toward stateless sessions (load-balancer-friendly)
Discover capabilities without connecting (/.well-known metadata)
Priority 2
Agent communication (Tasks)
Turn “experimental” into operational semantics.
Retry semantics for transient failure
Result expiry / retention policies
Clear lifecycle guarantees (agents can depend on it)
Priority 3
Governance maturation
Increase SEP throughput without chaos.
Working Groups own domain expertise
Delegated SEP review/approval (reduce bottleneck)
Contributor ladder (trust → scope)
Priority 4
Enterprise readiness
Controls without bloating the core protocol.
Audit trails, SSO-integrated auth, gateway behavior
Configuration portability across environments
Expect most of this as extensions (extensions-first)