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

Can you do yourself a favor and look at the source code and tell me why you think MCP is necessary here?

I mean you just took some examples and went "See MCP!" without any actual understanding of what that code is doing.

All of these have underlying API's that have exactly ZERO need for MCP. All of this functionality already exists and can be used with LLM's.

* https://help.ableton.com/hc/en-us/articles/209072009-Install...

* https://docs.blender.org/api/current/info_quickstart.html

* https://docs.unity3d.com/6000.2/Documentation/ScriptReferenc...

The most hilarious quote from one of those projects:

>The proxy server is required because the public facing API for UXP Based JavaScript plugin does not allow it to listen on a socket connection (as a server) for the MCP Server to connect to (it can only connect to a socket as a client).

Maybe that should have been the sign that this was completely unnecessary and stupid?

>Do you know of another way you can control all of those applications via LLMs?

Seriously. This becoming a bad joke. I mean conceptually, what did you think was happening here? MCP was just magically doing something that didn't already exist before?

It's a waste of effort and time. Do not use MCP.