The author uses their feelings a lot to describe their distaste for MCP. It doesn’t read like a very well informed article should, in my opinion.

MCP servers are like proxies, that can adapt their represented tools and resources based upon external conditions. They’re far from being static in nature and can provide an entry point for otherwise hidden or secured functionality. Ie. some actions may be provided via an MCP and not otherwise. File resources may be present behind an MCP server and not otherwise. Tools may be relevant for a certain agent and not others, or they may become unavailable.

That, and regular APIs often don’t expose data in a streaming capacity that LLMs benefit from. That’s why you see MCP servers serving HTTP streams or SSE.

Static files make this inflexible for what, simplicity?

At least we have a standard now, for this kind of thing. Static files would be a lazy half-arsed solution at beast.

MCP tooling exists because sometimes your need to reduce heuristics to get the dumb LLM to do something useful. Tools do things programmatically correctly every time based on what they’re programmed to do. The only thing the LLM has to do is pick the right tool, provide inputs, and read outputs. The LLM can fuck up in all sorts of ways, and MCP is a way to narrow the sorts of things it can fuck up on.

I can#t wait for AI to fuck up in more varied and stupid ways by people giving it control over stuff. Great. No notes at all. Anyone who sows this crap should reap the consequences.