Webinars / Past sessions
MCP Release 2026-07-28: What Changes, What Breaks, and What You Need to Do About It
Watch the recording
Recorded July 28, 2026 · 30 min
Register to get instant access to the recording.
You're in — the recording is unlocked.
Oops! Something went wrong. Please try again.
What you'll learn
- What's actually changing across the protocol core, authorization, extensions, and deprecations
- Why it matters, and which changes are urgent versus which you can stage
- The tactical and strategic shifts your team needs to make to stay ahead of the migration
- Demos, plus the questions attendees asked during live Q&A
About this session
The 2026-07-28 spec is the largest change to MCP since launch, and it carries breaking changes: the session handshake is removed, servers have to become formal OAuth 2.1 resource servers, extensions become first-class, and features like Sampling and Roots are now deprecated.
Some of these change session-based architectures the day the spec lands; others put you on a 12-month migration clock. They also force new strategic and tactical shifts. For example, how you re-architect authorization once bring-your-own-token stops working is a tactical call every team has to get right, and whether you run both protocol versions yourself or put a runtime in front is the strategic one that shapes the rest.
Hosted by
Mateo Torres
Developer Relations
Mateo is an expert at bridging cutting-edge AI research with practical developer tools. With a background in computational biology and experience in both research and engineering, he now focuses on making LLMs more useful by connecting them to systems developers already use. At Arcade, Mateo creates tutorials, SDKs, and open-source examples that help developers move beyond chatbots and into fully agentic applications.
