Try for free
MLOps.community
MLOps.community

What an Anthropic Engineer Thinks About MCP

27 July 2026 52:27 Demetrios

Listen to episode

About this episode

In this episode, we're joined by David Soria Parra, Engineering Lead at Anthropic and one of the core maintainers of the Model Context Protocol (MCP), to 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 AI podcast episodes

Browse all →

Want to find AI jobs?

Join thousands of AI professionals finding their next opportunity

We respect your inbox. Unsubscribe at any time.

© 2026 MLOps.community. All rights reserved.

Common Questions

Frequently asked questions

Quick answers about how DevFound's AI matching, resumes, and referrals work.

DevFound's AI Copilot ingests your profile, goals, and live job data to deliver curated matches in seconds. Every match includes a resume variant, suggested referrals, and interview prep so you can act immediately. The more feedback you provide, the sharper the Copilot becomes.

AI-led job searches shrink the hours spent sifting through boards and formatting resumes. DevFound pairs automation with your personal outreach, so you reserve energy for interviews and negotiation. Traditional networking still matters, but AI gives you a lift before you even send a message.

Modern AI roles expect comfort with production-grade code, data fluency, and practical ML tooling. The strongest candidates pair deep technical chops with storytelling—translating model impact to product, GTM, and exec partners. Continuous learning keeps you ahead as stacks evolve.

DevFound rewards active seekers. Keep your profile fresh, respond to match quality prompts, and enable alerts so you never miss a role. The AI prioritizes companies and teams that align with your feedback, accelerating both introductions and interview invites.

High-density tech hubs continue to host the deepest AI talent pools, yet distributed teams are catching up fast. Use DevFound filters to hone in on onsite, hybrid, or fully remote roles and watch openings expand across time zones.

DevFound aggregates thousands of remote AI openings and flags the nuances—core hours, async culture, and visa needs—up front. The Copilot also recommends how to position your distributed work experience so hiring managers know you can thrive on a remote team.

Still have questions?

Contact Support