Why you should care about a tech acronym
Normally we'd never ask a general reader to learn a protocol name. MCP is the exception, for one reason: it's the invisible thing that decides what your AI can actually do for you. When your assistant can suddenly read your calendar, search your files, or check your company's systems — MCP is usually why. Knowing roughly how it works makes you better (and safer) at using AI.
The problem: a genius in a glass box
Picture the smartest assistant in the world — locked in a glass box. You can talk through the glass, and the answers are brilliant. But your calendar, your files, your email? All outside the box. Every useful fact has to be copy-pasted in by you; everything it produces has to be copy-pasted out.
That was AI before agents got tools. And when companies did wire an AI to an app, each connection was custom-built — like needing a different charger for every gadget you own. A thousand apps and a dozen AIs would need twelve thousand custom wires. It couldn't scale.
The idea: one standard plug
Remember drawers full of incompatible chargers — one per phone, camera and gadget? Then USB-C arrived: one connector shape, and suddenly everything fits everything.
MCP (Model Context Protocol) does that for AI. It's a standard way for any app to say 'here's what I can do' and for any AI to use it. The app builds one MCP connection, the AI speaks MCP — and they fit. No custom wiring per pairing, ever again. That's why 'the USB-C of AI' stuck as the nickname.
How it works — the menu analogy
When an app offers an MCP connection (called an 'MCP server' — you'll see the term in settings screens), it's essentially publishing a menu of what it can do. Your calendar's menu might read: check availability, list events, create event, delete event.
An AI connected to that menu can now order from it — and only from it. If 'delete event' isn't on the menu you allowed, the AI simply has no way to delete anything. The menu is both the capability and the boundary.
A short history, for context
Anthropic (the company behind Claude) introduced MCP in November 2024 as an open standard — meaning anyone could use it, including competitors. That openness is why it won: within a year, the major AI labs and thousands of apps had adopted it, the way the whole industry eventually settled on USB.
By 2026 it's simply plumbing — the reason the agent era works at all. Agents without connections are geniuses in glass boxes; MCP is how the box got doors.
What it means for you, practically
- 1When an AI app asks to 'connect' to your files, calendar or another service — that's usually an MCP connection. Treat it like granting a door key.
- 2Grant the narrowest useful access: read-only if reading is enough, one folder rather than the whole drive.
- 3Review your connections now and then, and revoke ones you no longer use — same hygiene as app permissions on your phone.
