3.3 — MCP: USB-C for AI

🟢 In plain words — MCP avoids reinventing the cable for every piece of software. Instead of coding a custom integration for the calendar, another for email, another for the database, you plug into MCP servers that all speak the same language. The protocol standardises the exchange; it does not automatically grant access to applications or data.

🔌 The (official) analogy: MCP = USB-C for AI. Before, each piece of software required its own “cable” (a specific integration). With MCP, you plug into an MCP server (a small connector that exposes an application to the AI) and the AI instantly accesses the application. An order like “find a slot in my calendar” becomes: the agent calls the calendar tool via MCP, reads the result, confirms the action.

📅 The facts (verified). MCP was introduced by Anthropic in November 2024 as an open standard. It was adopted very fast: OpenAI (March 2025) and Google DeepMind (April 2025) integrated it. Adoption is broad, but no single auditable counter supports a precise number of active servers here.

Caution

⚠️ The flip side (preview of Level 4): plugging an AI into your real tools = giving it the power to act for real. A poorly contained agent can send the wrong email or delete a file. “Power” implies “guardrails.” More in Module 4.

🧩 Concrete example — before USB-C, every phone had its own charger: one cable per device, a drawer full of incompatible cords. USB-C unified everything. MCP does the same for AI: a single “plug” instead of one cable per piece of software.

⏳ Freshness note: the MCP ecosystem moves fast (number of servers, vendors that adopt it). The principle — a single standard to plug the AI into everything — stays stable.

✅ In short

• MCP (Anthropic, Nov. 2024) is an open standard to plug the AI into your tools.
• It standardises the interface, not trust, authentication, permissions or security.
• Key image: it’s USB-C for AI — a single plug instead of one cable per piece of software.
• More power = more risk: hence the guardrails of Module 4.

Primary source: official MCP documentation.

🔎 Going further (tech) — build a real MCP server (the 3 primitives: Tools / Resources / Prompts) in the niveau-4-mcp-server.ipynb notebook: a mini offline server, then the real mcp SDK (FastMCP), no API key.