003 - What Is MCP? The Model Context Protocol Explained

Hook an AI assistant up to your files, your calendar, and a database at work, and someone has to build all three connections by hand. Add a fourth tool and you wire it up again; switch assistants and much of that work starts over. MCP, the Model Context Protocol, exists to end that one-off plumbing. This episode explains what MCP actually is, how it's structured, and what a company is really claiming when it says its app supports MCP. MCP is an open standard introduced by Anthropic in 2024, and it is no longer Anthropic's alone. In December 2025, Anthropic donated the protocol to the Agentic AI Foundation, a vendor-neutral project under the Linux Foundation, co-founded alongside Block and OpenAI. The project's own analogy for itself is a USB-C port for AI applications: rather than every application inventing a private way to reach every tool and data source, MCP provides one common interface. The episode walks through the architecture. The AI application is the host. Inside it, an MCP client handles standardized communication with one or more MCP servers, and an MCP server is a program that exposes capabilities to the application — access to GitHub, a database, a file system, or another service. Because client and server follow the same protocol, the application can discover what a server offers and interact with it through a consistent pattern. Servers can expose three kinds of capabilities: tools, which are actions the model can invoke like running a search or writing a file; resources, which are data the application can read such as documents or database records; and prompts, which are reusable templates for common tasks. A server might expose one, several, or all three. The episode is careful not to oversell interoperability. A standardized connection pattern is not the same as universal compatibility — protocol versions, supported capabilities, authentication, permissions, and transport all still matter, and not every client works with every server in every situation. It also connects MCP back to the agent from episode 2: the agent decides what to do, while MCP is the common doorway it uses to reach outside tools and data. It closes on the security question. A doorway to real files, accounts, and services raises genuine questions about what an application can reach, what it can change, and what credentials it uses. A standard makes connecting easier, but deciding what should be connected still takes judgment. Sources & References Introduction, Model Context Protocol documentation — https://modelcontextprotocol.io/docs/getting-started/intro Architecture overview, Model Context Protocol documentation — https://modelcontextprotocol.io/docs/2026-07-28/learn/architecture MCP joins the Agentic AI Foundation, Model Context Protocol Blog — https://blog.modelcontextprotocol.io/posts/2025-12-09-mcp-joins-agentic-ai-foundation/ Linux Foundation Announces the Formation of the Agentic AI Foundation — https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-agentic-ai-foundation Voice narration is AI-generated.