a post titled "mcp is dead" hit the front page of hacker news last week with 311 points and almost 300 comments. that is the kind of headline that makes you click and then makes you roll your eyes, because nothing in this space dies on a six-month timeline. so i read the argument, pulled the numbers, and checked what the people building these protocols are saying. the short version: mcp is not dead. the idea that you should wire every tool you own into an mcp server is the thing that is dying, and that distinction matters if you are deciding what to build this year.
what people are angry about
the model context protocol, for anyone who skipped the hype, is a standard anthropic shipped in november 2024 so language models can talk to external tools and data through one consistent interface. think of it as a common plug. the pitch was good. you write one server, any compatible model can use it.
the complaint is about what that plug costs you. every tool an mcp server exposes ships its full definition into the model's context window on connect. the name, the parameter schema, the response format, all of it. the quandri writeup that started the latest round measured it: four servers connected, 77 tools, and 21,077 tokens gone before the model reads a single word from you. that is 10.5% of a 200k context window spent on definitions you mostly will not call. the linear server alone ate around 12,807 tokens for 42 tools when the author only ever used two of them.
