StarZero All shows Try the podcast clipper →

Apr 3, 2025 · 1h 20m · latent-space

The Creators of Model Context Protocol

Alessio Fanelli · 5m spoken
0:00 / 0:00
▶ Watch on YouTube →

gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions

In this episode of the Latent Space podcast, Anthropic engineers Justin and David discuss the origins, core architecture, and open-source ecosystem of the Model Context Protocol (MCP), explaining how it provides a universal connection layer between AI applications, tools, and data sources.

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 7.2% of the talking time here. How this is scored →

The hosts as informed peer 5.8 Guest teaching 4.5 Guest disagreement 1.4 The hosts pushing back 2.6
05100:0020:0040:001:00:001:20:001:58–8:01 · The hosts as informed peer 3/10 The Inception and Origin Story of MCP at Anthropic The hosts set up the episode warmly and ask for the inception story. David and Justin recount early brainstorming at Anthropic, local IDE frustrations, and prototyping MCP in Zed.8:01–12:26 · The hosts as informed peer 5/10 Architectural Inspiration from Language Server Protocol and Core Design Principles Swix identifies the classic M x N infrastructure integration problem and draws parallels to LSP. Justin and David explain adopting JSON-RPC to keep underlying transport boring while focusing innovation on primitives.12:26–19:25 · The hosts as informed peer 6/10 Deconstructing MCP Primitives: Tools, Resources, and Prompts Swix shares diagrams and prompts the guests on why MCP split primitives into tools, resources, and prompts. The guests explain how presentation and user-versus-model initiation guided these abstractions.19:25–29:24 · The hosts as informed peer 7/10 Information Architecture: Differentiating Tools from Resources and Raw Data Handling Alessio presses on common SDK design pitfalls where server builders over-filter API responses, citing the Google Maps reference server. Justin admits Claude wrote much of it, and David argues developers must unlearn decades of rigid API schema formatting when building for LLMs.29:24–32:43 · The hosts as informed peer 4/10 Evaluating Protocol Differences: Model Context Protocol versus OpenAPI Swix asks for a definitive breakdown between MCP and OpenAPI. Justin and David articulate that OpenAPI is too granular and stateless, whereas MCP provides stateful higher-level agentic primitives.32:43–40:10 · The hosts as informed peer 6/10 Practical Server Development Strategies and AI-Assisted Implementation Alessio references hackathons where builders use agents to autogenerate MCP servers from API specs. Guests explain how LLMs can easily one-shot server development directly from SDK context.40:10–45:33 · The hosts as informed peer 6/10 Composability, Bi-Directional Model Sampling, and the Agent Spectrum Alessio asks how MCP servers can be composed into DAGs, and Swix pushes on whether a recursive client-server MCP construct constitutes an agent. David and Justin differentiate simple proxies from agentic sampling loops.45:33–54:43 · The hosts as informed peer 7/10 Context Limits, Tool Routing, and Registry Ecosystem Security Swix examines tool context ceilings (250 tools) and challenges registry security models, arguing that package trust metrics can be easily compromised. Guests emphasize that client applications must retain ultimate control over tool filtering.54:43–1:01:20 · The hosts as informed peer 6/10 Technical Deep Dive into Reference Servers: Memory, Filesystem, and Sequential Thinking Swix reviews reference servers such as memory and filesystem, asking about the relationship between sequential thinking MCP and Anthropic's new Think tool blog post. Justin explains these servers often bridge capabilities ahead of native model adoption.1:01:20–1:09:59 · The hosts as informed peer 7/10 Roadmap Architecture: Streamable HTTP Transport, Authentication, and Scopes The discussion turns to the transition from persistent SSE to streamable HTTP transport. Alessio asks about dynamic granular scoping for enterprise data, and Justin outlines the protocol conservatism necessary to preserve backwards compatibility.1:09:59–1:18:05 · The hosts as informed peer 7/10 Open-Source Governance, Community Stewardship, and Multi-Company Maintenance David emphasizes that drive-by commenters without code contributions will be disregarded. Swix challenges the centralization of governance by citing GraphQL's foundation donation, while David and Justin defend nimble multi-company maintenance to avoid death by committee.1:58–8:01 · Guest teaching 2/10 The Inception and Origin Story of MCP at Anthropic The hosts set up the episode warmly and ask for the inception story. David and Justin recount early brainstorming at Anthropic, local IDE frustrations, and prototyping MCP in Zed.8:01–12:26 · Guest teaching 4/10 Architectural Inspiration from Language Server Protocol and Core Design Principles Swix identifies the classic M x N infrastructure integration problem and draws parallels to LSP. Justin and David explain adopting JSON-RPC to keep underlying transport boring while focusing innovation on primitives.12:26–19:25 · Guest teaching 4/10 Deconstructing MCP Primitives: Tools, Resources, and Prompts Swix shares diagrams and prompts the guests on why MCP split primitives into tools, resources, and prompts. The guests explain how presentation and user-versus-model initiation guided these abstractions.19:25–29:24 · Guest teaching 5/10 Information Architecture: Differentiating Tools from Resources and Raw Data Handling Alessio presses on common SDK design pitfalls where server builders over-filter API responses, citing the Google Maps reference server. Justin admits Claude wrote much of it, and David argues developers must unlearn decades of rigid API schema formatting when building for LLMs.29:24–32:43 · Guest teaching 6/10 Evaluating Protocol Differences: Model Context Protocol versus OpenAPI Swix asks for a definitive breakdown between MCP and OpenAPI. Justin and David articulate that OpenAPI is too granular and stateless, whereas MCP provides stateful higher-level agentic primitives.32:43–40:10 · Guest teaching 4/10 Practical Server Development Strategies and AI-Assisted Implementation Alessio references hackathons where builders use agents to autogenerate MCP servers from API specs. Guests explain how LLMs can easily one-shot server development directly from SDK context.40:10–45:33 · Guest teaching 5/10 Composability, Bi-Directional Model Sampling, and the Agent Spectrum Alessio asks how MCP servers can be composed into DAGs, and Swix pushes on whether a recursive client-server MCP construct constitutes an agent. David and Justin differentiate simple proxies from agentic sampling loops.45:33–54:43 · Guest teaching 5/10 Context Limits, Tool Routing, and Registry Ecosystem Security Swix examines tool context ceilings (250 tools) and challenges registry security models, arguing that package trust metrics can be easily compromised. Guests emphasize that client applications must retain ultimate control over tool filtering.54:43–1:01:20 · Guest teaching 4/10 Technical Deep Dive into Reference Servers: Memory, Filesystem, and Sequential Thinking Swix reviews reference servers such as memory and filesystem, asking about the relationship between sequential thinking MCP and Anthropic's new Think tool blog post. Justin explains these servers often bridge capabilities ahead of native model adoption.1:01:20–1:09:59 · Guest teaching 6/10 Roadmap Architecture: Streamable HTTP Transport, Authentication, and Scopes The discussion turns to the transition from persistent SSE to streamable HTTP transport. Alessio asks about dynamic granular scoping for enterprise data, and Justin outlines the protocol conservatism necessary to preserve backwards compatibility.1:09:59–1:18:05 · Guest teaching 5/10 Open-Source Governance, Community Stewardship, and Multi-Company Maintenance David emphasizes that drive-by commenters without code contributions will be disregarded. Swix challenges the centralization of governance by citing GraphQL's foundation donation, while David and Justin defend nimble multi-company maintenance to avoid death by committee.1:58–8:01 · Guest disagreement 0/10 The Inception and Origin Story of MCP at Anthropic The hosts set up the episode warmly and ask for the inception story. David and Justin recount early brainstorming at Anthropic, local IDE frustrations, and prototyping MCP in Zed.8:01–12:26 · Guest disagreement 1/10 Architectural Inspiration from Language Server Protocol and Core Design Principles Swix identifies the classic M x N infrastructure integration problem and draws parallels to LSP. Justin and David explain adopting JSON-RPC to keep underlying transport boring while focusing innovation on primitives.12:26–19:25 · Guest disagreement 1/10 Deconstructing MCP Primitives: Tools, Resources, and Prompts Swix shares diagrams and prompts the guests on why MCP split primitives into tools, resources, and prompts. The guests explain how presentation and user-versus-model initiation guided these abstractions.19:25–29:24 · Guest disagreement 1/10 Information Architecture: Differentiating Tools from Resources and Raw Data Handling Alessio presses on common SDK design pitfalls where server builders over-filter API responses, citing the Google Maps reference server. Justin admits Claude wrote much of it, and David argues developers must unlearn decades of rigid API schema formatting when building for LLMs.29:24–32:43 · Guest disagreement 2/10 Evaluating Protocol Differences: Model Context Protocol versus OpenAPI Swix asks for a definitive breakdown between MCP and OpenAPI. Justin and David articulate that OpenAPI is too granular and stateless, whereas MCP provides stateful higher-level agentic primitives.32:43–40:10 · Guest disagreement 1/10 Practical Server Development Strategies and AI-Assisted Implementation Alessio references hackathons where builders use agents to autogenerate MCP servers from API specs. Guests explain how LLMs can easily one-shot server development directly from SDK context.40:10–45:33 · Guest disagreement 2/10 Composability, Bi-Directional Model Sampling, and the Agent Spectrum Alessio asks how MCP servers can be composed into DAGs, and Swix pushes on whether a recursive client-server MCP construct constitutes an agent. David and Justin differentiate simple proxies from agentic sampling loops.45:33–54:43 · Guest disagreement 2/10 Context Limits, Tool Routing, and Registry Ecosystem Security Swix examines tool context ceilings (250 tools) and challenges registry security models, arguing that package trust metrics can be easily compromised. Guests emphasize that client applications must retain ultimate control over tool filtering.54:43–1:01:20 · Guest disagreement 1/10 Technical Deep Dive into Reference Servers: Memory, Filesystem, and Sequential Thinking Swix reviews reference servers such as memory and filesystem, asking about the relationship between sequential thinking MCP and Anthropic's new Think tool blog post. Justin explains these servers often bridge capabilities ahead of native model adoption.1:01:20–1:09:59 · Guest disagreement 2/10 Roadmap Architecture: Streamable HTTP Transport, Authentication, and Scopes The discussion turns to the transition from persistent SSE to streamable HTTP transport. Alessio asks about dynamic granular scoping for enterprise data, and Justin outlines the protocol conservatism necessary to preserve backwards compatibility.1:09:59–1:18:05 · Guest disagreement 3/10 Open-Source Governance, Community Stewardship, and Multi-Company Maintenance David emphasizes that drive-by commenters without code contributions will be disregarded. Swix challenges the centralization of governance by citing GraphQL's foundation donation, while David and Justin defend nimble multi-company maintenance to avoid death by committee.1:58–8:01 · The hosts pushing back 1/10 The Inception and Origin Story of MCP at Anthropic The hosts set up the episode warmly and ask for the inception story. David and Justin recount early brainstorming at Anthropic, local IDE frustrations, and prototyping MCP in Zed.8:01–12:26 · The hosts pushing back 2/10 Architectural Inspiration from Language Server Protocol and Core Design Principles Swix identifies the classic M x N infrastructure integration problem and draws parallels to LSP. Justin and David explain adopting JSON-RPC to keep underlying transport boring while focusing innovation on primitives.12:26–19:25 · The hosts pushing back 2/10 Deconstructing MCP Primitives: Tools, Resources, and Prompts Swix shares diagrams and prompts the guests on why MCP split primitives into tools, resources, and prompts. The guests explain how presentation and user-versus-model initiation guided these abstractions.19:25–29:24 · The hosts pushing back 3/10 Information Architecture: Differentiating Tools from Resources and Raw Data Handling Alessio presses on common SDK design pitfalls where server builders over-filter API responses, citing the Google Maps reference server. Justin admits Claude wrote much of it, and David argues developers must unlearn decades of rigid API schema formatting when building for LLMs.29:24–32:43 · The hosts pushing back 1/10 Evaluating Protocol Differences: Model Context Protocol versus OpenAPI Swix asks for a definitive breakdown between MCP and OpenAPI. Justin and David articulate that OpenAPI is too granular and stateless, whereas MCP provides stateful higher-level agentic primitives.32:43–40:10 · The hosts pushing back 2/10 Practical Server Development Strategies and AI-Assisted Implementation Alessio references hackathons where builders use agents to autogenerate MCP servers from API specs. Guests explain how LLMs can easily one-shot server development directly from SDK context.40:10–45:33 · The hosts pushing back 4/10 Composability, Bi-Directional Model Sampling, and the Agent Spectrum Alessio asks how MCP servers can be composed into DAGs, and Swix pushes on whether a recursive client-server MCP construct constitutes an agent. David and Justin differentiate simple proxies from agentic sampling loops.45:33–54:43 · The hosts pushing back 4/10 Context Limits, Tool Routing, and Registry Ecosystem Security Swix examines tool context ceilings (250 tools) and challenges registry security models, arguing that package trust metrics can be easily compromised. Guests emphasize that client applications must retain ultimate control over tool filtering.54:43–1:01:20 · The hosts pushing back 2/10 Technical Deep Dive into Reference Servers: Memory, Filesystem, and Sequential Thinking Swix reviews reference servers such as memory and filesystem, asking about the relationship between sequential thinking MCP and Anthropic's new Think tool blog post. Justin explains these servers often bridge capabilities ahead of native model adoption.1:01:20–1:09:59 · The hosts pushing back 3/10 Roadmap Architecture: Streamable HTTP Transport, Authentication, and Scopes The discussion turns to the transition from persistent SSE to streamable HTTP transport. Alessio asks about dynamic granular scoping for enterprise data, and Justin outlines the protocol conservatism necessary to preserve backwards compatibility.1:09:59–1:18:05 · The hosts pushing back 5/10 Open-Source Governance, Community Stewardship, and Multi-Company Maintenance David emphasizes that drive-by commenters without code contributions will be disregarded. Swix challenges the centralization of governance by citing GraphQL's foundation donation, while David and Justin defend nimble multi-company maintenance to avoid death by committee.

speaking balance: gold is the hosts, purple is the guest (3 minute bins)

0:00 · the hosts 4.5% · guest 95.5%0:00 · the hosts 4.5% · guest 95.5%3:00 · the hosts 3.5% · guest 96.5%3:00 · the hosts 3.5% · guest 96.5%6:00 · the hosts 6.9% · guest 93.1%6:00 · the hosts 6.9% · guest 93.1%9:00 · the hosts 0% · guest 100%9:00 · the hosts 0% · guest 100%12:00 · the hosts 0% · guest 100%12:00 · the hosts 0% · guest 100%15:00 · the hosts 0% · guest 100%15:00 · the hosts 0% · guest 100%18:00 · the hosts 16.4% · guest 83.6%18:00 · the hosts 16.4% · guest 83.6%21:00 · the hosts 0% · guest 100%21:00 · the hosts 0% · guest 100%24:00 · the hosts 25.2% · guest 74.8%24:00 · the hosts 25.2% · guest 74.8%27:00 · the hosts 22.4% · guest 77.6%27:00 · the hosts 22.4% · guest 77.6%30:00 · the hosts 9.7% · guest 90.3%30:00 · the hosts 9.7% · guest 90.3%33:00 · the hosts 8.9% · guest 91.1%33:00 · the hosts 8.9% · guest 91.1%36:00 · the hosts 21.2% · guest 78.8%36:00 · the hosts 21.2% · guest 78.8%39:00 · the hosts 13.1% · guest 86.9%39:00 · the hosts 13.1% · guest 86.9%42:00 · the hosts 0% · guest 100%42:00 · the hosts 0% · guest 100%45:00 · the hosts 0% · guest 100%45:00 · the hosts 0% · guest 100%48:00 · the hosts 9.9% · guest 90.1%48:00 · the hosts 9.9% · guest 90.1%51:00 · the hosts 15.9% · guest 84.1%51:00 · the hosts 15.9% · guest 84.1%54:00 · the hosts 0% · guest 100%54:00 · the hosts 0% · guest 100%57:00 · the hosts 0% · guest 100%57:00 · the hosts 0% · guest 100%1:00:00 · the hosts 0% · guest 100%1:00:00 · the hosts 0% · guest 100%1:03:00 · the hosts 9.5% · guest 90.5%1:03:00 · the hosts 9.5% · guest 90.5%1:06:00 · the hosts 18.8% · guest 81.2%1:06:00 · the hosts 18.8% · guest 81.2%1:09:00 · the hosts 0% · guest 100%1:09:00 · the hosts 0% · guest 100%1:12:00 · the hosts 0% · guest 100%1:12:00 · the hosts 0% · guest 100%1:15:00 · the hosts 0% · guest 100%1:15:00 · the hosts 0% · guest 100%1:18:00 · the hosts 9.2% · guest 90.8%1:18:00 · the hosts 9.2% · guest 90.8%
Sharpest disagreement ▶ 1:10:08 David warns drive-by open source commentators will be ignored

David bluntly pushes back on passive community commentary, asserting that contributors who just share opinions without writing code or building SDK extensions will simply be ignored.

 Hardest push from the hosts ▶ 1:13:04 Swix challenges Anthropic's long-term stewardship using GraphQL precedent

Swix directly presses whether Anthropic's control will hit a ceiling and challenges the guests on donating the standard to a neutral foundation like Linux or Apache.

 Biggest teaching moment ▶ 27:32 David explains unlearning traditional software engineering API design

David reframes how developers must approach LLM interfaces, explaining that developers need to unlearn decades of software engineering habits and stop pre-structuring data before passing it to LLMs.

 The host holds their own ▶ 25:04 Alessio critiques over-filtered API wrappers in reference MCP servers

Alessio demonstrates technical expertise by critiquing server SDK wrappers like Google Maps that omit raw parameters and restrict user control over payload responses.
the scores for every segment, with the reasoning behind each
ChapterTopicThe hosts as informed peerGuest teachingGuest disagreementThe hosts pushing backWhy
The Inception and Origin Story of MCP at Anthropic 3201 The hosts set up the episode warmly and ask for the inception story. David and Justin recount early brainstorming at Anthropic, local IDE frustrations, and prototyping MCP in Zed.
Architectural Inspiration from Language Server Protocol and Core Design Principles 5412 Swix identifies the classic M x N infrastructure integration problem and draws parallels to LSP. Justin and David explain adopting JSON-RPC to keep underlying transport boring while focusing innovation on primitives.
Deconstructing MCP Primitives: Tools, Resources, and Prompts 6412 Swix shares diagrams and prompts the guests on why MCP split primitives into tools, resources, and prompts. The guests explain how presentation and user-versus-model initiation guided these abstractions.
Information Architecture: Differentiating Tools from Resources and Raw Data Handling 7513 Alessio presses on common SDK design pitfalls where server builders over-filter API responses, citing the Google Maps reference server. Justin admits Claude wrote much of it, and David argues developers must unlearn decades of rigid API schema formatting when building for LLMs.
Evaluating Protocol Differences: Model Context Protocol versus OpenAPI 4621 Swix asks for a definitive breakdown between MCP and OpenAPI. Justin and David articulate that OpenAPI is too granular and stateless, whereas MCP provides stateful higher-level agentic primitives.
Practical Server Development Strategies and AI-Assisted Implementation 6412 Alessio references hackathons where builders use agents to autogenerate MCP servers from API specs. Guests explain how LLMs can easily one-shot server development directly from SDK context.
Composability, Bi-Directional Model Sampling, and the Agent Spectrum 6524 Alessio asks how MCP servers can be composed into DAGs, and Swix pushes on whether a recursive client-server MCP construct constitutes an agent. David and Justin differentiate simple proxies from agentic sampling loops.
Context Limits, Tool Routing, and Registry Ecosystem Security 7524 Swix examines tool context ceilings (250 tools) and challenges registry security models, arguing that package trust metrics can be easily compromised. Guests emphasize that client applications must retain ultimate control over tool filtering.
Technical Deep Dive into Reference Servers: Memory, Filesystem, and Sequential Thinking 6412 Swix reviews reference servers such as memory and filesystem, asking about the relationship between sequential thinking MCP and Anthropic's new Think tool blog post. Justin explains these servers often bridge capabilities ahead of native model adoption.
Roadmap Architecture: Streamable HTTP Transport, Authentication, and Scopes 7623 The discussion turns to the transition from persistent SSE to streamable HTTP transport. Alessio asks about dynamic granular scoping for enterprise data, and Justin outlines the protocol conservatism necessary to preserve backwards compatibility.
Open-Source Governance, Community Stewardship, and Multi-Company Maintenance 7535 David emphasizes that drive-by commenters without code contributions will be disregarded. Swix challenges the centralization of governance by citing GraphQL's foundation donation, while David and Justin defend nimble multi-company maintenance to avoid death by committee.

Statements from this episode (0)

Nothing in this episode matches those filters. clear them

Made with StarZero

Turn any episode into a week of clips.

This entire site, over 200 episodes transcribed, diarized, checked and made playable, runs on the StarZero media pipeline. Drop in your own episode and the podcast clipper finds the moments worth sharing, cuts them, captions them, and reframes them for every feed.

Try the podcast clipper Learn more