MCP is dead; long live MCP

I've been working with MCP for a few months now, building adapters for desktop automation (browser, CLI tools, Office apps).

The protocol itself is solid - the JSON-RPC transport and tool/resource abstraction work well. What's missing is the ecosystem of ready-to-use adapters.

Most developers want to connect AI to their existing tools without writing custom integration code. That's the real gap right now.

The "MCP is dead" framing is premature IMO. It's more like "MCP needs better tooling and adapters" - which is a solvable problem.

[flagged]

I’m struggling to understand the recent wave of backlash against MCP. As a standard, it elegantly solves a very real set of integration problems without forcing you to buy into a massive framework.

It provides a unified way to connect tools (whether local via stdio or remote via HTTP), handles bidirectional JSON-RPC communication natively, and forces tools to be explicit about their capabilities, which is exactly what you want for managing LLM context and agentic workflows.

This current anti-MCP hype train feels highly reminiscent of the recent phase where people started badmouthing JSON in favor of the latest niche markup language. It’s just hype driven contrarianism trying to reinvent the wheel.