ProgrammerHumor
justWhy
Discussion
because you gotta keep up appearances
whilst the smallbrains are losing their minds over llms, and the grifters are pouring money into them in the hope of boosting their own wealth, everyone else has to just be a long for the ride
"LLMs are not so good in my field, I've used them and they say very convincing but incorrect and convoluted things. This is because my field requires the human touch, it can't be replaced by AI. But those overpaid engineers? They generate code, AI generates code. Why are we paying them so much? Let's just use AI."
The thoughts of an imbecile c-suite parasite.
What I don’t understand is why do we need MCP? We already have the REST standard for network calls, or you could use RPC. and on top of that GitHub has a great CLI. What benefit do we get from an MCP server?
And here I was thinking it was MineCraft Private server. As in for people working at github or something.
REST is not a standard. Not even close!
RPC is a completely generic term. There are hundreds of different RPC protocols.
MCP is just some API on top of the JSON-RPC 2.0 protocol.
Discoverability. Nobody is implementing rest as designed, rpc is totally without it, so this is a way for llms who direly need to figure out shit on the fly to be able to do so.
So the reason we should invent and go along with one standard is because everyone ignores the other standard? What makes you think it will be any different this time?
Because if you don't follow it, it doesn't work. Unlike REST and RPCs which are more ideas than standards and leave a lot of room for interpretation or customization.
That’s interesting, I’ll need to look into what MCP is/isn’t a bit more. My immediate impression has been the reason MCP “doesn’t work if you don’t follow it” is because it’s not proposing as much as something like REST. MCP is more like the curl + http standards than REST, in the sense it provides an interface for LLMs to interact with a tool, like how curl lets a user interact with a web server.
If that’s the case, my criticism is more that I don’t see the benefit of making an api that’s not accessible to humans AND AIs. HTTP and curl can be used by users and AI, so why do we need to provide a wrapper for AI?
MCP includes documentation for what can be accessed and what parameters must be provided.
Nothing stops us (technically) from having this with REST (and in many cases we do, e.g. Swagger/Open API). I get being annoyed at the unearned hype when the only benefit this approach really has over older ones is that same hype...
I mean, if by REST you mean OG rest, then I would say we don't already have it. It's more like a proposal that was ignored. Colloquial REST, the stuff we in fact "already have" doesn't cut it, so we need stricter protocols with clearer focus to solve that side.
MCP is api for api, except that api can use by Ilm s Easily
What makes MCP easier to interface for AI than making api requests to a REST api using curl, with a swagger doc for information on what the endpoints do?
It seems to me we already have the technology for interacting with services over the web, and good CLI tools already exist when you want to interact with a local tool. Could you give me an example of a use case where I’d want to my ai to use an MCP over a REST API or an existing command line tool?
There is none, we have cli, sdk, rest api, now mcp.
It just another way of communication, under the hood everything just a curl command.
Whoa this brings back memories, my grandpa had a neck tie with a little piggies and "MCP" pattern all over it
Model context protocol is not for people but llms