unicornAll work

MCP — Model Context Protocol

One standard 'socket': connect a server once, any MCP client can use it — like USB.

In short MCP (Model Context Protocol) is an open standard by which an AI agent connects to external tools and data. One shared "socket": connect an MCP server once and any MCP-capable client (Claude Desktop, Claude Code, your app) can use it without reinventing the integration.

MCP serveradapter to a resource shared protocol MCP Claude Desktop Claude Code your app
Like USB: one plug to the standard — works everywhere.

The problem MCP solves

Tools give an agent hands (the agent loop and tools). But before, each integration was written by hand and anew for each client: describe the schema, handle the calls, maintain it. Ten tools × three apps = thirty different wirings.

MCP standardises this. A server describes its capabilities once over a shared protocol, and a client (the agent) can talk to any such server. It's like USB: not a bespoke port per device, but one common one.

Analogy: a plug and socket to one standard. A device maker needn't know the building's wiring — they make a plug to the standard, and the device works everywhere.

How it works

Once the model has access to an MCP server, it sees its tools as ordinary tools and calls them in the agent loop.

Why it matters to you

The safety line

An MCP server gets access to a real resource and can act. So the same rules apply as for any tools: permissions and review (the agent loop and tools). Connect trusted servers and understand what each one is allowed to do.

Related

The source is the Claude Platform 101, Claude Code 101 and Introduction to Claude Cowork courses. Related: the agent loop and tools, Claude skills, Claude Code setup.

All theory