MCPs: The Natural Evolution of CLIs

    Kent C. DoddsKent C. Dodds

    I recently shared that I'm building an application only accessible via MCP (Model Context Protocol), and someone commented that it's "just a CLI with extra steps." I appreciate the feedback, but it shows a misunderstanding of what MCPs are and their potential. Let's dive into why MCPs are a significant leap beyond traditional CLIs and APIs.

    Natural language: The game-changer

    The primary advantage of MCPs over CLIs is the ability to use natural language for communication. While CLIs require specific commands and syntax, MCPs allow users to interact more intuitively. It's like talking to a knowledgeable friend instead of remembering arcane incantations.

    MCPs enable natural language interaction, making them more accessible and user-friendly than traditional CLIs.

    Sure, you can pipe output from one CLI to another, but MCPs take this to a new level. AI can use one MCP to gather context and pass it to another — without these MCPs needing direct integration. It's like having a super-smart assistant that knows how to connect all your tools seamlessly.

    Empowering nontechnical users

    Here's where MCPs really shine: nontechnical people can confidently use your MCP service through an AI assistant they're already familiar with. You're not going to see many non-developers firing up a terminal to use your product, right? (Actually, someone ask the terminal.shop guys how many non-technical people bought coffee from them via SSH).

    For example, the journaling app I'm building (mostly as an MCP teaching tool and to explore the possibilities) could potentially be used by anyone comfortable chatting with AI assistants. No command line required!

    MCPs aren't just about broadening your user base — they're about providing a superior experience. Natural language interaction feels more intuitive and less intimidating than wrestling with CLI arguments and specific character orders.

    The future of interaction

    While my current project is more of an exploration than a mass-market product, it highlights an important point: MCPs represent a significant evolution in how we interact with software.

    MCPs increase accessibility, improve user experience, and open up new possibilities for software interaction.

    So, no — MCPs are not "just CLIs with extra steps." They're a leap forward in making powerful software capabilities accessible to a broader audience through natural language and AI assistance. As the technology matures, we'll likely see even more exciting developments in this space.

    The next time someone dismisses MCPs as glorified CLIs, you'll know better. We're not just adding steps — we're paving a new path for human-computer interaction.

    Start designing the future of intelligent user experiences

    Join the EpicAI.pro newsletter to get updates on events, articles, and more as they’re released

    I respect your privacy. Unsubscribe at any time.

    Share