Dec 28, 2025 · 1h 39m · latent-space
One Year of MCP — with David Soria Parria and AAIF leads from OpenAI, Goose, Linux Foundation
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this special Latent Space episode, co-hosts Alessio Fanelli and Swyx celebrate the one-year anniversary of the Model Context Protocol (MCP) with co-creator David Soria Parra and host a historic panel featuring leadership from OpenAI, Block, and the Linux Foundation to announce the launch, architecture, and governance of the Agentic AI Foundation (AAIF).
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. The hosts hold 16.3% of the talking time here. How this is scored →
speaking balance: gold is the hosts, purple is the guest (3 minute bins)
David pushes back forcefully on the community misconception that code execution modes render MCP obsolete, clarifying that MCP remains the foundational communication and authentication layer.
Hardest push from the hosts ▶ 55:40 Swyx challenges iframe architecture for MCP appsSwyx directly challenges David on the viability of iframes for rich UI components, highlighting severe CORS headaches and UI styling inconsistencies.
Biggest teaching moment ▶ 8:59 OAuth architecture and IDP decoupling in enterpriseDavid provides a masterclass on enterprise authentication, walking through why combining the auth server and resource server broke enterprise SSO integration and required complete architectural separation.
The host holds their own ▶ 26:55 Swyx surfaces Anthropic's internal MCP gatewaySwyx demonstrates deep domain knowledge by citing internal engineering talks to drill into Anthropic's actual internal platform infrastructure and dogfooding practices.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The hosts as informed peer | Guest teaching | Guest disagreement | The hosts pushing back | Why |
|---|---|---|---|---|---|---|
| Reflecting on One Year of the Model Context Protocol | 5 | 4 | 1 | 1 | Swyx and Alessio establish a collegial atmosphere, accurately framing the one-year milestone and public announcements. David gives a structured historical recap of the protocol's evolution from local to remote and enterprise auth. | |
| The Creation and Governance of the Agentic AI Foundation | 6 | 4 | 1 | 2 | Alessio and Swyx ask pointed questions about how other protocols and the foundation governance fit together, referencing Swyx's early analysis on MCP. David clarifies the narrow initial scope for protocol acceptance and core maintainer roles. | |
| Iterating on Remote Transports and Enterprise OAuth Specifications | 5 | 8 | 2 | 2 | David openly schools the hosts on OAuth architecture, breaking down why their initial spec failed by combining the auth server and resource server instead of integrating with enterprise IDPs. Swyx asks clarifying questions to understand the failure mode. | |
| Transport Protocols, Bidirectional Streaming, and Horizontal Scalability | 6 | 7 | 2 | 1 | Alessio asks about transport protocol design choices and regrets. David provides a deep technical breakdown of why streamable HTTP was chosen, why making bidirectional return streams optional backfired, and the distributed state challenges of horizontal scaling. | |
| Open Source Standards: IETF Comparison and Core Maintainer Governance | 6 | 5 | 2 | 2 | Swyx draws a comparison between the MCP governance model and the IETF standards process. David explains why IETF consensus moves too slowly for AI velocity and defends MCP's small core maintainer benevolent dictatorship. | |
| Model Alignment, Progressive Discovery, and Programmatic MCP vs Code Mode | 7 | 6 | 4 | 3 | Alessio and Swyx bring up context bloat and probe the tension between Anthropic's programmatic MCP and Code Mode. David firmly clarifies that programmatic MCP is an execution optimization rather than a replacement for protocol connectivity. | |
| MCP vs Skills: Vertical Domain Knowledge Meets Horizontal Connectivity | 6 | 6 | 2 | 2 | Swyx prompts a comparison between MCP and skills. David delineates them clearly, framing skills as vertical domain knowledge needing execution environments while MCP serves as the horizontal communication and auth layer. | |
| Anthropic's Internal Dogfooding and Enterprise Gateway Infrastructure | 7 | 4 | 1 | 1 | Swyx demonstrates deep familiarity with Anthropic's internal setup from prior talks, highlighting internal MCP gateways. David confirms and details how internal employees deploy containerized MCP servers autonomously. | |
| Standardizing MCP Registries, Discovery, and Supply Chain Security | 6 | 6 | 2 | 2 | Alessio queries how public and pass-through registries fit together. David explains the NPM-like trust model, the risk of supply chain attacks, and the architectural necessity of curated private sub-registries. | |
| Lessons from Developer Summits and Financial Services Industry Constraints | 5 | 7 | 1 | 1 | Swyx asks for field lessons from international developer events. David explains unique legal constraints in financial services, like mandatory third-party attribution contracts spearheaded by Bloomberg. | |
| The State and Evolution of the MCP Sampling Protocol | 7 | 6 | 2 | 2 | Swyx and Alessio press on why sampling adoption is lagging and how long-running tasks operate. David explains why clients avoided sampling and details the polling-and-webhook design of the new tasks primitive. | |
| Context Window Compaction, Retention Strategies, and Agent Memory | 6 | 6 | 3 | 2 | Swyx asks about context compaction and Alessio asks why developers should use MCP over standard REST APIs. David explains REST OpenAPI specification bloat and ambiguous tool descriptions. | |
| MCP Apps and UI: Bringing Rich Visual Experiences into Chat Interfaces | 8 | 5 | 2 | 6 | Swyx aggressively pushes back against using standard raw iframes for MCP apps due to CORS issues, styling fragmentation, and brand consistency concerns, prompting David to acknowledge styling remains an open problem. | |
| Protocol Extensions, Healthcare Compliance, and Call for Community Builders | 5 | 6 | 1 | 1 | Swyx asks about additional protocol extensions. David provides an example of session-level isolation for HIPAA compliance to prevent data leakage across servers. | |
| Neutrality and Industry Protection: Why Anthropic Donated MCP to the Linux Foundation | 6 | 5 | 2 | 2 | Swyx directly raises community skepticism about Anthropic taking its eye off the ball by donating MCP. David firmly refutes this, citing proprietary standard lock-in risks like HDMI on Linux. | |
| Introducing the Agentic AI Foundation Leadership Panel | 5 | 4 | 1 | 1 | The panel is introduced with Jim Zemlin, Nick Cooper, and Brad. Alessio asks about the origins of the multi-company coalition, and David and Nick detail the organic collaboration. | |
| The Linux Foundation Perspective: AI Dog Years and Unprecedented Demand | 5 | 6 | 1 | 1 | Jim Zemlin explains the Linux Foundation's criteria for launching new efforts, emphasizing the unprecedented inbound interest and describing how AI moves in 'dog years.' | |
| Goose as the Reference Agent Client for Open Protocol Development | 6 | 5 | 1 | 1 | Brad and Nick describe Goose's role as an early reference implementation client to validate protocol specs like MCP UI before standardization. | |
| Balancing Open Standards with Healthy Implementation Competition | 6 | 5 | 1 | 2 | Swyx asks whether OpenAI's open-source agent tooling might be donated. Nick explains the delicate balance between open standard commonality and competitive diversity in implementation. | |
| Incentives for Contributing Open Source Projects to the Foundation | 6 | 5 | 1 | 1 | Alessio asks why an independent project with strong traction should donate to the foundation. Jim, Nick, and Brad explain the positive feedback loop of pooled engineering resources and shared learning. | |
| Why Agents Warrant a Dedicated Foundation Distinct from LF Data & AI | 7 | 5 | 1 | 2 | Swyx queries why a distinct foundation was formed instead of folding agents into LF Data & AI. Jim explains the unique audience separation between model training infra, inferencing, and agent application layers. | |
| Inside the Directed Fund: Operations, IP Protection, and Community Infrastructure | 6 | 6 | 1 | 2 | Alessio and Swyx ask where directed funds actually go in practice. Jim details IP protection, community convening logistics, metrics platforms, and separating technical governance from financial contributions. | |
| Drawing Lessons from Kubernetes and the Cloud Native Computing Foundation | 6 | 6 | 1 | 2 | Alessio compares the current landscape to the CNCF era. Jim recounts the historical precedent of Google donating Kubernetes in 2014 when Mesos and PaaS were competing standards. | |
| 2025 Vision for the Agentic AI Foundation and Concluding Thoughts | 5 | 4 | 1 | 1 | The panel shares concluding thoughts and 2025 aspirations, highlighting asynchronous agent workflows and enterprise adoption milestones. |