Developers blast MCP over new elicitation overhead
Developer Dax Raad has raised significant architectural concerns regarding the Model Context Protocol (MCP) specification, noting its strict reliance on a "one process equals one session" model creates severe overhead. The critique highlights that MCP's new elicitation capability lacks necessary context information, making it impossible to identify session events without maintaining separate server instances for each connection.
MCP is moving fast to become the standard for AI context, but foundational architectural oversights threaten its scalability for production deployments.
* **Severe Overhead Limitations:** Forcing a 1:1 ratio between processes and sessions is a massive bottleneck for multi-tenant or remote server environments.
* **Elicitation Blind Spot:** The fact that elicitation events carry no context metadata shows that the protocol hasn't fully solved asynchronous, stateful communication.
* **Premature Standardization:** This critique validates developers who feel the MCP specification is being standardized before core use cases like robust session management are properly proven out.
DISCOVERED
1h ago
2026-06-25
PUBLISHED
7h ago
2026-06-24
RELEVANCE
AUTHOR
thdxr