MCP vs CLIs: The Good, the Bad, and the Ugly
CLIs are efficient, composable, and familiar to agents. MCP is younger and rougher, but its weaknesses can be fixed. It also offers security and governance that CLIs structurally cannot.
Recent content on kvg.dev
CLIs are efficient, composable, and familiar to agents. MCP is younger and rougher, but its weaknesses can be fixed. It also offers security and governance that CLIs structurally cannot.
Agents don’t work like developers. They can’t read the docs, iterate on a bad design, or grumble their way through a weird API. They just pay in tokens. Here’s why APIs designed for agents are eating the world, and the principles to design for them.
MCP addresses a N×M integration problem. Skills tackle tool bloat. The surface-level overlap in primitives doesn’t make them competitors—it makes them complementary. Here’s why the ‘versus’ framing is wrong and how they work together.
MCP servers are proliferating, but many ship with serious Tool Bloat problems. Learn why excessive tool definitions degrade agent performance and how to build lean, effective systems.
I built this site in a weekend using Hugo, GitHub, and Cloudflare Pages. This blog walks through the steps that made the magic happen.
I’m currently a Senior Staff Software Engineer working on AI + Databases @ Google Cloud. With nearly a decade of experience at industry-leading tech companies, I have a history of engineering scalable, reliable platforms that deliver exceptional developer experiences.