What happened?
An essay titled “MCP was always a bad idea?” reached 181 points on Hacker News, making it the highest-signal discussion in this batch.
Why people care
MCP has become the default way agents reach external tools. A well-argued case against the abstraction lands directly on the infrastructure choice a large number of teams have already made.
The argument in context
The useful part of the essay is not simply whether MCP is good or bad. It asks whether a general protocol creates the right abstraction for agents that need different permission models, context sizes and failure handling across tools.
Why it matters
Once a protocol becomes the default integration surface, its costs are easy to hide. Teams may inherit discovery, authentication and compatibility decisions before they have measured whether the abstraction helps their own workflows.
What to read for
Separate the author’s architectural criticism from the discussion’s broader reaction. The Hacker News thread is useful as a signal of attention, while the essay is the primary source for the actual claims and trade-offs.