Top
Best
New

Posted by ejholmes 19 hours ago

When does MCP make sense vs CLI?(ejholmes.github.io)
384 points | 245 commentspage 11
poly2it 12 hours ago|
I wonder if what we'll get out of MCP tech in the end is a standardised machine readable description of CLI interfaces? Could be neat actually.
mudkipdev 17 hours ago||
This got renamed right in front of my eyes
whatever1 17 hours ago||
First they came for our RAGs, now for our MCPs. What’s next ?
righthand 12 hours ago||
Lol people are so lost in the bs
lidn12 1 hour ago||
[dead]
fennecbutt 12 hours ago||
[dead]
aplomb1026 11 hours ago||
[dead]
SignalStackDev 18 hours ago||
[dead]
aplomb1026 17 hours ago||
[dead]
entrustai 14 hours ago|
The CLI vs MCP debate is about input ergonomics — how the agent invokes tools. Both sides are arguing about the left side of the pipeline.

The harder unsolved problem is the right side: what happens to the output before it becomes consequential action. Neither a CLI nor an MCP server tells you whether the text the agent just generated is compliant, scoped, or admissible. That enforcement problem exists regardless of which invocation pattern you prefer.

The best CLI in the world doesn't help you when the agent produces a clinical summary that omits a contraindication or a financial disclosure that drifts outside regulatory bounds. That's a different layer entirely — and it's mostly being ignored while everyone argues about transport protocols.

More comments...