Model Context Protocol (MCP)
Gen AI · AI Agents & Tool Use
Theory
The Model Context Protocol (MCP) is an open standard for connecting AI applications to external tools and data, such as files, databases or business apps, through one common interface instead of a custom integration for every pair. An MCP server wraps a tool or data source and describes what it offers: tools the model can call, resources it can read and reusable prompts. An MCP client inside the AI application connects to servers, lists what they offer and passes those capabilities to the model.
Because the format is shared, one server built for a ticketing system can be reused by any compatible app or agent. This turns the "every app times every tool" integration problem into roughly "apps plus tools". MCP standardises the connection only; you still decide which servers to trust and what permissions each one gets.
Why we use it
Without a standard, every AI app needs its own connector for every tool, which multiplies work and maintenance. MCP lets a connector be written once and reused across many AI apps and agents.
When to use it
Use MCP when you want your tools or data available to several AI apps, or want to plug existing servers into your agent. For a single app calling one internal function, plain tool calling may be simpler.
How it works
- AI app starts with an MCP client
- Client connects to the configured MCP servers
- Client lists each server's tools and resources
- Model chooses a tool during the conversation
- Is the action allowed for this user? Yes: Call the server, return the result. No: Block or ask for approval.
- Model answers using the server's data
Example
Without MCP: build a custom integration between your AI app and Notion, another for Slack, another for GitHub — each from scratch.
With MCP: connect to an existing "Notion MCP server," a "Slack MCP server," and a "GitHub MCP server" — your agent instantly gains standardized access to all three, and any other MCP-aware app you build later can reuse the same servers.Key points
- Open standard connecting AI apps (clients) to tools and data (servers)
- Servers expose tools, resources and prompts in a common format
- One server can be reused across many AI apps and agents
- Standardises the connection, not trust: still review servers and permissions
- For one app and one internal function, plain tool calling may be enough