Software Needs Either MCP or CLI
EXM7777 · x · 2026-07-17
The author argues that we should stop prioritizing software lacking both MCP and CLI. Learning a new UI is inherently negative value, and the future is shifting towards having "agents drive software" rather than humans manually clicking around.
They also note that if a tool only offers an API, a CLI can still be generated using tools like PrintingPress. Products like Kit and beehiiv are already providing their own MCPs, allowing agents to configure emails, manage subscribers, draft newsletters, and send/read analytics directly without opening a web interface.
More from coding & agent
- Soft Clamp cuts tool-call overuse in multi-teacher distillation, from 13.7% to 9.0% — antgroup · 2026-07-21
- Agent harness memory loss and compaction are still a major usability problem — adityaag · 2026-07-21
- SpecJudge runs locally on Ollama to pick the right-sized AI model for your project — jokiruiz · 2026-07-21
- A developer maps out six design rules for CLIs that humans and AI agents can both use — yujiezha · 2026-07-21
- A coding-agent skill that forces ADHD-friendly, answer-first output — ayghri · 2026-07-21
- A set of agent skills for CAD, robotics, and hardware design — earthtojake · 2026-07-21