What if you don't need MCP at all?

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.

> MCP was a really shitty attempt at building a plugin framework

Can you go more in depth? The protocol is relatively simple, what about it you feel is "shitty" as a plugin framework?

The hate for MCP here is absurd.

It's JSON-RPC, with some descriptors.

And some comments about OAuth 2.

The value is in the consensus. You can make a tool that agents can connect to with no apriori knowledge.

>It's JSON-RPC, with some descriptors.

That's not even true. It defines the lifecycle of tool calling.

JSON-RPC with some descriptors would have been fine and amazing.