MCP Debate: Token Tax, Context Bloat, and What Devs Can Do

The useful part

If you run agents today, the debate is a prompt to audit what your tools actually cost in context and dollars before you add another server. What happened A blog post titled "Why MCP was always a bad idea" (maharship.com) argues that the Model Context Protocol was designed for 2024 models and that it generates context bloat and a token tax. The post is the seed of a renewed debate, not a formal specification change.

How it works

• The claim is architectural and cost-oriented: the protocol's shape, as the author sees it, does not fit how models are used now.
• The discussion landed on Hacker News as a thread with roughly 165 points and more than 100 comments in the last ~13 hours (news.ycombinator.com/item?id=49779329).
• On X, the post is being cited alongside counter-arguments about the value of audit and sandbox controls.
• Example posts circulating include "MCP was always a bad idea" is today's HN fight..., I don't think MCP was a bad idea рџ¤"...
• No benchmark, migration, or incident is claimed by the post itself in the material available.

What to take from it

<img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scal...

Details worth keeping

the vision goes far beyond just server, and Why MCP Was Always a Bad Idea? These are the framings in the conversation, not conclusions.