Lesson 8 / 25

Why MCP Exists

Explain the N-times-M integration problem that a shared protocol solves.

One protocol instead of many adapters

Without a standard, each AI app needs a custom connector for each tool: N apps times M tools. The Model Context Protocol (MCP) is an open standard so a tool author writes one server and any MCP-capable app can use it. It is often compared to USB-C: one port shape for many devices.

Host, client, server

An MCP host runs one client per server. Servers expose capabilities that any compatible host can use.

Three parts: host, client, server.
Figure 3.1 — Host, client and server.

A universal charger

Before common chargers, every phone needed its own cable. A shared standard lets any charger work with any phone. MCP does the same for apps and tools.

A standard, not a product

MCP is a specification with open SDKs, so you are not tied to one vendor. But the specification is still evolving, so check the current version of the docs when you build.

Quick check: What problem does MCP mainly reduce?

  • Slow GPUs
  • Writing a custom connector for every app-and-tool pair
  • Hindi translation
  • Database indexing
Answer

Writing a custom connector for every app-and-tool pair — A shared protocol turns N times M integrations into N plus M.