@kodekloud: Why We Need MCP When APIs Already Exist 🤔 One app talking to one service is easy. One app talking to 10 is where it falls apart, and you rebuild the same integration for every new app. MCP is the shared layer that fixes that. Save this for the next time someone asks you the difference. Which service would you connect first? #MCP #ModelContextProtocol #API #AIAgents #FunctionCalling #AIEngineering #LLM #MCPServer #Coding #KodeKloud
MCP is just wrapping APIs for Agentic workflows, fun to explore but not for most industrial standards. API calls returns the answer with finality, MCP at the client end returns with illustrations of certain probabilities.
2026-07-20 21:18:23
265
Shivani :
So helpful!
2026-07-21 23:13:27
0
Prodigy Luxury Apartment :
At the root they re all api
2026-07-21 00:44:00
68
marumanchi :
We dont need it that’s the answer
2026-07-22 02:06:32
0
Jonathan banks :
They are called CLI tools, write them in rust/typescript/python for optimal results
2026-07-21 18:32:27
0
Lucidor_d_inhalor :
Is it safe tho? Like I wouldn’t use MCP for banking or financial related services. Someone can trick LLM into doing something it’s not mean to. It’s an attack vector
2026-07-20 14:00:05
110
PNW4Life :
Hence the MC = multi context. It’s quite literally in the name what it does.
2026-07-22 02:48:40
0
Haktes :
put API to separate project/lib and just call it
2026-07-22 04:43:49
0
Pedrongks :
Simpler terms, MCP = So you can do changes in it. API = Access the app only.
2026-07-21 23:44:11
0
mopdd :
In my experience MCP use so many more tokens than API. I don’t know why… I’m guessing it costs a lot of compute to read all the tools and then pull in that data
2026-07-21 01:07:44
11
1 Eyed Man Child :
well done!
2026-07-22 02:21:56
0
Darrin - Enlightened_D :
MCP is just a layer on top of APIs with instructions for AI to understand how to use it
2026-07-21 15:32:34
11
TotallyNotACCPSpy :
MCP servers are very useful but you completely miss one of their most powerful points… Service discovery.
2026-07-22 03:01:39
2
iimmppoossiibbllee :
don't see the point of this.
2026-07-21 00:10:40
9
KVruno :
Bc APIs were built for humans, not bots
2026-07-21 01:19:47
31
Mark Price :
Your explanation is fundamentally flawed because an LLM cannot think nor reason.
2026-07-20 20:57:55
4
Nguyễn Hữu Chỉnh :
Actually, it’s a wrapper of API :))
2026-07-21 09:37:45
0
Riddeled Corpse :
So we add three layers of complexity instead of writing a single integration middleware. Sounds like integration with an LLM is the goal here but it’s clumsy and the extra levels of complexity make the identification of problems a nightmare.
2026-07-21 21:59:45
1
algogeeks :
Not sure i understand… if i expose an api on Slack i dont then need to rewrite it for another service to use.. and no matter what you use you would always need ti build the logic/request
2026-07-20 16:49:03
13
Harbinger2001 :
Reinventing REST…
2026-07-21 14:59:55
1
dosik🤭 :
Swagger docs already provide list of APIs with descriptions, so is MCP same?
2026-07-21 08:09:10
1
Jesus :
The logic that makes MCP appealing is in itself flawed: "I have to develop a second app so I'll go ahead and write the integrations to all 10 services from scratch". You don't do that, you create API clients that you can reuse
2026-07-21 14:16:13
0
Eluyndor :
How about: MCPs are maintained by the target app that you just discover. If there is a new endpoint, your code does not need to change.
2026-07-20 21:13:48
0
Nile💠 :
Why can't LLM directly call APIs
2026-07-21 05:53:13
1
s3ns1ble :
MCP is a Trojan horse. They hide your company from its users. The LLM becomes the value provider to the customer instead of you. This is like when Facebook showed full news articles on the feed and stole traffic. It’s a dangerous thing to do.
2026-07-21 07:29:21
1
To see more videos from user @kodekloud, please go to the Tikwm
homepage.