What MCP actually is
MCP, the Model Context Protocol, is a standard way for a model to call your tools and read your data. Before MCP, every team wrote a bespoke integration layer: custom function schemas, custom auth glue, custom retry logic, one per tool, one per vendor. MCP standardizes that boundary. A model client speaks one protocol, and any MCP server, yours or a third party's, can expose tools, resources, and prompts through it.
Think of MCP as the USB-C of the agent stack. It doesn't change what your database does or what your CRM does. It changes how the model reaches them. That's a vertical relationship: one model, talking down to a set of tools it needs for a single task.
I cover the mechanics in more depth in the MCP explainer.