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.

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

but the major user interfaces for operating LLMs do and that's what matters

> 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.

so what's the proven and standard API I can use to interact with ableton live? blender? unity3d? photoshop?

What do all of the links below have in common? Do you know of another way you can control all of those applications via LLMs? Computer use?

https://github.com/ahujasid/ableton-mcp

https://github.com/ahujasid/blender-mcp

https://github.com/CoplayDev/unity-mcp

https://github.com/mikechambers/adb-mcp

The mcp part is not essential for the actual controlling of the applications. You could “rip out” the mcp functionality and replace it with something else. The only reason why the authors chose mcp is most likely that it was the first and therefore most common plugin interface for llm tools.

Unfortunately, most standards that we end up with are only standard because they're are widely used and not because they are the best or they make the most sense.