- they necessarily work through the context window and therefore don’t compose;
Meaning, if your agent has a skill that needs to run five MCP tools in a certain way, it can’t just script that away the first time it sees this, and have that flow be fast and token efficient from then on.
MCPs are a 2025 tech meant to solve 2025 AI problems.
funny, because you are complaining about limitations of MCP that have been solved since 2025
which point exactly?
I am going to push back on this a bit as someone who also has scepticism (bloated spec, concepts deprecated already, etc.) but ultimately think it solves a few gnarly problems whilst admittedly -- it's early days -- creating a few more.
The first argument in favour of MCP is that large enterprises like it. It's a controlled surface to give access to things that may never have had an API before. Yeah, OK, that feels like a "loser takes all" moment but it does at least give you access to something you did not have before.
The second is that it tries to solve thorny things like letting the server ask for information by way of a form-like construct. That is actually quite handy for servers that do asynchronous or slow work, and that may require feedback from you over time. Doing this with start-stopping a tool harness can also work, but it's fiddly because a context compaction event can happen which might lose state; not all harnesses handle this well; LLMs may get confused; etc.
Finally you can inject, in a good harness anyway, some or all of these tools into your system so they become part of the fabric. You can build your own little cut-down surface area so by removing shell access you let your AI call Foo and Bar MCP calls and nothing else. That also is useful.
But yes: you're right fundamentally. It's SOAP/RPC all over again, and CLI+skill should be the default for your own tooling if you can get away with it.
You'd simply scope the old school APIs with relevant access credentials.
what do you do when you have an agent running in an execution environment that does not have access to a terminal? has that thought ever entered your brain?
i mean why do rest apis even exist, you can just do everything through cli commands
It adds security but...
- adds a service which is another attack surface that can be compromised.
- adds another system that requires maintenance and securing to prevent compromise.
- takes machine resources
- duplicates a subset of what can easily be harness functionality
- duplicates services and security (usually) of existing APIs, or adds another layer on top.
Whereas ultimately an AI harness
- will improve and optimise its own skills performing the same MCP functions
- can use plugins
- can have harness centralised security controls and behaviours
MCP becomes a false economy for our current AI implementations, it's real purpose seems to be a crutch for that small models that struggle to write their own skills that use existing APIs. The thing is this is a problem that is rapidly disappearing, but could also be performed by secured harness plugins.