Comment by troupo

> The fact that there is a bidirectional stateful mode for HTTP is horrifying,

Oh no, really? So why didn't the new vibe-coded hotness use WebSockets for bidirectional communication?

> MCP is here, it solves problems we have now,

Many other protocols save the exact same problem of client-server communication with well-defined ways of discovering available API calls.

> it's supported by industry.

It's supported by hype and people who have very little knowledge of what existis in the world.

Also, industry is notorious for supporting a lot of crazy and bad shit. Doesn't make it good.

> If there are pain points, we can fix them in the standard without throwing the baby out with the bathwater.

You have already thrown out a lot of babies by deciding that the vibe-coded MCP protocol is the only true way to set up two-way communication between a server and a client, and refuse to even entertain the thought that it might not be a good protocol to begin with.