MCP: A Protocol in Need of a Major Overhaul?

This article presents a critical analysis of the Model Context Protocol (MCP). The author attempted to build an MCP server, only to find the documentation lacking, design decisions bizarre, and the HTTP transport options (SSE+HTTP and the so-called "Streamable HTTP") overly complex and confusing, far inferior to the simplicity and efficiency of WebSockets. The author argues that MCP's excessive flexibility leads to increased complexity, higher maintenance costs, and security risks. They suggest replacing the existing HTTP transport with WebSockets and simplifying the protocol design for improved usability.