←back to thread

237 points jdkee | 1 comments | | HN request time: 0.218s | source
Show context
whoknowsidont ◴[] No.45948637[source]
MCP was a really shitty attempt at building a plugin framework that was vague enough to lure people into and then allow other companies to build plugin platforms to take care of the MCP non-sense.

"What is MCP, what does it bring to the table? Who knows. What does it do? The LLM stuff! Pay us $10 a month thanks!"

LLM's have function / tool calling built into them. No major models have any direct knowledge of MCP.

Not only do you not need MCP, but you should actively avoid using it.

Stick with tried and proven API standards that are actually observable and secure and let your models/agents directly interact with those API endpoints.

replies(8): >>45948748 #>>45949815 #>>45950303 #>>45950716 #>>45950817 #>>45951274 #>>45951510 #>>45951951 #
cyanydeez ◴[] No.45948748[source]
probably easier to just tell people: You want MCP? Add a "description" field to your rest API that describes how to call it.

That's all it's doing. Just plain ole context pollution. World could be better served by continuing to build out the APIs that exist.

replies(6): >>45949052 #>>45949068 #>>45950107 #>>45950478 #>>45951105 #>>45951859 #
1. blitzar ◴[] No.45951859[source]
> World could be better served by continuing to build out the APIs that exist.

before LLM's and MCP the world was depreciating or locking down APIs