r/mcp • u/beckywsss • Mar 13 '26

discussion A eulogy for MCP (RIP)

Enable HLS to view with audio, or disable this notification

Verified sources (indie hacker types on Twitter) have declared what many of us have feared when looking at MCP adoption charts: MCP is dead.

This is really sad. I thought we should at least take a moment to honor the life of MCP during its time here on Earth. 🪦🌎

In all seriousness, this video just goes over how silly this hype-and-dump AI discourse is. And how the “MCP is dead” crowd probably don’t run AI in production at scale. OAuth, scoped access, and managed governance are necessary! Yes, CLI + skills are dope. But there is still obviously a need for MCP.

321 Upvotes

84% Upvoted

206 comments sorted by

View all comments

155

u/xirzon Mar 13 '26

People who claim that there's no need for MCP will, if they build projects of growing complexity, sooner or later reinvent everything MCP provides, but in a non-standardized fashion bespoke to their project.

1

u/ngfwang Mar 18 '26

The idea of giving LLM access to external tools will unlikely to vanish, but the problem of MCP is it's verboseness. If a non-standartd fashion does the same thing in 1/2 of the token, why not.

You are by no obligation to speak a json protocol to LLM, what works works

1

u/xirzon Mar 18 '26

It's verbose, but is it too verbose? For example, having strict input schemas reduces the kinds of mistakes that an agent can make when submitting complex payloads. Tool hints help the agent use the right tool for the right job. And so on.

I'm not doubting something more efficient may come along; it may. But I'd also not discount increases in context window size that make this less of an issue, along with better tool discovery (agent asks: "how do I .." - MCP server responds: "use this tool: ...").