Show Notes
David Soria Parra is an Engineering Lead at Anthropic and one of the core maintainers of the Model Context Protocol (MCP). We explore the biggest evolution of the protocol since its launch, and why MCP is becoming the foundation for the next generation of AI agents.
We discuss why MCP is moving toward stateless communication, what developers misunderstand about state, sessions, and transport layers, and how lessons from real-world deployments at massive scale have shaped the protocol's future. We also dive into MCP v2, SDK migrations, protocol design, extension architecture, governance, developer experience, and how Anthropic thinks about balancing simplicity with long-term flexibility.
Along the way, we explore progressive disclosure, tool search, programmatic tool calling, context bloat, forward compatibility, long-running AI tasks, protocol evolution, open-source governance, observability, and why the future of AI infrastructure will depend on designing protocols that can evolve without breaking the ecosystem.
Timestamps: [00:00] Introduction [01:59] Why MCP Had to Become Stateless [04:28] The Tradeoffs of Stateless Design [06:13] What We Learned About Agent State [08:04] Sessions, Models & Implicit State [09:33] Migrating to MCP v2 [12:19] Lessons from HTTP & Open Source Standards [18:16] Shipping Fast Without Breaking Everything [20:35] The Future Complexity of MCP [22:44] Core Features vs Extensions [26:47] Progressive Disclosure Explained [28:16] Solving Context Bloat [30:50] Why Tool Search Beats Progressive Disclosure [32:10] The Biggest MCP Anti-Pattern [34:25] Designing for Forward Compatibility [38:41] Why "Tasks" Matter [40:53] JSON, Tokens & Better Tool Calling [44:44] Observability & Tracing AI Agents [47:34] Will MCP Ever Be Finished? [50:22] What's Next for MCP
More from Agentic Conversations (formally mlops.community)
AI can write your code, choose its own tools, and book your next trip. But who checks that it actually did the job?
What happens when you give 200 engineers who have barely touched AI a coding assistant and a six-month deadline to rebuild their platform? Pepijn Senders, a principal engineer who previously led AI enablement at HelloFresh, has done exactly that, and he chose Sonnet over Opus on purpose.
An AI slips out of its sandbox. A chatbot won’t explain your cat’s stripes. And your next shopping spree might not involve you clicking anything.
What happens to the web when the ones browsing it are no longer people? Sarah Drasner, Area Tech Lead at Google, sits down with us ahead of her Agentic Web keynote at AGNTCon + MCPCon North America. She works through that question from both directions: rebuild the web so agents can use it properly, or build agents smart enough to handle the web as it already exists.
Everyone is racing to build one agent that can do everything. Justin Schroeder, co-founder of Standard Agents, thinks the future looks more like thousands of tiny ones. Ahead of his talk on domain-specific agents at AGNTCon + MCPCon North America, he explains why tightly scoped agents might be the smarter bet, even if it feels like a step back toward the single-purpose machine learning models of a few years ago.