Re:OpenCode Browse
by mickeyp on Tuesday November 17, 2026 @02:03AM
(#50528352)
Harness developer here.
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.
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.