
Explain like I'm five
Imagine you're baking a cake and need to check the recipe, grab eggs from the fridge, and set a timer—all at once. Model Context Protocol is like a helpful kitchen assistant that safely hands you each thing exactly when you need it, without you having to stop and search. It lets AI models ask for information from different places in a neat, organized way.

Why it matters
This matters because it lets AI models do more complex tasks, like booking a flight or answering questions from your calendar, without being given all the data upfront. You encounter it in apps where an AI assistant needs to pull info from multiple sources, like your email or a weather service, to help you.

Common misconception
People often think Model Context Protocol is a specific AI model, but it's actually a communication standard—like a rulebook for how models talk to tools. Another mix-up is that it's the same as giving the model all context at once, but it's about securely requesting only what's needed, when it's needed.

Formal definition
Model Context Protocol (MCP) is an open protocol that standardizes how AI models interact with external context sources, such as databases, APIs, and file systems. It defines a client-server architecture where the model (client) can request specific data from servers that expose resources and tools, enabling dynamic, secure, and efficient access to context without embedding it in the prompt. MCP is designed to reduce complexity and improve interoperability in AI-powered applications.