For those having exposed both MCP and CLI, should both tools/commands expose the exact same capabilities?

Reddit r/AI_Agents News
mcp cli architecture api-design developer-experience

Summary

The author discusses the architectural challenge of designing both MCP and CLI interfaces, weighing the benefits of mirroring capabilities versus leveraging the unique strengths of each (composability for CLI, safety/auditability for MCP).

I'm building MCP and CLI at my company, directly exposed to users. I had done the MCP first, investing time and thoughts on not making it just a wrapper of our APIs. When building the CLI, I wondered if it should mirror the MCP implementation? Instinct said yes but thinking longer I'm less sure. CLI feels better for composability with pipes, jq, grep etc while MCP feels better for typed safe and auditable workflows (potentially with better permissioning). Curious how people who are handling both are thinking about it!
Original Article

Similar Articles

@RhysSullivan: https://x.com/RhysSullivan/status/2070311929038680262

X AI KOLs Following

The author reflects on why the Model Context Protocol (MCP) has struggled, contrasting it with CLI-based agent workflows and arguing for more flexible tool integration. They suggest that agents should support MCP, CLI, API, etc., and express optimism about MCP's future despite current challenges.

MCP is dead?

Hacker News Top

A technical critique of the Model Context Protocol (MCP) arguing that it consumes excessive context window tokens, has low operational reliability, and overlaps with existing CLI/API approaches, with measurements from Quandri's stack showing 10.5% context usage.