An API lets one piece of software talk to another. MCP (Model Context Protocol) is a newer idea: a standard way for AI models, particularly large language models, to discover and use tools, files and data sources without a developer wiring up a custom integration for each one.
What an API actually is
API stands for application programming interface. It is a general term for any defined way that one program can request something from another: a weather service exposing endpoints for temperature data, a payments platform exposing endpoints for charging a card, a mobile app talking to its backend.
APIs come in many shapes (REST, GraphQL, gRPC, and so on), but they share a common pattern: the developer reads the documentation, learns the specific requests the API expects, and writes code to call it.
import requests
response = requests.get(
"https://example.com/api/weather",
params={"city": "London"}
)
print(response.json())That code only works because a human read the docs and wrote it to match this one API. A different API means different code.
Where MCP fits in
MCP is a protocol designed for a different problem: how does an AI model know what tools exist, what they do, and how to call them, without a developer hand-coding every possible connection in advance?
Instead of a model being limited to whatever a developer explicitly programmed it to call, an MCP server describes its own tools and data in a standard format. Any MCP-compatible client, including an AI assistant, can read that description and work out how to use the tool on the fly.
Wondering how this was made? How we make these