MCP simply explained: the Model Context Protocol as USB-C for AI agents

When someone tells you in 2026 that AI agents "operate your systems", there is almost always a three-letter detail behind it: MCP. The Model Context Protocol is the common connector through which an agent talks to your tools, files and data sources. The best image for it: MCP is the USB-C for AI agents. One plug, many devices, instead of a separate cable for every tool.

I (Sebastian) deliberately explain MCP in workshops without tech jargon, because the idea is simple and the effect is large. Before MCP, every connection between an AI and an internal system had to be built individually. With MCP there is a standard, and that very standard is one of the reasons agentic work suddenly became practical in 2026.

As of October 2026

What MCP is, without the jargon

An AI agent on its own can only produce text. It becomes useful when it can do something: read a file, fetch a record, create an entry in a system. For that it needs tools. MCP is the uniform language in which an agent and a tool talk to each other. A tool is connected via a so-called MCP server, and any MCP-capable agent can use it. That is the whole trick: connect once, usable everywhere. What an agent actually does with such tools is in how AI agents work.

Why the USB-C image fits

Before USB-C, every device had its own plug and you needed a different cable for everything. Before MCP it was the same: whoever wanted to connect ChatGPT to the CRM built a custom solution that worked with no other tool. MCP standardises the plug. An MCP server built once for your ticket system works with any agent that speaks MCP, whether Claude, ChatGPT or another. That drastically lowers the cost per integration and makes vendors more interchangeable.

Why MCP became the standard in 2026

MCP was introduced by Anthropic as an open standard in late 2024, with support for local MCP servers in the Claude desktop apps. What matters is what happened next: in March 2025 OpenAI added MCP support to its Agents SDK. In December 2025 Anthropic counted more than 10,000 active public MCP servers, and ChatGPT, Cursor, Gemini, Microsoft Copilot and Visual Studio Code had adopted the standard. In the same month Anthropic handed MCP to the Agentic AI Foundation (AAIF) under the Linux Foundation. The AAIF was co-founded by Anthropic, Block and OpenAI, with support from Google, Microsoft, AWS, Cloudflare and Bloomberg. With that, MCP is no longer a vendor project but neutral industry infrastructure. In July 2026 the MCP project reported close to half a billion downloads a month across its Tier 1 SDKs.

What changed in 2026

Two developments from summer 2026 matter for you: a new version of the protocol and a shared home with the agent protocol A2A.

The 28 July 2026 specification

On 28 July 2026 the MCP project released the 2026-07-28 specification. The most important change: the protocol core is now stateless. The previous connection setup (initialize) and the Mcp-Session-Id session header are gone. Every request carries its protocol version, client identity and capabilities itself. On top of that:

• Easier scaling: any request can land on any server instance behind a plain load balancer, without shared session storage. Tool lists carry cache hints (ttlMs, cacheScope).
• More control on the network: method and tool name travel in the Mcp-Method and Mcp-Name HTTP headers. A gateway, rate limiter or web application firewall can route and meter requests on them without reading the JSON body.
• Hardened sign-in: clients must validate the issuer per RFC 9207. Dynamic Client Registration is deprecated in favour of Client ID Metadata Documents.
• Extensions instead of core: Tasks, MCP Apps and Enterprise Managed Authorization run as formal extensions. Questions to the user in the middle of a tool call go through Multi Round-Trip Requests instead of permanently open connections.
• Plannable migration: the four Tier 1 SDKs (TypeScript, Python, Go, C#) support the new version, the Rust SDK in beta. A formal deprecation policy sets a minimum window of twelve months.

For developers of existing MCP servers, the project announces some migration cost, especially where they relied on session identifiers.

Who governs MCP today

MCP sits with the Agentic AI Foundation, hosted by the Linux Foundation. Its projects cover different layers: AGENTS.md (instructions and context for agents), goose (an agent runtime), MCP (connecting agents to tools and data), agentgateway (routing, policy and observability of agent traffic) and, since 17 August 2026, A2A, the protocol Google launched for communication between agents. A2A shipped its first stable version, 1.0, in March 2026. On 13 August 2026 the Linux Foundation reported 247 AAIF member organisations, including the new Gold members Alibaba Group, Visa and Wells Fargo. How MCP and A2A work together and when you need which protocol is covered in MCP vs A2A: what IT leads need to know now.

What this means in practice for the Mittelstand

Three concrete consequences, without you having to build an MCP server yourself:

Agents can reach your systems. With MCP, an agent like Claude Code or the agents used in Cursor can be connected to your ticket system, your docs or internal services, instead of only drawing on training knowledge.

Less lock-in. Because the connector is standardised, you tie yourself less to a single AI vendor. An integration built once survives a tool switch.

Security becomes homework. A standard plug also means an agent can trigger real actions via MCP. So access rights, approvals and a deliberate choice of which MCP servers are allowed at all are mandatory. How much an agent may do on its own is covered in the human-in-the-loop guide. Rules for connectors and MCP servers are also part of the agent annex in our free AI policy template.

FAQ

Do I need to understand MCP to use AI? Not in daily use. But as soon as agents are meant to reach your systems, MCP is the keyword purchasing and IT should ask about. It decides effort and interchangeability.

Is MCP tied to Anthropic? No, not any more. Since December 2025 MCP sits with the Agentic AI Foundation under the Linux Foundation and is supported by several major vendors. It is an open standard, not a vendor product.

Do we need our own MCP servers? Often not immediately. For common systems there are ready-made MCP servers. You build your own where internal special systems need connecting. That is a manageable developer topic.

What does it mean that MCP is now stateless? Since the 28 July 2026 specification there is no session at protocol level any more: every request carries its protocol version, client identity and capabilities itself. That lets any request land on any server instance, without shared session storage. Your application can still keep state: the MCP project recommends an explicit handle that a tool returns and the model passes on to the next calls.

Is MCP secure? The standard itself is neutral; security lies in the configuration: which servers are allowed, what rights they have and which actions need a human approval. That is governance, not a tool purchase.

Read more

• MCP vs A2A: what IT leads need to know now
• From chatbot to agent: why 2026 is the shift
• What is Claude Code? The AI agent in the terminal, simply explained
• Cursor training: from tool access to a productive agentic workflow
• How AI agents work (loop, tools, memory, planning)
• What is agentic AI? The executive crash course
• Human-in-the-loop: how much autonomy should an agent have
• A workday with AI agents: Claude Code and Cowork in the Mittelstand

Sources

• Model Context Protocol, official documentation: https://modelcontextprotocol.io
• Anthropic, Introducing the Model Context Protocol (25 Nov 2024): https://www.anthropic.com/news/model-context-protocol
• OpenAI Agents SDK, release v0.0.7 with MCP support (26 Mar 2025): https://github.com/openai/openai-agents-python/releases/tag/v0.0.7
• Anthropic, Donating the Model Context Protocol and establishing the Agentic AI Foundation (9 Dec 2025): https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation
• Model Context Protocol Blog, The 2026-07-28 Specification (28 Jul 2026): https://blog.modelcontextprotocol.io/posts/2026-07-28/
• Linux Foundation, Agentic AI Foundation Welcomes 57 New Members (13 Aug 2026): https://www.linuxfoundation.org/press/agentic-ai-foundation-welcomes-57-new-members-gaining-major-financial-services-players-and-apac-leaders
• Agentic AI Foundation, A2A joins AAIF's open agentic stack (17 Aug 2026): https://aaif.io/blog/a2a-joins-aaif

How Sentient Dynamics can help

We clarify with you which MCP connections make sense, which servers should be allowed and where human approvals belong, and we train the teams that make agents productive with your systems.

Book a demo