[varenc]

The value is that many companies like building MCP servers much more than CLIs. For whatever reason.

Here's some companies that offer MCP servers but don't seem to offer an equally featured CLI:

   - Asana
   - Square
   - Linear
   - Dropbox 
   - Canva
   - Slack (sorta)
   - Figma (sorta)

and many more that offer both, but support their MCP more.

Should they all be offering CLI tools? IMHO, yes absolutely. But an MCP server gets much more interest. I'd rather encourage them to keep improving and supporting their MCP services than telling them to drop it for a CLI.

There's lots of things like this in technology where you end up stuck with the first thing because its popularity perpetuates itself. The QWERTY keyboard I'm typing this on is a prime example. x86 is another one.

[didibus]

A CLI needs to work on windows, mac, linux, android, iOS, etc. And it still needs some backend APIs to call. So creating one is a lot more work than just making an MCP.

[PaulHoule]

That kind of code is easily portable in C or Rust or Go or Java or Python so long as it is a CLI and not GUI.

[oliculipolicula]

Again, tangential, relevant only in that CLI "portability coolness" captures only some of the meaningfulness

Having slept on the poorly made point I was trying to stick. I'm aware its still all tell no show )-:

  A comment worthy of hacker news highlights, Amish-made, fully earnest!

Would appeal to people with money, all manner of handlers, enbies born to embrace struggle, not to mention portability porn addicts. All things to all people but without the messianic contingent

  An Amish who might well have built a Space Lasers Platform  at Bell Labs!

Should perhaps be the character to learn how to play. This same Amish character would only use CLIs, on a wooden nonelectronic keyboard

I credit the obvious (to you) people here (incl you again) for this concept of an idea. Molon labe

Update: backrooms is getting serious traction in Indonesia. Ask me in a year if it was only meta-interest

[didibus]

The language barely matters, the issue is packaging, distribution, platform permissions, pushing updates, keeping client/server versions in sync, shell support, etc.

Where-as if you just expose HTTP endpoints, all that doesn't matter, you just need cURL or any app, like the chatGPT mobile app, can just call into your endpoint.

[fooster]

The mcp support gets more support because there is no cli.