AI, Explained Simply

The Universal Plug for AI (a.k.a. why everyone's suddenly saying "MCP")

Quick question: do you have a drawer full of tangled chargers at home? One for your phone, one for your old camera, one for that random Bluetooth speaker?

That drawer is basically how AI used to work with your tools — email, databases, Slack, whatever. Every connection was custom-built, one at a time. Today I want to show you the thing that fixed it. It's called MCP (Model Context Protocol), and once you get it, you'll understand why every AI company suddenly can't stop talking about it.

---

The problem, first

Say a company wants their AI assistant to read email, check a database, and post in Slack. The old way: build a custom connection for each pair. Then they get a second AI tool. Guess what — they have to rebuild all those connections again, from scratch, just for the new one.

This is sometimes called the M×N problem: M assistants times N tools equals a growing pile of one-off wires. Nobody wants to be the person maintaining a hundred custom cables.

Analogy: before USB-C, every phone, camera and laptop had its own charger shape. You needed a whole drawer of cables. USB-C said: one plug shape, any device, any port. MCP is that idea — but for AI and the tools it uses.

How it actually works

Two simple pieces:

• MCP server — a small adapter someone builds once for a tool (Gmail, a database, your files, whatever). It exposes what that tool can do in a standard format.
• MCP client — lives inside the AI itself. It doesn't need to know anything special about Gmail vs. Slack vs. a database — it just speaks the same standard language to all of them.

Because both sides agree on the same "plug shape," any MCP-capable AI can use any MCP server, instantly. Build a server once — every AI benefits, not just the one it was built for.

The "aha" moment

Before MCP: a company wanting both Claude and ChatGPT to read their internal database had to build two separate custom integrations.

With MCP: they build the connector once, and it works for both — same way any USB-C cable works in any USB-C port, no matter the brand.

MCP is the USB-C of AI. One standard plug, so any AI can use any tool — instead of everyone building their own one-off cable.

That's really the whole idea. Everything else — the JSON configs, the server code — is just implementation detail on top of this one insight.

Got a concept you want explained this way? Just hit reply — that's exactly what this newsletter is for.