Skip to content
BENIBIX Learn

Model Context Protocol (MCP)

AI🔌 MCPMCP Architecture

Also known as MCP, Model Context Protocol

A shared plug that lets any AI app use tools and data.

Think of it like

Think of it like one plug that fits every socket. Any app can use any tool that has it.

Example

Lucy adds one GitHub server to her settings. Both her chat app and her code editor can now read her issues, with no extra code.

Why it matters

It turns many one-off links into one shared plug. A tool built once works in every app.

Definition

The Model Context Protocol, or MCP, is an open standard for linking AI apps to tools and data. A tool maker builds one MCP server, and any app that speaks MCP can use it. Before MCP, each app needed its own custom link to each tool. The protocol sets how the two sides find out what the other offers and how they swap messages. It was first released in 2024 and is now used by most major AI apps.

Example code

json
{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"]
    }
  }
}
A typical settings entry that adds one MCP server. The app starts it and finds its tools.
Without MCP, every app needs a link to every tool. With MCP, they all share one plug.

Common mistake

Thinking MCP is a model or an app. It is only the agreement on how apps and tools talk.

Key takeaways

  1. 1
    One shared plug. Build once, use anywhere.
  2. 2
    Apps and tools. Two sides, one language.
  3. 3
    Open standard. Not tied to one maker.

Compare