Re:MCP is eating the world–and it's here to stay
by simiones on Wednesday June 25, 2025 @05:44AM
(#44375360)
MCP is a detail here. The exact same thing would happen if generate_node and search were exposed as REST endpoints, if Claude Desktop had used REST instead of MCP.
[ Parent
| on HN ]
Re:MCP is eating the world–and it's here to stay
by bboygravity on Wednesday June 25, 2025 @08:03AM
(#44376297)
Isn't part of the issue that LLM's are relatively bad at REST and json and all that?
I remember like 2 years ago there was big hype/revolution around ChatGPT finally being able to return ONLY valid json when you asked it to. So apparently LLMs are not that good at scripting without mistakes.
Having said that, I honestly have no clue what MCP looks like or is lol :p
Re:MCP is eating the world–and it's here to stay
by simiones on Wednesday June 25, 2025 @08:47AM
(#44376686)
MCP is a form of JSON-RPC over HTTP, so I don't think it has anything to do with that.
Re:MCP is eating the world–and it's here to stay
by fennecbutt on Wednesday June 25, 2025 @09:30AM
(#44377109)
MCP is just json.
But to your last point: go look it up, have a read through their client/server implementations (for your language of choice). It doesn't actually take that long because the concept is actually rather simple, so I totally recommend it.
Re:MCP is eating the world–and it's here to stay
by visarga on Wednesday June 25, 2025 @11:12AM
(#44378269)
Maybe not, I think they trained the model to be especially capable of MCP tool use, and generated data this way. Other formats and systems might be slightly worse, and the whole model would probably not handle such a diversity of tools if all it had was trained on much less diverse API integrations.