MCP 2.0 What Changes, What Breaks, and What You Need to Do About It

MCP 728: What Changes, What Breaks, and What You Need to Do About It The MCP 728 specification introduces some of the biggest changes yet to the Model Context Protocol — and teams building with MCP need to understand what’s changing and how to prepare. In this session, Mateo Torres, Developer Advocate at Arcade.dev, breaks down the new specification and what it means for developers and organizations already building or deploying MCP. The 728 spec removes the session handshake, formalizes servers as OAuth 2.1 resource servers, makes extensions first-class, and deprecates features including Sampling and Roots. These changes also kick off a 12-month migration clock, giving teams a limited window to adapt their existing implementations. Mateo explores both the tactical and strategic decisions teams will need to make — from re-architecting authentication to deciding whether to support both protocol versions or introduce a runtime layer in front of MCP. If you're building, operating, or planning to adopt MCP, this session offers a practical guide to what changes, what might break, and what you should be doing now. 🎤 Speaker: Mateo Torres — Developer Advocate, Arcade.dev 📌 Topic: MCP 728: What Changes, What Breaks, and What You Need to Do About It Want to be part of the community building the future of agentic AI? Join the Agentic AI Foundation (AAIF) and connect with the people, projects, and organizations shaping open standards for agentic AI. https://aaif.io/news/linux-foundation-announces-formation-of-aaif