Developers Flip Toward MCP Over CLI for Agent Tool Integration

Over whether AI coding workflows should adopt Skill+CLI or MCP servers, multiple developers weighed in, and the discussion clearly shifted toward MCP between September 15-16.

Confirmed

• On September 15, PrinceSauromates opened the discussion: with open-source models getting more reliable, he wanted to upgrade his AI coding workflow and personally leaned toward Skill+CLI (feeling it offered more control), but hesitated in the face of MCP's standardized access.
• On September 16, trq212 said testing changed his mind: to his own surprise, MCP fits most integration scenarios better than CLI, because model tool calling has improved dramatically, tools can be deferred/lazily loaded, and MCP now supports a stateless mode.
• Rhys Sullivan (relayed via teropa) declared MCP has "won comprehensively," suiting agents better than CLI in most scenarios: an indexable tool catalog lets agents scale to unlimited tools, no full sandbox is needed to run, and all MCP servers share a consistent authentication mechanism.
• mitsuhiko joined in and agreed: tool calling has improved greatly, lazy loading avoids context explosion, the MCP protocol is now stateless and engineering-wise cleaner, so MCP already beats CLI for most integration scenarios.
• Security researcher yenkel brought back his article "If you kill MCP, you don't give a st about security": pushing back on the "MCP is dead, CLI is better" narrative, he stressed that CLI-invoked APIs cannot provide the guarantees good security requires.

Unconfirmed

• PrinceSauromates's initial intuition that "CLI gives more control" was never directly rebutted or validated in the follow-up discussion, and no consensus was reached on it.

Why it matters

• This debate directly shapes foundational architecture choices for the AI agent tool layer: if MCP's indexable catalogs, deferred loading, and stateless features have indeed matured, CLI integration's disadvantages in security and scalability get amplified; meanwhile yenkel's security objections show the debate is not over yet.

2026-09-15 ~ 2026-09-16 · 5 related posts

• [source] Skill+CLI vs MCP: a developer asks which integration route wins on tokens and reliability — PrinceSauromates · 2026-09-15
• [source] MCPs Beat CLIs for Most Integrations, Developer Concludes After Hands-On Testing — trq212 · 2026-09-16
• MCP now beats CLIs for most integrations as protocol goes stateless — mitsuhiko · 2026-09-16
• [source] MCP security researcher: killing MCP means you don't care about security, CLIs lack guarantees — yenkel · 2026-09-16
• MCP's total victory: why MCP beats CLIs for most agent integrations — teropa · 2026-09-16