← AI glossary

AI glossary · Basic · Agents

MCP

MCP (Model Context Protocol) is an open protocol that lets AI apps connect to external resources such as files, databases and work tools in the same way. A connector built once for MCP can be used as-is in many AI apps that support MCP.

About this term
Level
Basic · Technical terms you often meet in AI news
Fields
Agents
Added
2026-10-08
In plain words It is similar to replacing the different charging ports on each device with a single USB-C standard. However, MCP only standardizes "how things connect," so it does not guarantee that the connected tools are safe or useful.

How it works

MCP has three roles: the AI app the user uses (the host), the MCP client inside that app that handles connections, and the MCP server that actually provides tools or data. An MCP server announces, in a defined format, a list saying "these are the tools and resources I can provide," and the AI model picks one of them and calls it when needed. When the call result returns to the model, the model continues building its answer based on that content. A server can run on your own computer or be a remote server across the internet.

MCP connection structureUser → AI model(Request); AI model → MCP client(Tool call); MCP client → MCP server A; MCP client → MCP server B; MCP client → MCP server C; MCP server A → Files on my computer; MCP server B → Internal company DB; MCP server C → Messenger & calendarAI app (host)UserAI modelPicks tools and readsresultsMCP clientMCP server AFilesMCP server BDatabaseMCP server CWork toolsFiles on mycomputerInternal companyDBMessenger &calendarRequestTool call
MCP connection structure The MCP client inside the AI app connects to multiple MCP servers using the same protocol, and each server provides its own tools or data. The server types are examples.

Why it matters

Before MCP, connection code had to be written separately for each AI app and each tool. As the number of apps and tools grew, the number of connections to build multiplied. With a common protocol, the tool side only needs to build one MCP server, and the app side only needs an MCP client. As a result, the number of tools available to AI agents grew quickly, and many AI companies and developer tools came to support MCP.

Things to know

MCP servers hand real permissions to the AI, such as editing files or sending messages. So you need to be careful about installing servers from unclear sources and about prompt injection, where hidden instructions are mixed into retrieved documents or tool descriptions. If too many tools are connected, the tool descriptions take up a lot of the context window and the model may pick the wrong tool. It is safer to grant only the permissions that are truly needed and to have a person confirm actions that are hard to undo.

Example

If you connect an MCP server for GitHub to a coding agent or desktop AI app, then when the user says "summarize the open issues," the AI can fetch the issue list itself and summarize it. Because the same server can be connected to other MCP-supporting apps, a company may build just one MCP server for searching internal documents and share it across several AI tools.

Related terms