[For Beginners] What is MCP? - Explaining the difference from APIs in simple terms
Recently, I've been hearing phrases like
"Can we connect that via MCP?"
,
"Do we need an API?"
, or
"We can integrate it using MCP instead of an API."
more and more often.
But honestly,
"I don't even really understand APIs, and now MCP...?"
doesn't that cross your mind?
Plus,
IT terminology is full of foreign words, so conversations start sounding like incantations halfway through.
Today, I'll try to break down what "MCP" is, including how it differs from an API, in the simplest way possible.
━━━━━━━━━━━━━━
First, what was an API again?
To put it very simply, an API is—
"a gateway that connects systems to each other."
For example,
・ChatGPT
・Google Drive
・LINE
・Spreadsheets
are gateways for exchanging information, like
"Please give me this data"
or
"I'll pass you this information."
━━━━━━━━━━━━━━
So then, what is MCP?
MCP stands for Model Context Protocol.
…More foreign words, right?
To put it very simply, it is—
"a common connection standard for AI to talk to various external tools."
━━━━━━━━━━━━━━
To put it even more simply
An API was
"a gateway that connects systems to each other."
On the other hand, MCP is
like "a set of rules for AI to interact with various tools."
━━━━━━━━━━━━━━
For example, an API is
the reception desk at a store.
━━━━━━━━━━━━━━
Customer
↓
Reception (API)
↓
Kitchen
It's something like that.
━━━━━━━━━━━━━━
On the other hand, MCP is closer to
"a mechanism where you can order with the same feeling at any store."
━━━━━━━━━━━━━━
For example,
・Order with this button
・Communicate in this format
・Use up to these permissions
If there is a common connection standard like this,
the AI side
"doesn't have to memorize different operations every time."
━━━━━━━━━━━━━━
Why did MCP appear?
This is a point that feels very much like the AI era.
Until now, it was
Person
↓
Use an API
But recently, it has become an era of
AI
↓
Use various tools.
━━━━━━━━━━━━━━
For example, when an AI does things like
・Look at Google Drive
・Read Slack
・Check calendar
・Organize Notion
・Draft emails
it's quite difficult if the connection method is different every time.
━━━━━━━━━━━━━━
That's where MCP comes in.
By using MCP,
it becomes easier for AI to handle external tools with
"the same way of thinking."
━━━━━━━━━━━━━━
To state the difference roughly
API
= Gateway
MCP
= A common connection standard for AI to use that gateway
It's something like that.
━━━━━━━━━━━━━━
Actually, it's easy for beginners to get confused.
This is quite natural.
Because
・API
・API key
・MCP
・Integration
・Plugin
are all
"about connecting things."
━━━━━━━━━━━━━━
But what's important is
not "memorizing everything,"
but understanding "what is being connected."
━━━━━━━━━━━━━━
Convenient, but caution is also necessary.
Both MCP and API are
"about accessing external tools."
In other words,
・How much can it see?
・What can it operate?
・Whose permissions does it run under?
are quite important.
━━━━━━━━━━━━━━
Recently, we are approaching an era where
"AI does various things on its own."
That is precisely why,
it is becoming important to think not just "How convenient!"
but also "How much should I entrust to it?"
━━━━━━━━━━━━━━
Finally,
MCP feels quite difficult at first.
But in reality, it is the concept of
"a common connection standard for AI to talk to various external tools."
I currently provide support for AI and digital tools,
and rather than memorizing difficult words,
I value the moment when it clicks: "I see, that's its role!"