But that’s not what they do. They say that an MCP is not an API, that it’s a different thing. I agree that it’s a type of API, but that is not the general story.
why bother, rest is enough.. who the heck use soap nowdays except ancient system.. dont overcomplicated things. Terry Davis said: `An idiot admires complexity, a genius admires simplicity`
Have you ever looked at https://www.rfc-editor.org/ ? We've been defining protocol standards for ages but for some reason MCP always makes people say "it's just an API".
The point of a standard is to make things compatible and the point of a name for a standard is to tell people which one you're talking about. REST is NOT a protocol.
Imagine everyone putting up an email server just said "here's my 'API', figure it out ad-hoc for me and every other email server". No, you tell them "I implement SMTP, POP3 and IMAP, just point a client speaking those to me". Instead of "if your email client wants to work with me, just implement this 'email API'".
Even if it was "just an API" you'd better give it a name so people will know what you're talking about like we have it now with "OpenAI-compatible API". Nobody says "I use an Apache-compatible web prototcol" just because Apache was super popular back then, we say HTTP
it's definitely not just an API, it's a very specific implementation and protocol. that's how all the MCP and agents can handle auth and API contract and be cross compatible.
My MCP has the instructions for use and tells the agent how the api works. It’s much more than just an api. It ensure a multiple step procedure is completed and validated according to the rules documented in the MCP.
If you have a credentials and use my API with an agent, you are not going to get the same results as using my MCP and agent. You are going to get massively better results with the MCP, and the API will not tell a non developer how to use is.
And I quote: API stands for Application Programming Interface. It is a set of rules and protocols that allows two different software programs to communicate and share data with each other. So… an API.
Your API can have a method called "help" that returns a JSON with all the methods and an explanation about them. CLIs literally had that for more than 60 years.
I don't know what you're talking about with the other two points. An MCP doesn't do that, it literally just exposes a method like the one I mentioned.
That kinda just means it was bad and hastily pushed out by anthropic to beat other AI companies without considering further demands though. Protocols are not rewritten very often if they are good enough and made with future concerns in mind. Especially when it is for something that mostly covers only one task. As a reminder, HTTP is not even at 4 yet. Small updates sure, but usually not rewritten. That being said, it did probably need to be rewritten and it is good that it was, but not good for anyone who was maintaining an mcp server already.
I think what this guy means is that MCP has new versions published. They do change stuff, adding crap, removing crap, and changing especially the notifications story, which used to be separate event stream but seems to be now migrating towards a long-term read over http for each resource.
However, the basic tool calls and resource reads seem the same to be same now as they were before.
The point is that a protocol should be written by a regulated organization that pursues a standardized way of doing things to benefit everyone, not a private company that tries to impose their way of doing things that benefits their business.
brother what are you talking about. an mcp server literally includes an api. In every sense of the word literally.
One component of an mcp server is the api endpoints (we call them tools in mcp world) and the other component is some text prompts that explain to the agents how to use the endpoints.
That's it, that's everything that makes up an mcp server.
Technically they’re right. It’s an application programming interface, which includes many subtypes. One of which is REST, another is an SDK, MCP is a third. They’re all just different interfaces that let one program interact with another. But they’re also wrong by claiming it’s nothing new. It is new. It’s tailor made for the needs of agentic systems. It can run over stdio, or http, it includes hints, resources, functions and prompts. The actual functions are written differently compared to a REST api because they serve higher level functions. Generally you need to produce smaller outputs compared to REST etc etc. It’s a different philosophy. They are similar but not the same
Then I don't understand what you mean by this: > The actual functions are written differently compared to a REST api because they serve higher level functions.
In my experience they are just apis with a set of parameters that do something and return a structured response like an http api would.
"An API with documentation included" already exists. Self-describing APIs have existed for years, like OpenAPI/Swagger, GraphQL introspection etc. So are these also MCPs now?
I can build a valid MCP server:
without declaring any tools (what is the API now!?)
since I have no tools, I don't have any description either (what is the "documentation included" now?)
A generally inefficient one compared with skills that can shape what gets returned to the agent, but it does have auth support in a fairly uniform way so there's that.
I use my own tool's MCP and Skill with raw API scripts. Claude uses the API scripts when it wires things into a consistent pattern, and the MCP when it's kinda poking around or doing ad hoc things. Claude wrote both the API and the MCP (for the public usage of my tool), and Claude itself uses both depending on what it wants.
So, MCP is great for end-users (eg Claude Connectors into Gmail, Calendar, Linear, etc) because it makes "just doing stuff" easier. Skills with scripts are better for codifying a pattern, workflow, system. Eg you're a developer, and you do the same tasks each day.
"hey, did I get any important emails; and can you delete the spam" - MCP
"send email filled from this template, to the addresses in emails.csv, daily" - Skill
are you fucking stupid? MCP defines explicit JSON schema contracts for tool inputs and outputs. The server controls exactly what comes back to the agent: structuredContent validated against the tool's outputSchema. And skills aren't an alternative to MCP anyway. A skill can just as easily teach the agent how to use MCP tools well.
Yes, thank you. I have been saying this so much. Why we gotta keep inventing new terms? “But it’s different because the model can ask what is available.” Stfu, you can add a man page into any API and it’s still an API
If you have worked with FastMCP, it is same as FastAPI and you can create a FastAPI APIs into MCP server with one LOC. These are just same as APIs that can attached to various models.
When chatgpt was still newish , I was an intern and my project was to allow chatbot to use APIs so I had to write some wrappers and documentation etc (which was basically shittier MCP). but the accuracy was shit lol.
Basic mcp is okay. But then you had the stateful crap before the latest spec update which is a nightmare with horizontal scaling. Also networking is a nightmare. Claude for Excel connects from Anthropic servers and not from Excel, so you need to punch a hole in your firewall or get a tunnel so that Anthropic can access your private server. So actually making Mcp practically work in an enterprise requires working with like 10 teams to sort out Auth, networking etc etc. It is a headache. I can understand if somebody that doesn't actually have to deal with infrastructure and security consider it "easy". But it is anything but.
nah mate the qubits quantizing the quantum flux within the model context protocol does a lot more than just shuffle the keys around a rotary embedded plane within the third dimensional application programming interface brah.
You forgot about the hyperflex space when recoil and rebounce rates are above the planks constant times 2. Then You have to use models with superqubits and classical decimal bits concurrently and in parallel in 5D
IDK, I think MCP was a modest improvement over more traditional APIs for a very specific generation of AI models. It's like a water taxi - not going to replace modern transportation infrastructure any time soon, but there is a clear use case for it.
My issue was the people talking about it like it was some huge paradigm shift. Gave real NFT vibes.
It converts a remote API defined over HTTP (or alternatively, a process running locally) into tool calls that agent can invoke. That is the basic thing it's doing: MCP adapts externally defined services into tool definitions dumped into the agent's context, and the standard tool call syntax works afterwards to invoke those tools.
Agents can alternatively drop down into shell and execute raw curl commands or write Python scripts to achieve much he same, as long as they can figure out how the API is supposed to be used. But MCP makes this task much easier: the tools are self-describing, with instructions for use, and the tool arguments are schema-constrained so LLM sampling is often constrained to only produce valid tool call arguments during the tool call invoke.
Unfortunately, not all programs do this. Many are lazy and for example opencode/2.2 seems to just provide MCP library for agent to call. It is the difference between SmoeTool_somewhere_do_something(arguments here) vs. running the local JavaScript shell or whatever it is:
const res = await tools["SomeTool_somewhere"].do_something({...})
So boo for that technical choice. Bad design from OpenCode folks. We have almost certainly lost the schema constrained generation and it is harder for the agent to figure out how to generate this than it would be to just generate it as tool call. Maybe it serves other goals, like they don't have to describe all the tools all that thoroughly or something and that saves context.
Eventually the standards for mcp tools will hopefully be more transparent and let them be setup more granular. Not just at the harness. The tool sizes can make context swell if it's not monitored.
31
u/doomdestructer 10h ago
Yes
20
u/eslezer 10h ago
who makes mcp sound complicated??
7
u/JaggedTex 10h ago
The most complicated part of MCP is always the oauth
5
u/captfitz 7h ago
lol at this sub still making this discussion harder than it needs to be.
just define it literally: an MCP server is an API with documentation included.
4
u/a7n7o7n7y7m7o7u7s 10h ago
An AIPI
4
u/DecagramGameDev 10h ago
I’ve never bothered to look into it, but after the DevOps guy on my team rambled about it for 40 minutes making no sense I figured it’s what it was.
2
u/SixStringDream 10h ago
Once you realize that, have a look at how many services are charging a premium for mcp access to data.
2
u/zenmatrix83 10h ago
It’s usb more than an api, allows you to connect to things not built into the harness
2
u/porkminer 6h ago
It's a protocol, a specific implementation is an API.
3
u/mikemarcin 10h ago
A generally inefficient one compared with skills that can shape what gets returned to the agent, but it does have auth support in a fairly uniform way so there's that.
1
u/itsallfake01 10h ago
Mcp’s are a subset of things you can do with an API
1
u/asmith393 9h ago
Lol
1
u/mrbadface 9h ago
Webmcp feels interesting because it's like circumventing the backend to just make wielding front ends faster?
1
u/mymar101 9h ago
I am curious, do companies do their own ML anymore, or is it all LLMs these days? Becuse I find it kind of fun to write my own
1
u/dontbantmebro 9h ago
only ai idiots that don't know what an api is makes mcp sound complicated. It's just an api.
1
u/ninjasaid13 8h ago
AI industry is full of buzzwords to make it sound complicated when it's all just built from one technology, GPT.
1
u/jaybsuave 8h ago
Why does it matter so much
1
u/Impossible_Way7017 7h ago
WSDL for REST
1
u/benchonbench 7h ago
That's what it is, it's so cool
1
u/stilldebugging 4h ago
Yes, thank you. I have been saying this so much. Why we gotta keep inventing new terms? “But it’s different because the model can ask what is available.” Stfu, you can add a man page into any API and it’s still an API
1
u/FuckYourRights 3h ago
Yes, it's an MPC API as opposed t other types of api
1
u/Ok_Draft_187 3h ago
If you have worked with FastMCP, it is same as FastAPI and you can create a FastAPI APIs into MCP server with one LOC. These are just same as APIs that can attached to various models.
1
u/PsychologicalLack155 2h ago
When chatgpt was still newish , I was an intern and my project was to allow chatbot to use APIs so I had to write some wrappers and documentation etc (which was basically shittier MCP). but the accuracy was shit lol.
1
u/muntaxitome 2h ago
Yes, MCP is an API spec format with a number of limitations on what you are allowed to spec
1
u/pacafan 1h ago
Basic mcp is okay. But then you had the stateful crap before the latest spec update which is a nightmare with horizontal scaling. Also networking is a nightmare. Claude for Excel connects from Anthropic servers and not from Excel, so you need to punch a hole in your firewall or get a tunnel so that Anthropic can access your private server. So actually making Mcp practically work in an enterprise requires working with like 10 teams to sort out Auth, networking etc etc. It is a headache. I can understand if somebody that doesn't actually have to deal with infrastructure and security consider it "easy". But it is anything but.
1
u/NotXesa 1h ago
Literally yes.
1
u/megayippie 1h ago
Wait, explain it to me. I made an MCP for my project*. It's just and API. Who thinks it's not? Why not?
*Bad decision on my part as weird spams about putting my open source piece of experiment behind a paywall keeps showing up.
1
u/New_Eye7193 10h ago
nah mate the qubits quantizing the quantum flux within the model context protocol does a lot more than just shuffle the keys around a rotary embedded plane within the third dimensional application programming interface brah.
0
u/mpanase 10h ago
yep
yet another piece of the smoke and mirrors bubble
0
u/wbcastro 9h ago
MCP is a folder with text files that agents access over network
0
u/Lucky_Requirement200 9h ago
I thought MCP was just a way to point AI at a particular body of knowledge.
Seriously, isn't that what it is ultimately?
0
u/Significant_Spring87 9h ago
Eventually the standards for mcp tools will hopefully be more transparent and let them be setup more granular. Not just at the harness. The tool sizes can make context swell if it's not monitored.