Hacker News stirs over "I still prefer MCP over skills"

The argument, in brief

A blog post titled "I still prefer MCP over skills" at david.coffee has rekindled a small but lively debate on Hacker News. It has been reported that the author lays out a case for preferring an MCP-style approach — a compact, end-to-end capability — rather than breaking functionality into many discrete "skills." The post reportedly frames the choice as one of focus and cohesion versus modularity and reuse. Simple, punchy. A little nostalgic, too.

The community pushback

Comments on Hacker News ranged from nods of agreement to blunt pushback. Some readers allegedly praised the clarity and developer ergonomics of a single, opinionated MCP; others warned that monoliths bite back as systems scale, arguing skills make tooling, debugging, and third-party integrations easier. Who's right? Depends on the team, the product, and whether you like wrestling with duct tape or prefer a set of Swiss Army knives.

Why it matters

This isn't just academic hair-splitting. The discussion maps onto current industry choices around agent design, plugin ecosystems, and how companies ship AI features. Pick consolidation, and you may move faster early on. Pick modularity, and you'll probably face more upfront coordination — but maybe less pain later. The emotional heart of the post is plain: the author misses the clean satisfaction of a finished, coherent piece of work. Relatable. And in an era obsessed with "composable" everything, that sentiment is worth listening to.

Sources: david.coffee, Hacker News